Hello!
I am having trouble with reading the stack trace on crashlytics for ios app from my KMP library. Is there a way to access the actual kotlin exception that caused the crash? Right now I just see the SIGABRT call...
@brandonmcansh what exactly do you mean with local stack traces? Kotlin prints the unhandeled exception to stdout, so during development you shouldn't need any additional tools to see the stack traces.
l
Landry Norris
02/27/2024, 3:43 PM
Note that other things besides exceptions can cause SIGABRT on iOS. I spent a lot of time trying to find the stacktrace for a SIGABRT in Crashlytics, and it turned out that iOS will raise a SIGABRT if you are doing work on a thread and the app was backgrounded for a few seconds.