iOS App 崩溃问题`[UIWindow warpPoint:]` [英] iOS App crash issue `[UIWindow warpPoint:]`
本文介绍了iOS App 崩溃问题`[UIWindow warpPoint:]`的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我在我的应用中发现了一个奇怪的崩溃问题,我无法从崩溃报告中获得足够的消息.
I found a weird crash issue in my app, and I can't got enough message from the crash report.
这是崩溃报告:
-[TileLayer _isChargeEnabled]: unrecognized selector sent to instance 0x14aeadb0
(null)
(
0 CoreFoundation 0x376298a7 __exceptionPreprocess + 186
1 libobjc.A.dylib 0x3169e259 objc_exception_throw + 32
2 CoreFoundation 0x3762ca9b -[NSObject doesNotRecognizeSelector:] + 174
3 CoreFoundation 0x3762b915 ___forwarding___ + 300
4 CoreFoundation 0x37586650 _CF_forwarding_prep_0 + 48
5 UIKit 0x30775e43 -[UIWindow warpPoint:] + 686
6 UIKit 0x3075c1ff _UIApplicationHandleEvent + 2438
7 GraphicsServices 0x3777922b PurpleEventCallback + 882
8 CoreFoundation 0x375fd523 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 38
9 CoreFoundation 0x375fd4c5 __CFRunLoopDoSource1 + 140
10 CoreFoundation 0x375fc313 __CFRunLoopRun + 1370
11 CoreFoundation 0x3757f4a5 CFRunLoopRunSpecific + 300
12 CoreFoundation 0x3757f36d CFRunLoopRunInMode + 104
13 GraphicsServices 0x37778439 GSEventRunModal + 136
14 UIKit 0x3078bcd5 UIApplicationMain + 1080
15 Movie 0x00022eb3 _mh_execute_header + 7859
16 Movie 0x00022e40 _mh_execute_header + 7744
)
推荐答案
好吧,这意味着您尝试将消息(也称为调用方法)_isChargeEnabled
传递给类 TileLayer 的对象,但它是不存在.
Well, it means you tried passing a message (a.k.a calling a method) _isChargeEnabled
to an object of class TileLayer, but it is non-existent.
更新我做了一个快速的谷歌搜索,结果 _isChargeEnabled
是苹果的私有 API.你可以检查这个和this 了解更多信息.
UPDATE
I did a quick google search and turns out _isChargeEnabled
is private API of Apple. You could check this and this for more information.
这篇关于iOS App 崩溃问题`[UIWindow warpPoint:]`的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文