App Crash

[Saren Inden]

Since the release of iOS 13 with the google mobile ad sdk 7.50.0 we are encountering a lot of crashes (iOS 13 only).

`tryToOptimizeReturningMutuallyExclusiveConstraints`, we do not get any useful stack trace (except from the crash logging part).

But in our paid versions we do not encounter this bug. It occurs on the WebThread. We do not run anything on our self on the webthread so everything seems to point to the mobile ad sdk.

[Juru miyah]

Saya belum paham tentang pesan ini.. bantu saya menemukan solusi dari masalah ini.. terima kasih

[Mobile Ads SDK Forum Advisor Prod]

Hi Saren,

Thank you for raising this to us. Could you provide more context of the issue you've encountered? I'm afraid that it will be difficult for us to proceed with the investigation if no stack trace / logs to look into. It would be much appreciated if you can send a stack trace together with any reproducible test project using Reply privately to author option.

Regards,
Mark Albios
Mobile Ads SDK Team

ref:_00D1U1174p._5001UHI1iH:ref

[Saren Inden]

Annoyingly enough we do not have a way to reproduce this. We mainly see it due to the release by having millions of people using it under x amount of conditions.

The stack trace we got from fabric is also not really helpful I think since (at least as far as I see) there is not a clear origin except that it is from the webthread, the app it self never uses it in our code and it does not occur on the paid version of the app.

It occurs only on iOS 13+.

Thanks for the reply

