I keep getting this crash and I have no idea what is causing it. This is the stack trace:
Any help would be appreciated.
Thank you
It’s hard to say what’s going on here because your third-party crash reporter is failing, which means that the Apple crash reporter is unable to generate an accurate crash report.
Consider this:
Thread 0 Crashed:
0 libsystem_kernel.dylib … __pthread_kill + 8 (:-1)
1 libsystem_c.dylib … raise + 32 (raise.c:30)
2 Dynatrace … 0x103bec000 + 945708
3 App … FIRCLSSignalEnumerateHandledSignals + 20 (FIRCLSSignal.c:64)
4 App … FIRCLSSignalSafeInstallPreexistingHandlers + 244 (FIRCLSSignal.c:197)
5 App … FIRCLSSignalHandler + 560 (FIRCLSSignal.c:339)
6 libsystem_platform.dylib … _sigtramp + 56 (sigtramp.c:121)
7 CaptainUp … 0x103980000 + 199540
8 SystemConfiguration … reachPerformAndUnlock + 628 (SCNetworkReachability.c:1473)
Frame 8 shows that SCNetworkReachability is calling a reachability callback in your code. Frame 7 is your code. Frame 6 shows that something in your code has triggered a crash, and thus invoked your third-party crash reporter. Frames 5 through 0 show that the crash reporter itself has crashed.
This is a standard problem with third-party crash reports. I talk about this issue in detail in Implementing Your Own Crash Reporter.
You might be able to make some progress by symbolicating frame 7, but that isn’t a surety. It’s likely that frame 7 called some other routine in your code which then crashed, and that routine is missing from the backtrace due to problems backtracing across signal handler stack frames.
IMO the best option here is to remove your third-party crash reporter. At that point you should start getting crash reports that you can trust.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"