firebase-ios-sdk: Crashlytics crash on launch for some users: FIRCLSTerminateHandler() + 344
[REQUIRED] Step 1: Describe your environment
- Xcode version: Version 12.4 (12D4e)
- Firebase SDK version: 7.5.0 (Crashlytics 7.5.0)
- Installation method: CocoaPods
- Firebase Component: Crashlytics
[REQUIRED] Step 2: Describe the problem
I’m seeing a few crashes on launch for what I think are new installs. The crashes are reported through apple since it’s Crashlytics that is crashing.
Steps to reproduce:
I am unsure but am in contact with two testers experiencing the crash. Please let me know if there’s anything else I can provide to help resolve this expediently.
Relevant Code:
Date/Time: 2021-01-29 09:06:39.8052 -0800
Launch Time: 2021-01-29 09:06:38.8331 -0800
OS Version: iPhone OS 14.3 (18C66)
Release Type: User
Baseband Version: 1.31.03-5
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 0
Thread 0 name:
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x00000001d5e0c414 __pthread_kill + 8
1 libsystem_pthread.dylib 0x00000001f3866b40 pthread_kill + 272 (pthread.c:1388)
2 libsystem_c.dylib 0x00000001b1432bf4 __abort + 116 (abort.c:147)
3 libsystem_c.dylib 0x00000001b1432b80 abort + 116 (abort.c:118)
4 libc++abi.dylib 0x00000001bd10acf8 abort_message + 132 (abort_message.cpp:76)
5 libc++abi.dylib 0x00000001bd0fbe4c demangling_terminate_handler() + 308 (cxa_default_handlers.cpp:67)
6 libobjc.A.dylib 0x00000001bd004f64 _objc_terminate() + 144 (objc-exception.mm:701)
7 FirebaseCrashlytics 0x0000000101f900b4 FIRCLSTerminateHandler() + 344 (FIRCLSException.mm:335)
8 libc++abi.dylib 0x00000001bd10a0e0 std::__terminate(void (*)()) + 20 (cxa_handlers.cpp:59)
9 libc++abi.dylib 0x00000001bd10a06c std::terminate() + 44 (cxa_handlers.cpp:88)
10 libdispatch.dylib 0x00000001a7c89dc4 _dispatch_client_callout + 40 (object.m:562)
11 libdispatch.dylib 0x00000001a7c8d738 _dispatch_block_invoke_direct + 268 (queue.c:468)
12 FrontBoardServices 0x00000001b7daa250 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 48 (FBSSerialQueue.m:184)
13 FrontBoardServices 0x00000001b7da9ee0 -[FBSSerialQueue _targetQueue_performNextIfPossible] + 448 (FBSSerialQueue.m:227)
14 FrontBoardServices 0x00000001b7daa434 -[FBSSerialQueue _performNextFromRunLoopSource] + 32 (FBSSerialQueue.m:258)
15 CoreFoundation 0x00000001a801176c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 (CFRunLoop.c:1967)
16 CoreFoundation 0x00000001a8011668 __CFRunLoopDoSource0 + 208 (CFRunLoop.c:2011)
17 CoreFoundation 0x00000001a8010960 __CFRunLoopDoSources0 + 268 (CFRunLoop.c:2048)
18 CoreFoundation 0x00000001a800aa8c __CFRunLoopRun + 824 (CFRunLoop.c:2925)
19 CoreFoundation 0x00000001a800a21c CFRunLoopRunSpecific + 600 (CFRunLoop.c:3242)
20 GraphicsServices 0x00000001bfb0e784 GSEventRunModal + 164 (GSEvent.c:2259)
21 UIKitCore 0x00000001aaa48fe0 -[UIApplication _run] + 1072 (UIApplication.m:3253)
22 UIKitCore 0x00000001aaa4e854 UIApplicationMain + 168 (UIApplication.m:4707)
23 Blackbox 0x0000000101093c08 main + 80 (main.m:14)
24 libdyld.dylib 0x00000001a7cca6b0 start + 4
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 23 (9 by maintainers)
Good-ish news! Was able to narrow down where this crash was coming from and it was my own
@throw NSInternalInconsistencyException;from a bad data recovery state. I’m not sure if Crashlytics is supposed to handle that differently or if I should be throwing a different kind of exception though!You can only download containers of debug builds I think! There were no containers available to download off their device since this is a TestFlight build.