#8. Crashed: WebThread
0  CRFrameworkAnalytics           0x1036bf5e8 CLSProcessRecordAllThreads + 376 (CLSProcess.c:376)
1  CRFrameworkAnalytics           0x1036bf9d0 CLSProcessRecordAllThreads + 407 (CLSProcess.c:407)
2  CRFrameworkAnalytics           0x1036aee68 CLSHandler + 26 (CLSHandler.m:26)
3  CRFrameworkAnalytics           0x1036bda10 __CLSExceptionRecord_block_invoke + 199 (CLSException.mm:199)
4  libdispatch.dylib              0x192ec6184 _dispatch_client_callout + 16
5  libdispatch.dylib              0x192ea9dd8 _dispatch_lane_barrier_sync_invoke_and_complete + 56
6  CRFrameworkAnalytics           0x1036bd4b8 CLSExceptionRecord + 206 (CLSException.mm:206)
7  CRFrameworkAnalytics           0x1036bd2ec CLSExceptionRecordNSException + 102 (CLSException.mm:102)
8  CRFrameworkAnalytics           0x1036bcf10 CLSTerminateHandler() + 259 (CLSException.mm:259)
9  libc++abi.dylib                0x192fc6304 std::__terminate(void (*)()) + 16
10 libc++abi.dylib                0x192fc5ed8 __cxa_rethrow + 144
11 libobjc.A.dylib                0x192f21258 objc_exception_rethrow + 40
12 CoreFoundation                 0x19317092c CFRunLoopRunSpecific + 576
13 WebCore                        0x19b02a100 RunWebThread(void*) + 612
14 libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
15 libsystem_pthread.dylib        0x192f18aec thread_start + 8
--
Fatal Exception: NSInternalInconsistencyException
0  CoreFoundation                 0x1931f898c __exceptionPreprocess
1  libobjc.A.dylib                0x192f210a4 objc_exception_throw
2  Foundation                     0x1936ced64 -[NSISEngine tryToOptimizeReturningMutuallyExclusiveConstraints]
3  Foundation                     0x1934d9fd4 -[NSISEngine _optimizeWithoutRebuilding]
4  Foundation                     0x1934d9eec -[NSISEngine optimize]
5  Foundation                     0x1934d9b60 -[NSISEngine performPendingChangeNotifications]
6  UIKitCore                      0x19767d880 -[UIView(Hierarchy) layoutSubviews]
7  UIKitCore                      0x197690270 -[UIView(CALayerDelegate) layoutSublayersOfLayer:]
8  QuartzCore                     0x199b7c5f8 -[CALayer layoutSublayers]
9  QuartzCore                     0x199b80e28 CA::Layer::layout_if_needed(CA::Transaction*)
10 QuartzCore                     0x199b8c894 CA::Layer::layout_and_display_if_needed(CA::Transaction*)
11 QuartzCore                     0x199ad59f0 CA::Context::commit_transaction(CA::Transaction*, double)
12 QuartzCore                     0x199aff890 CA::Transaction::commit()
13 QuartzCore                     0x199b00284 CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*)
14 CoreFoundation                 0x193175c48 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__
15 CoreFoundation                 0x193170b34 __CFRunLoopDoObservers
16 CoreFoundation                 0x1931708dc CFRunLoopRunSpecific
17 WebCore                        0x19b02a100 RunWebThread(void*)
18 libsystem_pthread.dylib        0x192f151ec _pthread_start
19 libsystem_pthread.dylib        0x192f18aec thread_start
#0. com.apple.main-thread
0  libsystem_kernel.dylib         0x192ff0c8c __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x192f124e0 _pthread_cond_wait$VARIANT$armv81 + 676
2  JavaScriptCore                 0x1a1d91b2c WTF::ThreadCondition::timedWait(WTF::Mutex&, WTF::WallTime) + 80
3  JavaScriptCore                 0x1a1d77a18 WTF::ParkingLot::parkConditionallyImpl(void const*, WTF::ScopedLambda<bool ()> const&, WTF::ScopedLambda<void ()> const&, WTF::TimeWithDynamicClockType const&) + 2040
4  JavaScriptCore                 0x1a1d6a8b4 WTF::LockAlgorithm<unsigned char, (unsigned char)1, (unsigned char)2, WTF::EmptyLockHooks<unsigned char> >::lockSlow(WTF::Atomic<unsigned char>&) + 232
5  WebCore                        0x19b025b90 _WebThreadLock() + 272
6  WebCore                        0x19b026910 WebThreadLock + 112
7  UIKitCore                      0x1976e4b6c -[UIWebDocumentView _restoreScrollPointForce:] + 72
8  UIKitCore                      0x1976e4eb8 -[UIWebDocumentView _resetForNewPage] + 372
9  UIKitCore                      0x1976e59f8 -[UIWebDocumentView layoutSubviews] + 80
10 UIKitCore                      0x197690270 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 2140
11 QuartzCore                     0x199b7c5f8 -[CALayer layoutSublayers] + 284
12 QuartzCore                     0x199b80e28 CA::Layer::layout_if_needed(CA::Transaction*) + 480
13 QuartzCore                     0x199b8c894 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 136
14 QuartzCore                     0x199ad59f0 CA::Context::commit_transaction(CA::Transaction*, double) + 304
15 QuartzCore                     0x199aff890 CA::Transaction::commit() + 676
16 UIKitCore                      0x19721cb1c __34-[UIApplication _firstCommitBlock]_block_invoke_2 + 80
17 CoreFoundation                 0x193176614 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 20
18 CoreFoundation                 0x193175db4 __CFRunLoopDoBlocks + 264
19 CoreFoundation                 0x193171030 __CFRunLoopRun + 1100
20 CoreFoundation                 0x1931708bc CFRunLoopRunSpecific + 464
21 GraphicsServices               0x19cfdb328 GSEventRunModal + 104
22 UIKitCore                      0x1972056d4 UIApplicationMain + 1936
23 CalculatorForiPadFree          0x10279dfa8 main + 3 (main.swift:3)
24 libdyld.dylib                  0x192ffb460 start + 4
#1. Thread
0  libsystem_kernel.dylib         0x192ff1a74 __workq_kernreturn + 8
1  libsystem_pthread.dylib        0x192f15ff0 _pthread_wqthread + 352
2  libsystem_pthread.dylib        0x192f18ae0 start_wqthread + 8
#2. com.apple.uikit.eventfetch-thread
0  libsystem_kernel.dylib         0x192fcf5f4 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x192fcea60 mach_msg + 72
2  CoreFoundation                 0x193176068 __CFRunLoopServiceMachPort + 216
3  CoreFoundation                 0x193171188 __CFRunLoopRun + 1444
4  CoreFoundation                 0x1931708bc CFRunLoopRunSpecific + 464
5  Foundation                     0x1934b0994 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 228
6  Foundation                     0x1934b0874 -[NSRunLoop(NSRunLoop) runUntilDate:] + 88
7  UIKitCore                      0x19729d49c -[UIEventFetcher threadMain] + 152
8  Foundation                     0x1935e10b0 __NSThread__start__ + 848
9  libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
10 libsystem_pthread.dylib        0x192f18aec thread_start + 8
#3. GAIThread
0  libsystem_kernel.dylib         0x192fcf5f4 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x192fcea60 mach_msg + 72
2  CoreFoundation                 0x193176068 __CFRunLoopServiceMachPort + 216
3  CoreFoundation                 0x193171188 __CFRunLoopRun + 1444
4  CoreFoundation                 0x1931708bc CFRunLoopRunSpecific + 464
5  Foundation                     0x1934b0994 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 228
6  Foundation                     0x1934ea4a8 -[NSRunLoop(NSRunLoop) run] + 88
7  CRFrameworkAnalytics           0x10363923c +[GAI threadMain:] + 241 (GAI.m:241)
8  Foundation                     0x1935e10b0 __NSThread__start__ + 848
9  libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
10 libsystem_pthread.dylib        0x192f18aec thread_start + 8
#4. com.twitter.crashlytics.ios.MachExceptionServer
0  libsystem_kernel.dylib         0x192fcf5f4 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x192fcea60 mach_msg + 72
2  CRFrameworkAnalytics           0x1036a9b58 CLSMachExceptionServer + 180 (CLSMachException.c:180)
3  libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
4  libsystem_pthread.dylib        0x192f18aec thread_start + 8
#5. com.apple.NSURLConnectionLoader
0  libsystem_kernel.dylib         0x192fcf5f4 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x192fcea60 mach_msg + 72
2  CoreFoundation                 0x193176068 __CFRunLoopServiceMachPort + 216
3  CoreFoundation                 0x193171188 __CFRunLoopRun + 1444
4  CoreFoundation                 0x1931708bc CFRunLoopRunSpecific + 464
5  CFNetwork                      0x1963eae68 (Missing)
6  Foundation                     0x1935e10b0 __NSThread__start__ + 848
7  libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
8  libsystem_pthread.dylib        0x192f18aec thread_start + 8
#6. Thread
0  libsystem_kernel.dylib         0x192ff1a74 __workq_kernreturn + 8
1  libsystem_pthread.dylib        0x192f15ff0 _pthread_wqthread + 352
2  libsystem_pthread.dylib        0x192f18ae0 start_wqthread + 8
#7. JavaScriptCore bmalloc scavenger
0  libsystem_kernel.dylib         0x192ff0c8c __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x192f124e0 _pthread_cond_wait$VARIANT$armv81 + 676
2  libc++.1.dylib                 0x1930427a8 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 24
3  JavaScriptCore                 0x1a1dcd3fc void std::__1::condition_variable_any::wait<std::__1::unique_lock<bmalloc::Mutex> >(std::__1::unique_lock<bmalloc::Mutex>&) + 108
4  JavaScriptCore                 0x1a1dd0dcc bmalloc::Scavenger::threadRunLoop() + 200
5  JavaScriptCore                 0x1a1dd0ab4 bmalloc::Scavenger::Scavenger(std::__1::lock_guard<bmalloc::Mutex>&) + 10
6  JavaScriptCore                 0x1a1dd1dc0 std::__1::__thread_specific_ptr<std::__1::__thread_struct>::set_pointer(std::__1::__thread_struct*) + 38
7  libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
8  libsystem_pthread.dylib        0x192f18aec thread_start + 8
#8. Crashed: WebThread
0  CRFrameworkAnalytics           0x1036bf5e8 CLSProcessRecordAllThreads + 376 (CLSProcess.c:376)
1  CRFrameworkAnalytics           0x1036bf9d0 CLSProcessRecordAllThreads + 407 (CLSProcess.c:407)
2  CRFrameworkAnalytics           0x1036aee68 CLSHandler + 26 (CLSHandler.m:26)
3  CRFrameworkAnalytics           0x1036bda10 __CLSExceptionRecord_block_invoke + 199 (CLSException.mm:199)
4  libdispatch.dylib              0x192ec6184 _dispatch_client_callout + 16
5  libdispatch.dylib              0x192ea9dd8 _dispatch_lane_barrier_sync_invoke_and_complete + 56
6  CRFrameworkAnalytics           0x1036bd4b8 CLSExceptionRecord + 206 (CLSException.mm:206)
7  CRFrameworkAnalytics           0x1036bd2ec CLSExceptionRecordNSException + 102 (CLSException.mm:102)
8  CRFrameworkAnalytics           0x1036bcf10 CLSTerminateHandler() + 259 (CLSException.mm:259)
9  libc++abi.dylib                0x192fc6304 std::__terminate(void (*)()) + 16
10 libc++abi.dylib                0x192fc5ed8 __cxa_rethrow + 144
11 libobjc.A.dylib                0x192f21258 objc_exception_rethrow + 40
12 CoreFoundation                 0x19317092c CFRunLoopRunSpecific + 576
13 WebCore                        0x19b02a100 RunWebThread(void*) + 612
14 libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
15 libsystem_pthread.dylib        0x192f18aec thread_start + 8
#9. AVAudioSession Notify Thread
0  libsystem_kernel.dylib         0x192fcf5f4 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x192fcea60 mach_msg + 72
2  CoreFoundation                 0x193176068 __CFRunLoopServiceMachPort + 216
3  CoreFoundation                 0x193171188 __CFRunLoopRun + 1444
4  CoreFoundation                 0x1931708bc CFRunLoopRunSpecific + 464
5  AVFAudio                       0x19fbd0e68 GenericRunLoopThread::Entry(void*) + 156
6  AVFAudio                       0x19fc21df0 CAPThread::Entry(CAPThread*) + 204
7  libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
8  libsystem_pthread.dylib        0x192f18aec thread_start + 8
#10. WebCore: LocalStorage
0  libsystem_kernel.dylib         0x192ff0c8c __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x192f124e0 _pthread_cond_wait$VARIANT$armv81 + 676
2  JavaScriptCore                 0x1a1d91b2c WTF::ThreadCondition::timedWait(WTF::Mutex&, WTF::WallTime) + 80
3  JavaScriptCore                 0x1a1d77a18 WTF::ParkingLot::parkConditionallyImpl(void const*, WTF::ScopedLambda<bool ()> const&, WTF::ScopedLambda<void ()> const&, WTF::TimeWithDynamicClockType const&) + 2040
4  WebKitLegacy                   0x19f03940c bool WTF::Condition::waitUntil<WTF::Lock>(WTF::Lock&, WTF::TimeWithDynamicClockType const&) + 184
5  WebKitLegacy                   0x19f03c040 std::__1::unique_ptr<WTF::Function<void ()>, std::__1::default_delete<WTF::Function<void ()> > > WTF::MessageQueue<WTF::Function<void ()> >::waitForMessageFilteredWithTimeout<WTF::MessageQueue<WTF::Function<void ()> >::waitForMessage()::'lambda'(WTF::Function<void ()> const&)>(WTF::MessageQueueWaitResult&, WTF::MessageQueue<WTF::Function<void ()> >::waitForMessage()::'lambda'(WTF::Function<void ()> const&)&&, WTF::Seconds) + 168
6  WebKitLegacy                   0x19f03b724 WebCore::StorageThread::threadEntryPoint() + 68
7  JavaScriptCore                 0x1a1d8f7a4 WTF::Thread::entryPoint(WTF::Thread::NewThreadContext*) + 256
8  JavaScriptCore                 0x1a1d91314 WTF::wtfThreadEntryPoint(void*) + 12
9  libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
10 libsystem_pthread.dylib        0x192f18aec thread_start + 8
#11. com.apple.CFNetwork.CustomProtocols
0  libsystem_kernel.dylib         0x192fcf5f4 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x192fcea60 mach_msg + 72
2  CoreFoundation                 0x193176068 __CFRunLoopServiceMachPort + 216
3  CoreFoundation                 0x193171188 __CFRunLoopRun + 1444
4  CoreFoundation                 0x1931708bc CFRunLoopRunSpecific + 464
5  CFNetwork                      0x1963eae68 (Missing)
6  Foundation                     0x1935e10b0 __NSThread__start__ + 848
7  libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
8  libsystem_pthread.dylib        0x192f18aec thread_start + 8
#12. IndexedDatabase Server
0  libsystem_kernel.dylib         0x192ff0c8c __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x192f124e0 _pthread_cond_wait$VARIANT$armv81 + 676
2  JavaScriptCore                 0x1a1d91b2c WTF::ThreadCondition::timedWait(WTF::Mutex&, WTF::WallTime) + 80
3  JavaScriptCore                 0x1a1d77a18 WTF::ParkingLot::parkConditionallyImpl(void const*, WTF::ScopedLambda<bool ()> const&, WTF::ScopedLambda<void ()> const&, WTF::TimeWithDynamicClockType const&) + 2040
4  JavaScriptCore                 0x1a1d502d4 bool WTF::Condition::waitUntil<WTF::Lock>(WTF::Lock&, WTF::TimeWithDynamicClockType const&) + 184
5  JavaScriptCore                 0x1a1d5772c WTF::CrossThreadQueue<WTF::CrossThreadTask>::waitForMessage() + 120
6  JavaScriptCore                 0x1a1d57568 WTF::CrossThreadTaskHandler::taskRunLoop() + 296
7  JavaScriptCore                 0x1a1d8f7a4 WTF::Thread::entryPoint(WTF::Thread::NewThreadContext*) + 256
8  JavaScriptCore                 0x1a1d91314 WTF::wtfThreadEntryPoint(void*) + 12
9  libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
10 libsystem_pthread.dylib        0x192f18aec thread_start + 8
#13. com.apple.CoreMotion.MotionThread
0  libsystem_kernel.dylib         0x192fcf5f4 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x192fcea60 mach_msg + 72
2  CoreFoundation                 0x193176068 __CFRunLoopServiceMachPort + 216
3  CoreFoundation                 0x193171188 __CFRunLoopRun + 1444
4  CoreFoundation                 0x1931708bc CFRunLoopRunSpecific + 464
5  CoreFoundation                 0x193171608 CFRunLoopRun + 60
6  CoreMotion                     0x19fa8f64c CLClientCreateIso6709Notation + 149564
7  libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
8  libsystem_pthread.dylib        0x192f18aec thread_start + 8
#14. Thread
0  libsystem_kernel.dylib         0x192ff1a74 __workq_kernreturn + 8
1  libsystem_pthread.dylib        0x192f15ff0 _pthread_wqthread + 352
2  libsystem_pthread.dylib        0x192f18ae0 start_wqthread + 8
#15. Thread
0  libsystem_pthread.dylib        0x192f18ad8 start_wqthread + 190
#16. com.google.fira.worker
0  libsystem_kernel.dylib         0x192ff2424 fsync + 8
1  libsqlite3.dylib               0x194e68ff8 sqlite3_free_table + 63640
2  libsqlite3.dylib               0x194e72b90 sqlite3_randomness + 2404
3  libsqlite3.dylib               0x194e68998 sqlite3_free_table + 62008
4  libsqlite3.dylib               0x194e53f24 sqlite3_value_text + 23504
5  libsqlite3.dylib               0x194e2015c sqlite3_finalize + 3608
6  libsqlite3.dylib               0x194e4c98c sqlite3_step + 60828
7  libsqlite3.dylib               0x194e3dd74 sqlite3_step + 388
8  libsqlite3.dylib               0x194e053e4 sqlite3_exec + 300
9  CRFrameworkAnalytics           0x10376359c -[APMSqliteStore endTransaction] + 37152
10 CRFrameworkAnalytics           0x103763258 -[APMSqliteStore performTransaction:] + 36316
11 CRFrameworkAnalytics           0x10373c9e8 -[APMMeasurement setUserAttributeOnWorkerQueue:] + 159104
12 CRFrameworkAnalytics           0x10374ee7c __51-[APMScheduler scheduleOnWorkerQueueBlockID:block:]_block_invoke + 234004
13 libdispatch.dylib              0x192ec5610 _dispatch_call_block_and_release + 24
14 libdispatch.dylib              0x192ec6184 _dispatch_client_callout + 16
15 libdispatch.dylib              0x192ea373c _dispatch_lane_serial_drain$VARIANT$armv81 + 564
16 libdispatch.dylib              0x192ea4154 _dispatch_lane_invoke$VARIANT$armv81 + 400
17 libdispatch.dylib              0x192ead43c _dispatch_workloop_worker_thread + 576
18 libsystem_pthread.dylib        0x192f15fa4 _pthread_wqthread + 276
19 libsystem_pthread.dylib        0x192f18ae0 start_wqthread + 8
#17. Thread
0  libsystem_kernel.dylib         0x192ff1a74 __workq_kernreturn + 8
1  libsystem_pthread.dylib        0x192f15ff0 _pthread_wqthread + 352
2  libsystem_pthread.dylib        0x192f18ae0 start_wqthread + 8
#18. Thread
0  libsystem_kernel.dylib         0x192ff1a74 __workq_kernreturn + 8
1  libsystem_pthread.dylib        0x192f15ff0 _pthread_wqthread + 352
2  libsystem_pthread.dylib        0x192f18ae0 start_wqthread + 8
#19. Thread
0  libsystem_kernel.dylib         0x192ff1a74 __workq_kernreturn + 8
1  libsystem_pthread.dylib        0x192f15ff0 _pthread_wqthread + 352
2  libsystem_pthread.dylib        0x192f18ae0 start_wqthread + 8
#20. Thread
0  libsystem_kernel.dylib         0x192fcf648 semaphore_timedwait_trap + 8
1  libdispatch.dylib              0x192e97f30 _dispatch_sema4_timedwait$VARIANT$armv81 + 64
2  libdispatch.dylib              0x192e984b8 _dispatch_semaphore_wait_slow + 72
3  libdispatch.dylib              0x192eabf44 _dispatch_worker_thread + 344
4  libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
5  libsystem_pthread.dylib        0x192f18aec thread_start + 8
#21. Thread
0  libsystem_kernel.dylib         0x192fcf648 semaphore_timedwait_trap + 8
1  libdispatch.dylib              0x192e97f30 _dispatch_sema4_timedwait$VARIANT$armv81 + 64
2  libdispatch.dylib              0x192e984b8 _dispatch_semaphore_wait_slow + 72
3  libdispatch.dylib              0x192eabf44 _dispatch_worker_thread + 344
4  libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
5  libsystem_pthread.dylib        0x192f18aec thread_start + 8
#22. Thread
0  libsystem_kernel.dylib         0x192fcf648 semaphore_timedwait_trap + 8
1  libdispatch.dylib              0x192e97f30 _dispatch_sema4_timedwait$VARIANT$armv81 + 64
2  libdispatch.dylib              0x192e984b8 _dispatch_semaphore_wait_slow + 72
3  libdispatch.dylib              0x192eabf44 _dispatch_worker_thread + 344
4  libsystem_pthread.dylib        0x192f151ec _pthread_start + 124
5  libsystem_pthread.dylib        0x192f18aec thread_start + 8

