How to interpret crash reports that are not fully symbolized in firebase?

Question

In our application, we use crash analytics in firebase, this helped us quickly resolve errors by specifying the function name and even line numbers, but sometimes it only gives

appDelegate.swift [start + 17644]

How can I request this report? and why does it look like this?

this is a full trace with threads, the application name is replaced with appName

Exception name: EXC_SOFTWARE / UNCAUGHT_NS_EXCEPTION 1 CoreFoundation __exceptionPreprocess + 1241536 2 libobjc.A.dylib objc_exception_throw + 34136 3 CoreFoundation -[__NSPlaceholderDictionary initWithObjects:forKeys:count:] + 80952 4 CoreFoundation +[NSDictionary dictionaryWithObjects:forKeys:count:] + 80552 5 FBSDKCoreKit 4304632780 + 244684 6 FBSDKCoreKit 4304632048 + 243952 7 FBSDKCoreKit 4304437716 + 49620 8 CoreFoundation __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 823848 9 CoreFoundation _CFXRegistrationPost + 821548 10 CoreFoundation ___CFXNotificationPost_block_invoke + 820904 11 CoreFoundation -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1276824 12 CoreFoundation _CFXNotificationPost + 44016 13 Foundation -[NSNotificationCenter postNotificationName:object:userInfo:] + 26152 14 UIKit -[UIApplication _deactivateForReason:notify:] + 491392 15 CoreFoundation __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 823848 16 CoreFoundation ___CFXRegistrationPost_block_invoke + 823692 17 CoreFoundation __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 905564 18 CoreFoundation __CFRunLoopDoBlocks + 903512 19 CoreFoundation __CFRunLoopRun + 896080 20 CoreFoundation CFRunLoopRunSpecific + 36932 21 GraphicsServices GSEventRunModal + 49556 22 UIKit -[UIApplication _run] + 504568 23 UIKit UIApplicationMain + 483376 24 appName main (AppDelegate.swift:18) 25 libdyld.dylib start + 17844 Thread 2 1 libsystem_kernel.dylib mach_msg_trap + 4460 2 libsystem_kernel.dylib mach_msg + 4056 3 CoreFoundation __CFRunLoopServiceMachPort + 904424 4 CoreFoundation __CFRunLoopRun + 895236 5 CoreFoundation CFRunLoopRunSpecific + 36932 6 Foundation -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 51848 7 Foundation -[NSRunLoop(NSRunLoop) runUntilDate:] + 185720 8 UIKit -[UIEventFetcher threadMain] + 10422824 9 Foundation __NSThread__start__ + 1090680 10 libsystem_pthread.dylib _pthread_body + 14412 11 libsystem_pthread.dylib _pthread_start + 14172 12 libsystem_pthread.dylib thread_start + 3496 Thread 3 1 libsystem_kernel.dylib mach_msg_trap + 4460 2 libsystem_kernel.dylib mach_msg + 4056 3 CoreFoundation __CFRunLoopServiceMachPort + 904424 4 CoreFoundation __CFRunLoopRun + 895236 5 CoreFoundation CFRunLoopRunSpecific + 36932 6 CFNetwork +[NSURLConnection(Loader) _resourceLoadLoop:] + 847820 7 Foundation __NSThread__start__ + 1090680 8 libsystem_pthread.dylib _pthread_body + 14412 9 libsystem_pthread.dylib _pthread_start + 14172 10 libsystem_pthread.dylib thread_start + 3496 Thread 4 1 libsystem_kernel.dylib mach_msg_trap + 4460 2 libsystem_kernel.dylib mach_msg + 4056 3 CoreFoundation __CFRunLoopServiceMachPort + 904424 4 CoreFoundation __CFRunLoopRun + 895236 5 CoreFoundation CFRunLoopRunSpecific + 36932 6 Foundation -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 51848 7 Foundation -[NSRunLoop(NSRunLoop) run] + 397836 8 appName +[GAI threadMain:] + 1782640 9 Foundation __NSThread__start__ + 1090680 10 libsystem_pthread.dylib _pthread_body + 14412 11 libsystem_pthread.dylib _pthread_start + 14172 12 libsystem_pthread.dylib thread_start + 3496 Thread 5 1 libsystem_kernel.dylib mach_msg_trap + 4460 2 libsystem_kernel.dylib mach_msg + 4056 3 appName google_breakpad::ExceptionHandler::WaitForMessage(void*) + 2388144 4 libsystem_pthread.dylib _pthread_body + 14412 5 libsystem_pthread.dylib _pthread_start + 14172 6 libsystem_pthread.dylib thread_start + 3496 Thread 6 1 libsystem_kernel.dylib mach_msg_trap + 4460 2 libsystem_kernel.dylib mach_msg + 4056 3 CoreFoundation __CFRunLoopServiceMachPort + 904424 4 CoreFoundation __CFRunLoopRun + 895236 5 CoreFoundation CFRunLoopRunSpecific + 36932 6 GeoServices _runNetworkThread + 4308864 7 libsystem_pthread.dylib _pthread_body + 14412 8 libsystem_pthread.dylib _pthread_start + 14172 9 libsystem_pthread.dylib thread_start + 3496 Thread 7 1 libsystem_kernel.dylib __workq_kernreturn + 129672 2 libsystem_pthread.dylib _pthread_wqthread + 4952 3 libsystem_pthread.dylib start_wqthread + 3488 arrow_drop_down Thread 8 1 libsystem_kernel.dylib __workq_kernreturn + 129672 2 libsystem_pthread.dylib _pthread_wqthread + 4468 3 libsystem_pthread.dylib start_wqthread + 3488 arrow_drop_down Thread 9 1 libsystem_kernel.dylib __workq_kernreturn + 129672 2 libsystem_pthread.dylib _pthread_wqthread + 4952 3 libsystem_pthread.dylib start_wqthread + 3488 Thread 10 1 CoreFoundation> -[__NSDictionaryM countByEnumeratingWithState:objects:count:] + 86492 2 appName +[FIRAEvent normalizedParametersForParameters:isPublicEvent:] + 1999144 3 appName +[FIRAEvent normalizedParametersForParameters:isPublicEvent:] + 1999144 4 appName -[FIRAEvent initWithOrigin:isPublic:name:timestamp:previousTimestamp:parameters:] + 2002028 5 appName +[FIRAnalytics logEventOnSerialQueueWithOrigin:isPublicEvent:name:parameters:timestamp:ignoreEnabled:ignoreInterceptor:addedScreenParameters:] + 2195924 6 appName __65+[FIRAnalytics logEventWithOrigin:isPublicEvent:name:parameters:]_block_invoke_3 + 2195040 7 libdispatch.dylib _dispatch_call_block_and_release + 4604 8 libdispatch.dylib _dispatch_client_callout + 4540 9 libdispatch.dylib _dispatch_queue_serial_drain + 62528 10 libdispatch.dylib _dispatch_queue_invoke + 18852 11 libdispatch.dylib _dispatch_root_queue_drain + 70536 12 libdispatch.dylib _dispatch_worker_thread3 + 69864 13 libsystem_pthread.dylib _pthread_wqthread + 4788 14 libsystem_pthread.dylib start_wqthread + 3488 

Answer 1

Your application crashed due to an exception. Since your data does not show an exception string, it is not known which exception caused the failure.

The exception was caused by a problem in the FBSDKCoreKit structure, which is most likely a third-party SDK for third-party developers. Since you most likely did not load the debug symbols of this Firebase structure, they could not symbolize them and provide the classes and methods called in these frames.

The exception causes a problem with the processing of the NSDictionary object, it may try to insert the nil value for the key, but this is just an assumption.

Once no system frames in the received stack trace originate from your application, Firebase grouped a failure on this call instead of calls in FBSDKCoreKit .

To learn more about these crashes, you need to download the FBSDKCoreKit frame FBSDKCoreKit . With this information it is impossible to find out what the accident is and how to fix it.