Hello,
The app is in production/testfilght and I have seen this crash in Xcode Organizer. The highest percentage of such crashes.
It is happening on some of the devices that run iOS 13.0 ~ 13.3.
So I suppose it is happening while lunching the app.
One of the crash reports is on: https://gist.github.com/***7758258/0bdd45007a82003b1e96669ad33b5265
Thread 0 name:
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x00000001944b8634 mach_msg_trap + 8
1 libsystem_kernel.dylib 0x00000001944b7aa0 mach_msg + 72 (mach_msg.c:103)
2 CoreFoundation 0x0000000194660288 __CFRunLoopServiceMachPort + 216 (CFRunLoop.c:2575)
3 CoreFoundation 0x000000019465b3a8 __CFRunLoopRun + 1444 (CFRunLoop.c:2931)
4 CoreFoundation 0x000000019465aadc CFRunLoopRunSpecific + 464 (CFRunLoop.c:3192)
5 GraphicsServices 0x000000019e5fb328 GSEventRunModal + 104 (GSEvent.c:2246)
6 UIKitCore 0x000000019876863c UIApplicationMain + 1936 (UIApplication.m:4773)
7 MYAPP 0x00000001047e8320 main + 152 (main.m:16)
8 libdyld.dylib 0x00000001944e4360 start + 4
Thread 1 name:
Thread 1:
0 libsystem_kernel.dylib … mach_msg_trap + 8
1 libsystem_kernel.dylib … mach_msg + 72 (mach_msg.c:103)
2 libsystem_kernel.dylib … task_threads + 92 (taskUser.c:590)
3 MYAPP … ARS_suspendEnvironment + 128 (ARSCrash_MachException.m:60)
4 MYAPP … __51+[ARS_SeeaxyvkQaaAVDId installMachExceptionHandler]_block_invoke + 280 (ARSCrash_MachException.m:200)
5 libdispatch.dylib … _dispatch_call_block_and_release + 24 (init.c:1408)
…
It looks like you’re using a third-party crash reporter and it’s disrupted the crash state seen by the Apple crash reporter. My recommendation is that you remove the third-party crash reporter and see if that improves the quality of the Apple crash reports, thereby allowing you to debug this problem.
ps I generally recommend against using a third-party crash report. My Implementing Your Own Crash Reporter explains why.
Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"