[Mobile Ads SDK Forum Advisor Prod]

Hi All,

@Saren - Thank you for providing additional details of the issue encountered.

In order for me to proceed with my investigation, I'm afraid that I'll be needing a sample project with a reproducible case on this matter. Feel free to send a copy via Reply privately to author once one is available.

Regards,
Mark Albios
Mobile Ads SDK Team

ref:_00D1U1174p._5001UHI1iH:ref

[Craig McMahon]

I'm seeing this issue on iOS 13. As described above, the issue originates in a web thread and only occurs for users who are seeing ads.

[Mobile Ads SDK Forum Advisor Prod]

Hi Craig,

Thank you for adding details to the issue. Could you provide a stack trace / logs and any reproducible test project for me to further investigate? Please send it to me using Reply privately to author option.

Regards,
Mark Albios
Mobile Ads SDK Team

ref:_00D1U1174p._5001UHI1iH:ref

[Mobilekaz]

I'm experiencing the exact same problem, where our app with "normal" (non-paid) users are frequently experiencing the same exact crashes (NSInternalInconsistencyException: NSISEngine tryToOptimizeReturningMutuallyExclusiveConstraints) whereas our "premium" (paid) users are not. One of the major differences is that "normal" users are seeing AdMob ads and "premium" users are not. Unfortunately this seems to happen rather randomly so there's no concrete reproducible code. 

However, when we use symbolic breakpoint in Xcode, we can see that UIWebView may be used from AdMob (GADDispatchAsyncSafeMainQueue?) and this may be causing the problem, because every time this breakpoint is hit, the app crashes when the app goes to the background and then comes back to the foreground. 

Please remove all uses of UIWebView from your ad framework and this problem should go away. We're using Google-Mobile-Ads-SDK version 7.50.0. 

Thanks! 

Kazushi

2019年9月30日月曜日 11時22分32秒 UTC+9 mobileadssdkforumadvisor:

[Johannes Plunien]

We're facing the same issue in the eBay Kleinanzeigen iOS app. No additional information to provide, unfortunately. Stack trace looks exactly the same as the ones the others here already provided.

[Mobile Ads SDK Forum Advisor Prod]

