getting a <compiler-generated> Crash in crashlytics. However, the user's app on the device does NOT actually crash. Everything works as expected.
Heres is the stack trace: Crashed: com.apple.main-thread 0 DigiDeals 0x33404 specialized Universal.displayMessages() + 4302730244 (<compiler-generated>:4302730244) 1 DigiDeals 0x32840 specialized Universal.displayMessages() + 453 (Universal.swift:453) 2 libswift_Concurrency.dylib 0x4d764 swift::runJobInEstablishedExecutorContext(swift::Job*) + 436 3 libswift_Concurrency.dylib 0x4e9c8 swift_job_runImpl(swift::Job*, swift::ExecutorRef) + 72 4 libdispatch.dylib 0x124b4 _dispatch_main_queue_drain + 748 5 libdispatch.dylib 0x121b8 _dispatch_main_queue_callback_4CF + 44 6 CoreFoundation 0x56710 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 16 7 CoreFoundation 0x53914 __CFRunLoopRun + 1996 8 CoreFoundation 0x52cd8 CFRunLoopRunSpecific + 608 9 GraphicsServices 0x11a8 GSEventRunModal + 164 10 UIKitCore 0x40a90c -[UIApplication _run] + 888 11 UIKitCore 0x4be9d0 UIApplicationMain + 340 12 UIKitCore 0x638384 keypath_get_selector_hoverStyle + 11024 13 DigiDeals 0x4aaf8 main + 4302826232 (AppDelegate.swift:4302826232) 14 ??? 0x1c2bd5e4c (Missing)
the app never crashed on the device
Oh, it most certainly did |-:
It’s possible that the user didn’t notice this crash because the app was in the background at the time, but there’s clear evidence of a crash here. Consider this
Exception Type: EXC_BREAKPOINT (SIGTRAP)
This usually mean that your app trapped, that is, detected a failure case and crashed itself. Typically this comes from the Swift runtime, for example, when you force unwrap an optional that’s nil
or access an array out of bounds.
The crashing thread backtrace is this:
Thread 0 Crashed:
0 DigiDeals … 0x100994000 + 209924
1 DigiDeals … 0x100994000 + 303489
2 DigiDeals … 0x100994000 + 307013
3 DigiDeals … 0x100994000 + 350045
4 DigiDeals … 0x100994000 + 307369
5 libswift_Concurrency.dylib … completeTaskWithClosure(swift::AsyncContext…
It’s hard to say where this crash came from because frames 4 through 0 are not symbolicated. I recommend that you symbolicate the crash report to determine the identity of the crashing code. See Adding identifiable symbol names to a crash report.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"