Exception Type: EXC_CRASH (SIGABRT)
This shows that your app cashed itself, by calling abort
.
Thread 2 name:
Thread 2 Crashed:
0 libsystem_kernel.dylib … __pthread_kill + 8 (:-1)
1 libsystem_pthread.dylib … pthread_kill + 268 (pthread.c:1668)
2 libsystem_c.dylib … __abort + 128 (abort.c:155)
3 libsystem_c.dylib … abort + 180 (abort.c:126)
4 libc++abi.dylib … abort_message + 132 (abort_message.cpp:78)
5 libc++abi.dylib … demangling_terminate_handler() + 336 (cxa_default_handlers.cpp:71)
6 libobjc.A.dylib … _objc_terminate() + 160 (objc-exception.mm:704)
7 libc++abi.dylib … std::__terminate(void (*)()) + 20 (cxa_handlers.cpp:59)
8 libc++abi.dylib … std::terminate() + 64 (cxa_handlers.cpp:88)
9 libdispatch.dylib … _dispatch_client_callout + 40 (object.m:563)
10 libdispatch.dylib … _dispatch_continuation_pop + 500 (inline_internal.h:2622)
11 libdispatch.dylib … _dispatch_async_redirect_invoke + 584 (queue.c:835)
12 libdispatch.dylib … _dispatch_root_queue_drain + 396 (inline_internal.h:0)
13 libdispatch.dylib … _dispatch_worker_thread2 + 164 (queue.c:6935)
14 libsystem_pthread.dylib … _pthread_wqthread + 228 (pthread.c:2612)
15 libsystem_pthread.dylib … start_wqthread + 8 (:-1)
Frames 8 through 5 indicate that the language runtime called abort
because of an unhandled language exception. This is the backtrace of the code that caught — well, failed to catch — the language exception. What you need is the backtrace of the thread that threw that exception. Crash reports usually include this in a Last Exception Backtrace
section. However, that’s not present here.
That suggests one of two possibilities:
-
You’re using a third-party crash reporter that’s preventing this from showing up. Looking at the rest of your crash report, I don’t think that’s the case.
-
The unhandled language exception was thrown by C++ code. Apple’s crash reporter does not include this section for C++ exceptions. See this thread for the backstory.
I am receiving some crash logs from TestFlight users of my iOS app.
If you can get in touch with this beta tester and ask them for a sysdiagnose log taken shortly after the crash occurs, that may include enough info to debug this.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"