Hi All,

Thank you for sharing additional details of the issue. However, could you provide me with the App ID, and Ad Unit IDs with their Ad Format (Banner, Interstitial, Rewarded, Native) where the issue was encountered using Reply privately to author option so I could investigate this?

[Mobile Ads SDK Forum Advisor Prod]

Hi Robert, Johannes,

Thank you both for providing the requested details in private. I'm Ziv, Mark's colleague, and I will be assisting you both on this one for today, since Mark is currently out-of-office.

I tested both your ad unit IDs with our sample apps, and can confirm that I could not replicate the crash on my end. Kindly see attached screenshots for ads that I was able to load for Robert's ad units. On the other hand, I'm afraid that all of Johannes' ad units failed to load ads for me, though again it did not crash for me at the very least.

I will discuss this concern (and the findings reported thus far) with the rest of the team in order to gather our insights on this, but it would be much appreciated if anyone could send a sample project (with the issue reproduced) to us via Reply privately to author. In the case where one is sent, we can then forward that sample project to the Engineering team, along with all the reports thus far, in order for them to deliver a more decisive resolution to this concern.

Regards,
Ziv Yves Sanchez
Mobile Ads SDK Team

ref:_00D1U1174p._5001UHI1iH:ref

[arken thera]

Hey, we are also experiencing this. Looking at Crashlytics, after updating to AdMob iOS 7.50.0 we started to see this error. We can see this only happens for iOS 13 users and started after we upgraded to AdMob 7.50.0. We can also see that this happens before or after showing an ad but it is 100% related to seeing an ad. I'm posting a stacktrace below. We're seeing 1000~ crash each day. It's a relatively small number considering our DAU but this needs to be fixed ASAP.

Fatal Exception: NSInternalInconsistencyException
0 CoreFoundation 0x1b2dac98c __exceptionPreprocess
1 libobjc.A.dylib 0x1b2ad50a4 objc_exception_throw
2 Foundation 0x1b3282d64 -[NSISEngine tryToOptimizeReturningMutuallyExclusiveConstraints]
3 Foundation 0x1b308dfd4 -[NSISEngine _optimizeWithoutRebuilding]
4 Foundation 0x1b308deec -[NSISEngine optimize]
5 Foundation 0x1b308db60 -[NSISEngine performPendingChangeNotifications]
6 UIKitCore 0x1b7232880 -[UIView(Hierarchy) layoutSubviews]
7 UIKitCore 0x1b7245270 -[UIView(CALayerDelegate) layoutSublayersOfLayer:]
8 QuartzCore 0x1b97315f8 -[CALayer layoutSublayers]
9 QuartzCore 0x1b9735e28 CA::Layer::layout_if_needed(CA::Transaction*)
10 QuartzCore 0x1b9741894 CA::Layer::layout_and_display_if_needed(CA::Transaction*)
11 QuartzCore 0x1b968a9f0 CA::Context::commit_transaction(CA::Transaction*, double)
12 QuartzCore 0x1b96b4890 CA::Transaction::commit()
13 QuartzCore 0x1b96b5284 CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*)
14 CoreFoundation 0x1b2d29c48 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__
15 CoreFoundation 0x1b2d24b34 __CFRunLoopDoObservers
16 CoreFoundation 0x1b2d248dc CFRunLoopRunSpecific
17 WebCore 0x1babdf100 <redacted>
18 libsystem_pthread.dylib 0x1b2ac91ec _pthread_start
19 libsystem_pthread.dylib 0x1b2accaec thread_start

[Mobile Ads SDK Forum Advisor Prod]

Hi Arken,

Thank you for reporting this to us. I understand your concern, same with the other users who encountered the issue. However, I'm afraid that I would be needing a reproducible project for me to proceed with my investigations. Feel free to send a copy of the test project via Reply privately to author once available.

Regards,
Mark Albios
Mobile Ads SDK Team

ref:_00D1U1174p._5001UHI1iH:ref

[Ron Soffer]

We're seeing this as well. AdMob 7.50.0 on iOS 13. Please review any changes that could execute code on background threads.

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.

Fatal Exception: NSInternalInconsistencyException

0  CoreFoundation                 0x1c152498c __exceptionPreprocess

1  libobjc.A.dylib                0x1c124d0a4 objc_exception_throw

2  Foundation                     0x1c19fad64 -[NSISEngine tryToOptimizeReturningMutuallyExclusiveConstraints]

3  Foundation                     0x1c1805fd4 -[NSISEngine _optimizeWithoutRebuilding]

4  Foundation                     0x1c1805eec -[NSISEngine optimize]

5  Foundation                     0x1c1805b60 -[NSISEngine performPendingChangeNotifications]

6  UIKitCore                      0x1c59a9880 -[UIView(Hierarchy) layoutSubviews]

7  Rhymers Block                  0x103680c60 __smartlook_layout_subviews_method + 234 (SLChangesDetector.m:234)

8  UIKitCore                      0x1c59bc270 -[UIView(CALayerDelegate) layoutSublayersOfLayer:]

9  QuartzCore                     0x1c7ea85f8 -[CALayer layoutSublayers]

10 QuartzCore                     0x1c7eace28 CA::Layer::layout_if_needed(CA::Transaction*)

11 QuartzCore                     0x1c7eb8894 CA::Layer::layout_and_display_if_needed(CA::Transaction*)

12 QuartzCore                     0x1c7e019f0 CA::Context::commit_transaction(CA::Transaction*, double)

13 QuartzCore                     0x1c7e2b890 CA::Transaction::commit()

14 QuartzCore                     0x1c7e2c284 CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*)

15 CoreFoundation                 0x1c14a1c48 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__

16 CoreFoundation                 0x1c149cb34 __CFRunLoopDoObservers

17 CoreFoundation                 0x1c149d100 __CFRunLoopRun

18 CoreFoundation                 0x1c149c8bc CFRunLoopRunSpecific

19 WebCore                        0x1c9356100 RunWebThread(void*)

20 libsystem_pthread.dylib        0x1c12411ec _pthread_start

21 libsystem_pthread.dylib        0x1c1244aec thread_start

[Ignazio Calo]

Same problem here. 

About we see ~600 crashes per day on our iOS app with a significant drop in revenue. If this is not solved soon I guess we need to disable the display network and redirect our traffic to other sources.

0  CoreFoundation                 0x1c0189c30 __exceptionPreprocess

1  libobjc.A.dylib                0x1bfea40c8 objc_exception_throw

2  Foundation                     0x1c0675434 -[NSISEngine tryToOptimizeReturningMutuallyExclusiveConstraints]

3  Foundation                     0x1c046eb94 -[NSISEngine _optimizeWithoutRebuilding]

4  Foundation                     0x1c046eaa8 -[NSISEngine optimize]

5  Foundation                     0x1c046e718 -[NSISEngine performPendingChangeNotifications]

6  UIKitCore                      0x1c46b47c4 -[UIView(Hierarchy) layoutSubviews]

7  UIKitCore                      0x1c46c7abc -[UIView(CALayerDelegate) layoutSublayersOfLayer:]

8  libobjc.A.dylib                0x1bfe9faf0 -[NSObject performSelector:withObject:]

9  QuartzCore                     0x1c6c660f4 -[CALayer layoutSublayers]

10 QuartzCore                     0x1c6c663fc CA::Layer::layout_if_needed(CA::Transaction*)

11 QuartzCore                     0x1c6c79964 CA::Layer::layout_and_display_if_needed(CA::Transaction*)

12 QuartzCore                     0x1c6bbec1c CA::Context::commit_transaction(CA::Transaction*, double)

13 QuartzCore                     0x1c6be9bd8 CA::Transaction::commit()

14 QuartzCore                     0x1c6bea7ac CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*)

15 CoreFoundation                 0x1c010467c __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__

16 CoreFoundation                 0x1c00ff31c __CFRunLoopDoObservers

17 CoreFoundation                 0x1c00ff8cc __CFRunLoopRun

18 CoreFoundation                 0x1c00ff098 CFRunLoopRunSpecific

19 WebCore                        0x1c81c2464 <redacted>

20 libsystem_pthread.dylib        0x1bfe94d5c _pthread_start

21 libsystem_pthread.dylib        0x1bfe9cc84 thread_start

[Mobile Ads SDK Forum Advisor Prod]

Hi everyone, 
Thanks for reporting this. We've logged a bug and are investigating. 

ref:_00D1U1174p._5001UHI1iH:ref

[Mobile Ads SDK Forum Advisor Prod]

