Crashlytics线程仅在使用Xcode11构建的iOS13上崩溃

bem*_*l12 6 crashlytics ios13 xcode11

我的应用仅在具有以下调用堆栈的iOS13上崩溃:

#57. Crashed: com.twitter.crashlytics.ios.exception
0  myapp                          0x105d6d494 CLSProcessRecordAllThreads + 376 (CLSProcess.c:376)
1  myapp                          0x105d6d87c CLSProcessRecordAllThreads + 407 (CLSProcess.c:407)
2  myapp                          0x105d5d58c CLSHandler + 26 (CLSHandler.m:26)
3  myapp                          0x105d6bab4 __CLSExceptionRecord_block_invoke + 198 (CLSException.mm:198)
4  libdispatch.dylib              0x1be5c100c _dispatch_client_callout + 20
5  libdispatch.dylib              0x1be5cd804 _dispatch_lane_barrier_sync_invoke_and_complete + 60
6  myapp                          0x105d6b55c CLSExceptionRecord + 205 (CLSException.mm:205)
7  myapp                          0x105d6b390 CLSExceptionRecordNSException + 102 (CLSException.mm:102)
8  myapp                          0x105d6afb4 CLSTerminateHandler() + 258 (CLSException.mm:258)
9  libc++abi.dylib                0x1be6d9634 std::__terminate(void (*)()) + 20
10 libc++abi.dylib                0x1be6d8f58 __cxa_get_exception_ptr + 34
11 libc++abi.dylib                0x1be6d8f10 __cxxabiv1::exception_cleanup_func(_Unwind_Reason_Code, _Unwind_Exception*) + 126
12 libobjc.A.dylib                0x1be6341f8 _objc_exception_destructor(void*) + 362
13 Foundation                     0x1bee05434 -[NSISEngine tryToOptimizeReturningMutuallyExclusiveConstraints] + 322
14 Foundation                     0x1bebfeb94 -[NSISEngine _optimizeWithoutRebuilding] + 72
15 Foundation                     0x1bebfeaa8 -[NSISEngine optimize] + 116
16 Foundation                     0x1bebfe718 -[NSISEngine performPendingChangeNotifications] + 116
17 UIKitCore                      0x1c2e447c4 -[UIView(Hierarchy) layoutSubviews] + 316
18 UIKitCore                      0x1c23c6948 -[UIButton layoutSubviews] + 596
19 UIKitCore                      0x1c2e57abc -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 2156
20 libobjc.A.dylib                0x1be62faf0 -[NSObject performSelector:withObject:] + 68
21 QuartzCore                     0x1c53f60f4 -[CALayer layoutSublayers] + 292
22 QuartzCore                     0x1c53f63fc CA::Layer::layout_if_needed(CA::Transaction*) + 484
23 QuartzCore                     0x1c5409964 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 140
24 QuartzCore                     0x1c534ec1c CA::Context::commit_transaction(CA::Transaction*, double) + 308
25 QuartzCore                     0x1c5379bd8 CA::Transaction::commit() + 684
26 QuartzCore                     0x1c537abc0 CA::Transaction::release_thread(void*) + 232
27 libsystem_pthread.dylib        0x1be62c3c0 _pthread_tsd_cleanup + 584
28 libsystem_pthread.dylib        0x1be624dbc _pthread_exit + 84
29 libsystem_pthread.dylib        0x1be626de8 _pthread_wqthread_legacy_worker_wrap + 98
30 libsystem_pthread.dylib        0x1be626b30 _pthread_wqthread + 424
31 libsystem_pthread.dylib        0x1be62cc78 start_wqthread + 8

--