Hi everyone, 
Looking into the crash logs, we don't see any evidence that this is coming from the Mobile Ads SDK. Can someone provide a stack trace that references a GAD object? Thanks.

Jon

ref:_00D1U1174p._5001UHI1iH:ref

[Mobilekaz]

The problem is, as far as I can tell from our investigation, that the app crashes when the app goes to the background and then comes back to the foreground. Apparently some layout engine kicks in, which causes some view (maybe UIWebView?) to throw an exception and crashes. Hence, the stack trace does not reference any GAD objects. 

However, this bug occurs *every time* UIWebView is created; I confirmed this by using symbolic breakpoint in Xcode and I've seen this happen 20+ times. And the crash did not occur *at all* when UIWebView was not created. So I think there's a pattern that when AdMob loads UIWebView, it causes a crash at some point in the future. 

Here's the timeline of the crash: 

1. App launches

2. App loads AdMob, and AdMob somtimes loads UIWebView to show certain ads

3. User can continue to use the app

4. User swipes up the home indocator to go back to the home screen

5. User can continue to use the home screen

6. When the user brings the app to the foreground, the app crashes

Kazushi

2019年10月3日木曜日 3時04分58秒 UTC+9 mobileadssdkforumadvisor:

[Mobile Ads SDK Forum Advisor Prod]

Hi everyone, 
We are still looking into this. In the mean time, can you please provide (feel free to reply privately if you want) the name of your app in the app store, and the devices that are experiencing the crash (is it all iOS 13 devices or just certain ones?), as well as the ad formats you are using. Thanks. 

ref:_00D1U1174p._5001UHI1iH:ref

[Pablo Martinez]

Hello, we are also having this issue only affecting iOS 13 devices. I hope the library will be updated soon. 

[FantaMaster]

Hi, same problem here. This crash is occurring only on iOS 13 and it appeared when we switched to version 7.50.0 of Google-Mobile-Ads-SDK

[Dekel Maman]

Hey 

Same issue here only iOS13 devices, We're using GoogleMobileAds framework (NOT pod) version "afma-sdk-i-v7.36.0"

App name: Walla!News

Hop it will solve ASAP, we have ~800 crashes per day.

[Dekel Maman]

On my side, it happening with version 7.36.0 so I believe the crash cause because ios13 changes that don't fit the AdMob or vise Versa.

[Niall Watchorn]

Happening here too. iOS 13 only crashing due to 

-[NSISEngine tryToOptimizeReturningMutuallyExclusiveConstraints]

Related to google ad framework. Please fix ASAP, as it's crashing 30 times a day for my app. Very frustrating as it's leading to poor reviews.

N

[Trenìt! support]

Happening here too:

this is the stacktrace:

Fatal Exception: NSInternalInconsistencyException

0  CoreFoundation                 0x19622898c __exceptionPreprocess

1  libobjc.A.dylib                0x195f510a4 objc_exception_throw

2  Foundation                     0x1966fed64 -[NSISEngine tryToOptimizeReturningMutuallyExclusiveConstraints]

3  Foundation                     0x196509fd4 -[NSISEngine _optimizeWithoutRebuilding]

4  Foundation                     0x196509eec -[NSISEngine optimize]

5  Foundation                     0x196509b60 -[NSISEngine performPendingChangeNotifications]

6  UIKitCore                      0x19a6ae880 -[UIView(Hierarchy) layoutSubviews]

7  UIKitCore                      0x19a6c1270 -[UIView(CALayerDelegate) layoutSublayersOfLayer:]

8  QuartzCore                     0x19cbad5f8 -[CALayer layoutSublayers]

9  QuartzCore                     0x19cbb1e28 CA::Layer::layout_if_needed(CA::Transaction*)

10 QuartzCore                     0x19cbbd894 CA::Layer::layout_and_display_if_needed(CA::Transaction*)

11 QuartzCore                     0x19cb069f0 CA::Context::commit_transaction(CA::Transaction*, double)

12 QuartzCore                     0x19cb30890 CA::Transaction::commit()

13 QuartzCore                     0x19cb31284 CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*)

14 CoreFoundation                 0x1961a5c48 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__

15 CoreFoundation                 0x1961a0b34 __CFRunLoopDoObservers

16 CoreFoundation                 0x1961a08dc CFRunLoopRunSpecific

17 WebCore                        0x19e05b100 RunWebThread(void*)

18 libsystem_pthread.dylib        0x195f451ec _pthread_start

19 libsystem_pthread.dylib        0x195f48aec thread_start

[Mike Liu]

Has anyone downgraded to an earlier version of AdMob to see if it resolves the issue? I am seeing this issue on iOS AdMob version 7.50.0

[Craig McMahon]

I have anecdotal reports of two apps using an undocumented AdMob SDK option who do not experience this issue.

They're setting the value of gad_preferred_webview to wkwebview in Info.plist to force the AdMob SDK to use WKWebViews to host ads.

Has anyone else tried this?

[Rizwan Ali]

We are facing same problem as well on iOS 13. We are using GoogleMobileAd SDK 7.40. Now way to reproduce it on our side.
I have attached crash log. 

[Johannes Plunien]

Dear Google,

are your engineers already looking into this, or are you still ignoring us because we cannot deliver a sample project to reproduce the crash?

Cheers,

Johannes

[Johannes Plunien]

Sorry, only noticed now this reply:

> Looking into the crash logs, we don't see any evidence that this is coming from the Mobile Ads SDK. Can someone provide a stack trace that references a GAD object? Thanks.

I'm quite certain that you will never find any GAD in the stack trace. The method that is causing the assert in Apple's code is not not immediately called if you modify some autolayout constraints. It's similar to `setNeedsLayout`. You set it, and then one (or more) run loop iterations later it's being executed.

Cheers,

Johannes

[Johannes Plunien]

> (is it all iOS 13 devices or just certain ones?)

Yes, only happens on iOS 13, on all device types.

[Joel Ekström]

We have the same problem, same SDK.

No, we can't send a sample project. It's happening too seldom to be reliably reproduced. Same thing as the others here, seeing lots of crashes in Crashlytics.

[Pavel Jaoshvili]

Dear Google developers.

Please help us to resolve this problem. More than 2k crashes per day cause bad affect on our app.

среда, 16 октября 2019 г., 14:03:29 UTC+3 пользователь Joel Ekström написал:

[Trenìt! support]

Same here,

we published an update this week and we see a growing number of crashes on iOS 13 (no crashes on iOS 12)

please Google Devs, this bug has been going on for too long

we think it's about the time to get it fixed

[Kevin Chau]

Also getting crashes here, iOS 13 only. No pattern in logs.

[Patrick]

We too were seeing the crash at a very high rate. We removed Ad Mob completely from our product in order to isolate the problem and we have not had one instance of the crash since.

[Jordan Guggenheim]

We are seeing this as well in large quantities at scale. Can the Google team please acknowledge that this bug is being investigated and let us know what else you need from us? From our own iOS 13 WKWebView troubleshooting (unrelated to GAD) we have had to wrap calls to WKWebView functions to successfully prevent crashes that appear similar to this one. Thank you.

[Raj Doshi]

We're seeing the same crash on iOS 13. It happened when we updated the SDK to 7.50.0 and started building with the iOS 13 SDK. I hope there's a fix soon.

[Zhao Wang]

Hi Craig, 

Thanks for posting this tip here. I actually tried it but I still get one crash while testing. So this does not work for me. 

Are you building your app with iOS 13 SDK or iOS 12 SDK?  We are building with iOS 13 SDK and it crashes, but if we build with iOS 12 SDK, it does not. 

Thanks.

[Zhao Wang]

Besides totally removing AdMobs from the project, the only working solution for me is to build the app using iOS 12 SDK with Xcode 10.3. I tried and put app into production, then no single crash ever happened. Before we have many crashes daily

[Xcoder]

We can confirm the observation from the others: These crashes only occur on iOS 13 and only when using AdMob (we have several paid apps without ads and zero such crashes there).

While looking through the crash logs we observed in a lot (but not all) that one of the background threads involves GADSQLStorage. This is NOT the thread directly causing the crash but it seems to be a frequent pattern that one of the background threads is in [GADSQLStorage writeUpdatedValues]_block_invoke. See excerpt below.

Hope this helps Google to track down the issue and soon release a hotfix.

---

Application Specific Information:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Modifications to the layout engine must not be performed from a background thread after it has been accessed from the main thread.'

Last Exception Backtrace:
0   CoreFoundation                       0x000000018e94098c __exceptionPreprocess + 220
1   libobjc.A.dylib                      0x000000018e6690a4 objc_exception_throw + 52
2   Foundation                           0x000000018ee16d64 _AssertAutolayoutOnAllowedThreadsOnly + 316
3   Foundation                           0x000000018ec21fd4 -[NSISEngine _optimizeWithoutRebuilding] + 64
4   Foundation                           0x000000018ec21eec -[NSISEngine optimize] + 108
5   Foundation                           0x000000018ec21b60 -[NSISEngine performPendingChangeNotifications] + 108
6   UIKitCore                            0x0000000192dc6880 -[UIView(Hierarchy) layoutSubviews] + 304
7   UIKitCore                            0x0000000192dd9270 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 2136
8   QuartzCore                           0x00000001952c55f8 -[CALayer layoutSublayers] + 280
9   QuartzCore                           0x00000001952c9e28 CA::Layer::layout_if_needed(CA::Transaction*) + 476
10  QuartzCore                           0x00000001952d5894 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 132
11  QuartzCore                           0x000000019521e9f0 CA::Context::commit_transaction(CA::Transaction*, double) + 300
12  QuartzCore                           0x0000000195248890 CA::Transaction::commit() + 672
13  QuartzCore                           0x0000000195249284 CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*) + 88
14  CoreFoundation                       0x000000018e8bdc48 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 28
15  CoreFoundation                       0x000000018e8b8b34 __CFRunLoopDoObservers + 412
16  CoreFoundation                       0x000000018e8b88dc CFRunLoopRunSpecific + 492
17  WebCore                              0x0000000196773100 RunWebThread(void*) + 608
18  libsystem_pthread.dylib              0x000000018e65d1ec _pthread_start + 120
19  libsystem_pthread.dylib              0x000000018e660aec thread_start + 4

Thread 5 Crashed:
0   libsystem_kernel.dylib               0x000000018e738ebc __pthread_kill + 8
1   libsystem_c.dylib                    0x000000018e5a8824 abort + 96
2   MyAppCodeReplacedHere                0x0000000104931a94 uncaught_exception_handler + 68
3   CoreFoundation                       0x000000018e940c94 __handleUncaughtException + 632
4   libobjc.A.dylib                      0x000000018e66934c _objc_terminate() + 108
5   MyAppCodeReplacedHere                0x00000001049138f8 MSCrashesUncaughtCXXTerminateHandler() (MSCrashesCXXExceptionHandler.mm:160)
6   libc++abi.dylib                      0x000000018e70e304 std::__terminate(void (*)()) + 12
7   libc++abi.dylib                      0x000000018e70ded8 __cxa_rethrow + 140
8   libobjc.A.dylib                      0x000000018e669258 objc_exception_rethrow + 36
9   CoreFoundation                       0x000000018e8b892c CFRunLoopRunSpecific + 572
10  WebCore                              0x0000000196773100 RunWebThread(void*) + 608
11  libsystem_pthread.dylib              0x000000018e65d1ec _pthread_start + 120
12  libsystem_pthread.dylib              0x000000018e660aec thread_start + 4



Thread 12:
0   libsystem_kernel.dylib               0x000000018e73a424 fsync + 8
1   libsqlite3.dylib                     0x00000001905b1ae0 sqlite3_free_table + 62332
2   libsqlite3.dylib                     0x000000019059cf24 sqlite3_value_text + 23500
3   libsqlite3.dylib                     0x000000019056915c sqlite3_finalize + 3604
4   libsqlite3.dylib                     0x0000000190595fc0 sqlite3_step + 62412
5   libsqlite3.dylib                     0x0000000190586d74 sqlite3_step + 384
6   MyAppCodeReplacedHere                0x0000000104b5328c __35-[GADSQLStorage writeUpdatedValues]_block_invoke.77 (GADSQLStorage.m:236)
7   CoreFoundation                       0x000000018e98dea4 __NSDICTIONARY_IS_CALLING_OUT_TO_A_BLOCK__ + 12
8   CoreFoundation                       0x000000018e81767c -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 204
9   MyAppCodeReplacedHere                0x0000000104b530d4 -[GADSQLStorage writeUpdatedValues] (GADSQLStorage.m:214)
10  libdispatch.dylib                    0x000000018e60d610 _dispatch_call_block_and_release + 20
11  libdispatch.dylib                    0x000000018e60e184 _dispatch_client_callout + 12
12  libdispatch.dylib                    0x000000018e5eb73c _dispatch_lane_serial_drain$VARIANT$armv81 + 560
13  libdispatch.dylib                    0x000000018e5ec154 _dispatch_lane_invoke$VARIANT$armv81 + 396
14  libdispatch.dylib                    0x000000018e5f543c _dispatch_workloop_worker_thread + 572
15  libsystem_pthread.dylib              0x000000018e65dfa4 _pthread_wqthread + 272
16  libsystem_pthread.dylib              0x000000018e660ae0 start_wqthread + 4
---

[Gavin Finden]

It's amazing how this has been an issue for as long as it has been now (this thread was started 3 weeks ago) without any solutions or answers from Google as yet. It's clear from everything that's been posted that this is an issue with either UIWebView or the SDK's use and handling of it.

Please release an update that eliminates use of UIWebView, or do a thorough code review of any and all code that touches UIWebView to ensure that everything is being done properly. Check which threads that code will execute on to ensure that anything that must execute on the main thread is doing so. This shouldn't be that hard for your team to troubleshoot and fix. And until I see reports of UIWebView usage outside of the Google Mobile Ads SDK causing crashes on iOS 13 when built with Xcode 11, I believe that this is an issue specific to your SDK, and you guys should be doing everything in your power to fix this issue as quickly as possible.

Also please provide a useful update to us on the current status. Have you managed to repro it? Do you have any consistent repro steps? Have you a clue what's going on?

[Kevin Chau]

Unfortunately waiting for a fix from Google is my only option right now. I explored building my app on Xcode 10.3, but I would waste a lot of time trying to deal with a bitcode mismatch and which pod is causing it, turning off Bitcode is too much of a compromise.

This should be a high priority issue.

[Mobile Ads SDK Forum Advisor Prod]

Hi everyone, 
Can you confirm if this is happening after setting "gad_preferred_webview" = "wkwebview" in your info.plists? We are still investigating the issue. Thanks.

Jon

ref:_00D1U1174p._5001UHI1iH:ref

[Kevin Chau]

Hi Jon,

Zhao Wang above reported that he was still able to produce a crash. https://groups.google.com/d/msg/google-admob-ads-sdk/PuHOKMX1mVI/xe5unDikAAAJ

[Gavin Finden]

Jon,

It sounded like this was potentially tied to the app being backgrounded, perhaps at a very specific moment, according to at least one of the earlier posts. Do you guys have any notification observers for when the app is moving into the background or back into the foreground that are potentially being executed on a background thread? Or anything else that might trigger unusual behavior during app backgrounding and foregrounding?

[Saren Inden]

You can see with the analyzer that just including and initialising the sdk causes mutlitple webviews to be loaded. That should just not occur if the wkwebview is available.

We are going to test the "gad_preferred_webview" = "wkwebview" part and see if it makes a difference in our apps.

I think it is strange that you have to add that key btw, it should default to the latest/none deprecated version and be more like an override to force an older version (like the UIWebView) if you want that for some reason.

[Bob der Baumeister]

Just in this moment cocoapods loaded an update of this library. Release notes still missing.

% pod update

Update all pods

Updating local specs repositories

Analyzing dependencies

Downloading dependencies

Installing Google-Mobile-Ads-SDK 7.51.0 (was 7.50.0 and source changed to `https://cdn.cocoapods.org/` from `trunk`)

[FantaMaster]

Did anyone have the chance to release an update with this version (7.51.0) of the SDK? Does the crash still occur? Thanks

[GMG Mobile]

We're facing the same issue in our iOS app. No additional information to provide, unfortunately. Stack trace looks exactly the same as the ones the others here already provided.

We went live with "7.51.0" but still getting the same crash. Please resolve ASAP.

[Gavin Finden]

Has anyone been able to confirm yet if adding the "gad_preferred_webview" change fixes the crash?

Really, this shouldn't be that hard to get fixed, especially since Google should have access to a fair amount of crash information, and should be able to invest a decent amount in testing resources...

[Ignazio Calo]

sorry to disappoint you, but the gad_preferred_webview didn't fix the crash for us. 

And -based on the previous message- neither the update to 7.51.0 

[Daniel Garbien]

7.51.0 and gad_preferred_webview enforcing WKWebView doesn't help.

Cars-free stats dropped below 99%. We see more than 5k crashes a day. 