Fatal Exception: NSInternalInconsistencyException
Modifications to the layout engine must not be performed from a background thread after it has been accessed from the main thread.
0  CoreFoundation                 0x1be919c30 __exceptionPreprocess
1  libobjc.A.dylib                0x1be6340c8 objc_exception_throw
2  Foundation                     0x1bee05434 -[NSISEngine tryToOptimizeReturningMutuallyExclusiveConstraints]
3  Foundation                     0x1bebfeb94 -[NSISEngine _optimizeWithoutRebuilding]
4  Foundation                     0x1bebfeaa8 -[NSISEngine optimize]
5  Foundation                     0x1bebfe718 -[NSISEngine performPendingChangeNotifications]
6  UIKitCore                      0x1c2e447c4 -[UIView(Hierarchy) layoutSubviews]
7  UIKitCore                      0x1c23c6948 -[UIButton layoutSubviews]
8  UIKitCore                      0x1c2e57abc -[UIView(CALayerDelegate) layoutSublayersOfLayer:]
9  libobjc.A.dylib                0x1be62faf0 -[NSObject performSelector:withObject:]
10 QuartzCore                     0x1c53f60f4 -[CALayer layoutSublayers]
11 QuartzCore                     0x1c53f63fc CA::Layer::layout_if_needed(CA::Transaction*)
12 QuartzCore                     0x1c5409964 CA::Layer::layout_and_display_if_needed(CA::Transaction*)
13 QuartzCore                     0x1c534ec1c CA::Context::commit_transaction(CA::Transaction*, double)
14 QuartzCore                     0x1c5379bd8 CA::Transaction::commit()
15 QuartzCore                     0x1c537abc0 CA::Transaction::release_thread(void*)
16 libsystem_pthread.dylib        0x1be62c3c0 _pthread_tsd_cleanup
17 libsystem_pthread.dylib        0x1be624dbc _pthread_exit
18 libsystem_pthread.dylib        0x1be626de8 _pthread_wqthread_legacy_worker_wrap
19 libsystem_pthread.dylib        0x1be626b30 _pthread_wqthread
20 libsystem_pthread.dylib        0x1be62cc78 start_wqthread
Run Code Online (Sandbox Code Playgroud)

我绝对不知道,这个问题会发生什么,我该如何繁殖。它随机崩溃。我在项目中使用Crashlytics v3.14。有人面对同样的问题吗?

Old*_*mes 11

首先我建议打开“主线程检查器”,在 Xcode 中,转到 Product -> Scheme -> Edit scheme -> Diagnostics,你应该看到这个窗口 诊断选项卡 您可以尝试的另一件事是转到 Xcode 中的断点部分,然后单击 + 号并添加一个符号断点,该断点将侦听特定调用,您可以向其添加条件以检查它是否在主线程上被调用。

一个象征性的断点

如果您碰巧在代码中发现了您的错误,请将其发布在这里,因为我在我的应用程序中遇到了与您相同的崩溃,所以这就是我找出错误的程度。希望能帮到你!


Ary*_*yan 6

这个问题可能是由于谷歌广告 SDK(7.5XX + iOS13),发现这个线程

开发人员尝试按照Info.plistGoogle Ads 团队的建议在文件中使用以下密钥对值。

<key>gad_preferred_webview</key>
<string>wkwebview</string>
Run Code Online (Sandbox Code Playgroud)

这减少了崩溃,但这又带来了另一个冻结问题(100% CPU 使用率)。

最近 Google 发布了 7.55.0 并附注:

Removed all references to UIWebView. UIWebView is no longer supported.
Run Code Online (Sandbox Code Playgroud)

所以尝试将 Google 广告 SDK 更新为 7.55.0


小智 5

您的应用程式中启用了Google广告吗?这可能是Google ads sdk中的错误,也可能是iOS 13上的WebKit SDK实施中的错误。(对不起,我无法发表评论,因此我将其发布为答案)

带-通过阅读以上链接的线程,截至2019年11月19日,Google Ads团队的“官方”解决方案是修改您应用的plist,使其包含以下密钥/对,以使用wkwebview而不是uiwebview。

<key>gad_preferred_webview</key>
<string>wkwebview</string>
Run Code Online (Sandbox Code Playgroud)

来源:https//groups.google.com/forum/#!category-topic / google-admob-ads- sdk / ios / I4EEWrPPbSc

  • 这里同样的问题。我仍在等待 Google 的新更新。在当前版本(7.52.0)中此错误仍然存​​在。 (2认同)