[Gavin Finden]

It appears that even when using this flag in the Info.plist file, the SDK is still initializing UIWebViews, but only on the first launch after adding the flag. Subsequent launches seem to not use them anymore. This is on 7.50.0, haven't tested out 7.51.0.

Can someone who has released an update either with the flag added to their Info.plist and/or used the new SDK version confirm if their crashes have begun to drop off as more users have used the app? Or do they remain high, and show multiple crashes for individual users on the new version?

Also, for anyone seeing crashes from either using this flag or when using 7.51.0, is the crash identical to the previous one, or is it different?

[Daniel Garbien]

Gavin, you might be right. With 7.51.0 and the gad_preferred_webview flag I see crash to user rate is now 1:1 and there is less of them.

And the crash is identical.

[Calo, Ignazio]

From our crash-report we see this weird curve. The purple one is the release with the gad_preferred_webview. It crashed a lot on the first days after the release, then went down.
I can read this in two ways:
- Google fixed something on their backend, switching on/off some A/B test or similar thing.
- The crash happens only on *very first run* of the app, then the SDK starts using the WKWebView and therefore no crashes.

 

 

So from what I can see, the gad_preferred_webview is a good option to mitigate the crash.

 

 

 

--

Ignazio

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/PuHOKMX1mVI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/89e67c3f-ef1b-4cd9-b13d-f89cf5c20bc5%40googlegroups.com.

[Pasquale Puzio]

Good to know.

Thank you for the helpful feedback.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/C85B184C-69A6-4977-8F9E-F1188AE67EEE%40ebay.com.

--

Pasquale Puzio

[Gavin Finden]

Thank you, that is super helpful!

To unsubscribe from this group and all its topics, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.

[FantaMaster]

For the record, I confirm what has been said so far: by using the undocumented gad_preferred_webview setting, the number of crashes has significantly dropped. It doesn't solve the issue but it helps to mitigate the impact :)

[Vasco]

How is it possible that after more than 1 month with so many developers and end-users involved that Google still hasn't fixed it?

[Mike Liu]

This is my biggest crasher. Seems like it is happening on older app versions so probably something that changed on the server side, and can be fixed on server side.

[Kenny Ackerson]

Please please please someone from Google advise us what to do here. 

It's causing 2% of my app's sessions to crash, affecting many many thousands.

I am going to have to pull Admob from the app if this continues.

Please....

[Nikunj Gabani]

I am having the same issue only for iOS 13 users.

And it is causing the app badly.

Google, please do something asap.

[Anton V]

It happens also in my apps (hundreds crashes per days, iOS 13 only, 7.51.0 SDK, in all cases after app goes to the background and then comes back).

[Jesse lin]

Thank you for the helpful feedback!
We released new version with gad_preferred_webview on Nov 4.

It still has crashes, but a large number of crashes has dropped.

[Saalis Umer]

@Jesse, Is the Google Mobile Ads SDK 7.52.0 fixes the issue?

[FantaMaster]

Feedback on 7.52.0 would be greatly appreciated! :) Thanks

[Jaap]

Issue still there on 7.52.0 and setting gad_preferred_webview 

[Jaap]

Any update, Google? Impact is huge, to many developers!!

[TJ]

We're experiencing this as well, affecting a large segment of our users and growing every day as iOS 13 continues to be adopted.

Really hanging out for a fix here.

[Saalis Umer]

The issue remains even with SDK version 7.52.0

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/PuHOKMX1mVI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/adb6b3fa-f5e5-4e06-9b46-a8706eb3d6e3%40googlegroups.com.

--------DISCLAIMER---------

"IMPORTANT: The contents of this e-mail are confidential, private and may be legally privileged, and are intended solely for the addressee mentioned in the mail. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of Inshorts or its affiliates. If you have received this e-mail accidentally or otherwise, kindly notify and return the same to the sender and delete any copy from your system forthwith. Any unauthorised retention, viewing, disclosure or circulation of the same is prohibited and may render you culpable. Copyright in this e-mail and attachments created belongs to sender of this e-mail and the author also asserts the right to be identified as such and object to any misuse."

------------------------

[Wai Hoow Swee]

iOS 13 has been released for over 2 months, still @google is not fixing this crash issue. Guys, come on...

[XT]

Hi Jon,

Any update on this issue? I understand it might not be easy to debug, but to be honest it's a bit disappointing that there has been no communication from Google for a whole month now considering the very high number of crashes the SDK appears to be causing.

Thank you

On Thursday, October 17, 2019 at 5:38:56 PM UTC-4, mobileadssdkforumadvisor wrote:

Hi everyone, 
Can you confirm if this is happening after setting "gad_preferred_webview" = "wkwebview" in your info.plists? We are still investigating the issue. Thanks.

Jon

ref:_00D1U1174p._5001UHI1iH:ref

[Anton V]

Google responded here: https://groups.google.com/forum/#!category-topic/google-admob-ads-sdk/ios/I4EEWrPPbSc

Basically that means that each developer has to either accept iOS 13 crashes (which will likely to grow) or stick to WkWebView and accept the fact that it will affect user experience (users will listen to ads music/sounds even if they don't want to (muted sounds using hardware switch))

Not sure what is the best options for my users... but I had many complaints and 1 star reviews in the past that they couldn't disable sounds generated by ads

For me the crash happens always when app goes to the foreground when a user resumes the app activity. So they simply need to open the app again after crash, and according to Crashlytics it's not happening while user is interacting with the app. Not too bad comparing to the WkWebView option when users suddenly hear unwanted loud music.

Disappointing news...

[Saren Inden]

Real 'nice' that solution,. not!

Are ad income took a severe hit on the interstitial part when we went from WKWebView, so you are stuck on losing a part of your income or have a crashing app.
They also locked that thread so you cannot reply with any complaints or issues about their proposed solution...

[Trenìt! support]

Maybe it's time to move away from AdMob

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/PuHOKMX1mVI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/e521de0d-52d4-4547-8e9f-cc85755e342b%40googlegroups.com.

[Mark Riley]

Basically that means that each developer has to either accept iOS 13 crashes (which will likely to grow) or stick to WkWebView and accept the fact that it will affect user experience (users will listen to ads music/sounds even if they don't want to (muted sounds using hardware switch))

Not sure what is the best options for my users... but I had many complaints and 1 star reviews in the past that they couldn't disable sounds generated by ads

Why would you not be able to disable/turn down the sound using WkWebView? The hardware buttons on the device still control the volume do they not... 

[bellissimo]

Ah, just spotted the link to the Radar. That specifically refers to the mute button, but does this also affect the volume being turned down as well?

[Saalis Umer]

If the video ads are loaded with muted state, it should work irrespective of the hardware mute button? Isn't it?

On Wed, Nov 20, 2019 at 7:57 PM bellissimo <doogl...@gmail.com> wrote:

Ah, just spotted the link to the Radar. That specifically refers to the mute button, but does this also affect the volume being turned down as well?

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/PuHOKMX1mVI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/bd037a4c-a2e4-49b2-84a6-80bb0a0d14ba%40googlegroups.com.

[Mobile Ads SDK Forum Advisor Prod]

Hi everyone, 
We appreciate your patience. The official guidance can be found here: 
https://groups.google.com/forum/#!category-topic/google-admob-ads-sdk/ios/I4EEWrPPbSc
It's up to you to choose between the two approaches. Thank you.

[Saalis Umer]

It does mitigate the issue considerably for me with sdk v7.52.0 but still doesn't fix it completely.

[Waleed nour]

This solution causes huge decreae in Show rate percentage we lost revenu 

On Thursday, October 17, 2019 at 11:38:56 PM UTC+2, mobileadssdkforumadvisor wrote:

Hi everyone, 
Can you confirm if this is happening after setting "gad_preferred_webview" = "wkwebview" in your info.plists? We are still investigating the issue. Thanks.

[Trenìt! support]

It makes no sense that Google would keep this library crashing. Google must find a solution to avoid this crash, whichever is developer-side setting.

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/PuHOKMX1mVI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/95135255-2dad-47b9-921b-30f1803e225d%40googlegroups.com.

[Rob MacEachern]

@mobileadssdkforumadvisor We recently updated our `MoPub-AdMob-Adapters` pod from 7.44.0 to 7.50.0.1 (which depend on the corresponding Google-Mobile-Ads-SDK versions) and started experiencing this crash. It seems likely that a change in between 7.44 and 7.50 is causing this issue and not a change on Apple's end.

We're going to revert back to 7.44 until this is sorted out.

On Sunday, November 24, 2019 at 6:59:55 AM UTC-6, Trenìt! support wrote:

It makes no sense that Google would keep this library crashing. Google must find a solution to avoid this crash, whichever is developer-side setting.

Il sab 23 nov 2019, 12:33 Waleed nour <noor...@gmail.com> ha scritto:

This solution causes huge decreae in Show rate percentage we lost revenu 

On Thursday, October 17, 2019 at 11:38:56 PM UTC+2, mobileadssdkforumadvisor wrote:

Hi everyone, 
Can you confirm if this is happening after setting "gad_preferred_webview" = "wkwebview" in your info.plists? We are still investigating the issue. Thanks.

Jon

ref:_00D1U1174p._5001UHI1iH:ref

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/PuHOKMX1mVI/unsubscribe.

To unsubscribe from this group and all its topics, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.

[Peter Smith]

Some of my notes (I'm not Google, just an app dev).

The official post further up the thread on how to resolve has worked well for me.

Only some of my apps are affected really badly by this crash. It seems for me that the *smaller* the memory footprint of the app, the more often this crash occurs. I have had to switch to WkWebView in only one app where it was getting towards 2% of sessions crashing. I suspect for *larger* memory footprint apps, more graphical, the app is swapped out of memory completely more often, so the app completely restarts and causes the crash to occur less often.

I've found that when I issue an update to an app (without using the WkWebView flag) the crash count drops, but only temporarily. I suspect that when the app is updated on the device and the backgrounded  app is restarted it temporarily mitigates the memory issue leading to the crash.

It does seem pretty clear that because there are no GAD objects in the stack trace, and it only shows up on iOS13 that the root cause is not a Google issue. I believe that if this was a Google resolvable issue, then the same code would cause a crash on earlier versions of iOS as well. Also, as reported earlier in the thread the issue also occurs on very much older versions of Admob on iOS13, it isn't something that has been introduced recently.

I've found that using WkWebView has not completely resolved the issue, but reduced them to an acceptable level. However another issue shows up that is an error in Webkit yet to be resolved where the log fills up with Process Killed messages- the app itself is unaffected - this is also a known issue with WKWebView, app review didn't seem to mind. Also mentioned further up the thread that WkWebView doesn't respond to the mute switch, I have had no complaints yet. I also found that using WKWebView has removed a small number of some strange UIWebView crashes that I had been seeing for a long time.

My 2 cents. YMMV.

[Jin Wang]

Are you joking Google? You're not supposed to work around this issue. You should stop using UIWebView completely and removing it from your SDK. UIWebView has been officially deprecated on iOS 13 (source https://developer.apple.com/documentation/uikit/uiwebview) and Apple is complaining when we submit our binary with UIWebView references. Adding a settings in the info.plist doesn't completely solve this issue as others have suggested. Please make a sensible choice here and provide us with a viable solution!

[Markus Möller]

We're having this crash too with 2-3% of our users and also only in the app version that uses Google Ads. And only with iOS 13.

[Creative Domar]

How to add my admob in my free wordpress site

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/6674ca54-1302-4e38-adc5-14768d83add7%40googlegroups.com.

[Creative Domar]

https://obujhontor.wordpress.com/%e0%a6%a1%e0%a7%8b%e0%a6%ae%e0%a6%be%e0%a6%b0/

On Dec 3, 2019 1:56 PM, "Creative Domar" <obujh...@gmail.com> wrote:

How to add my admob in my free wordpress site

On Dec 3, 2019 1:54 PM, "Markus Möller" <m.mo...@radio.net> wrote:

We're having this crash too with 2-3% of our users and also only in the app version that uses Google Ads. And only with iOS 13.

On Thursday, September 26, 2019 at 10:39:31 AM UTC+2, Saren Inden wrote:

Since the release of iOS 13 with the google mobile ad sdk 7.50.0 we are encountering a lot of crashes (iOS 13 only).

`tryToOptimizeReturningMutuallyExclusiveConstraints`, we do not get any useful stack trace (except from the crash logging part).

But in our paid versions we do not encounter this bug. It occurs on the WebThread. We do not run anything on our self on the webthread so everything seems to point to the mobile ad sdk.

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsubscrib...@googlegroups.com.

[AppA11y]

Is a real fix coming for this? It is effecting a ton of users.

[Saalis Umer]

The fix given as of now is effective in reducing crashes by 90%.

--

---

You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/PuHOKMX1mVI/unsubscribe.

To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/53d6975d-a815-4c94-9927-3e9e0f3434e9%40googlegroups.com.

[Anton V]

Is there any negative impact on revenue / show rate / etc when implementing 'WkWebView' fix?

On Saturday, December 7, 2019 at 7:23:35 PM UTC+11, Saalis Umer wrote:

The fix given as of now is effective in reducing crashes by 90%.

On Sat, Dec 7, 2019 at 7:18 AM AppA11y <nick....@pangiaconsulting.com> wrote:

Is a real fix coming for this? It is effecting a ton of users.

On Thursday, September 26, 2019 at 1:39:31 AM UTC-7, Saren Inden wrote:

Since the release of iOS 13 with the google mobile ad sdk 7.50.0 we are encountering a lot of crashes (iOS 13 only).

`tryToOptimizeReturningMutuallyExclusiveConstraints`, we do not get any useful stack trace (except from the crash logging part).

But in our paid versions we do not encounter this bug. It occurs on the WebThread. We do not run anything on our self on the webthread so everything seems to point to the mobile ad sdk.

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/PuHOKMX1mVI/unsubscribe.

To unsubscribe from this group and all its topics, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/53d6975d-a815-4c94-9927-3e9e0f3434e9%40googlegroups.com.

[XT]

Dunno whether it's a coincidence, reporting bug, or something else, but the show rate in my app dropped by ~10% after the WKWebView fix and hasn't gone up since then. It's been just over a week since I implemented it.

[David Liu]

I'm wondering if this crash still occurs for the latest iOS SDK 7.53.0?

[AppA11y]

We are waiting for Google to chime in on this as well.  No mention in release notes.

[Daigo Sato]

I am having the same problem. The choice between crash or income sounds pretty harsh. We want to be informed for proper fix. 

[bellissimo]

On Tuesday, December 17, 2019 at 10:56:03 AM UTC, Daigo Sato wrote:

I am having the same problem. The choice between crash or income sounds pretty harsh. We want to be informed for proper fix. 

There is no reason why switching to WKWebView would affect your ad income. It is just using a different piece of UI and would have no affect on the underlying bids, the amount of ads shown or the fill rate as they are not linked in any way,

The main downside I can see is that the mute button will no longer have any affect, which could lead to a small increase in negative reviews. 

[bellissimo]

Saying that though, just because this is not crashing in the AdMob code does not mean that they cannot 'fix' it still. I have had a few instances where I have had seemingly 'unexplainable' crashes, which eventually I linked back to my code in some way. Once the link is established (however indirect) then workarounds can usually be found.  

The problem is really that the crash is not easily reproducible, although seems to be related to backgrounding the app while an ad is showing. If someone can come up with a reasonably reliable reproduction scenario then a fix may well be possible.

[Anton V]

Well... if effect of irrespective mute button exists, it does affect revenue, but not directly :  

Increasing number of unhappy customers leads to

- lower retention rate (less revenue in long term)

- more users will decide to turn the ads off (less revenue for their consecutive sessions, unless app can't work offline)

- more negative reviews - lower probability a new user downloads the app as they often read the recent ones --> lower revenue

- possible effect of keyword rankings (in case when ratings play any effect)

p.s. don't wait for a fix from Google. If you contact them directly, they'll tell you they're not going to do anything about it as 'solution' is already provided.   It's just about decision whether you want less crashes for your app or less revenue.

p.p.s. it's difficult to conclude now whether switching to WkWebView has any impact or not, as we are in the Christmas period when RPM, clicks, impressions, etc go up.

[bellissimo]

It would be very hard to say for sure what the effect is of switching. In my experience, negative reviews for things like this are likely to be few and far between, especially if you have a good support channel and an otherwise useful/enjoyable app. People already leave negative reviews for loud ads anyway, even though they can mute it. And they can still turn the volume down with WKWebView, so the problem is fairly limited.

Also, if it is a good app, they may be more likely to upgrade the app to get rid of the ads. This could offset any (possibly minor) decrease in retention or a handful of negative reviews which you may have got anyway. 

I guess my point is, it is basically guesswork what the impact would be. Ad revenue fluctuates for many reasons, and a drop in revenue after switching proves nothing. Personally I think the impact would be minor, but I would just keep an eye on the reviews. You can always switch back after all.