A modern programming language that makes developers happier.

kotlinlang

Screenshot 2023-09-22 at 8.27.37 PM.png

is there any official recommendation/way to get proper stack traces in production build?
without using <https://github.com/rickclephas/NSExceptionKt/tree/master> or crashkit iOS.
use case - we are using own Crash tracker, not firebase or bugsnag

Have a look at <https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.native/set-unhandled-exception-hook.html|https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.native/set-unhandled-exception-hook.html>

The hook lets you step in, but "proper stack traces" can be a complex topic in iOS. I'll actually point back to Rick's code here: <https://github.com/rickclephas/NSExceptionKt/blob/master/nsexception-kt-core/src/commonMain/kotlin/com/rickclephas/kmp/nsexceptionkt/core/NSException.kt#L17|https://github.com/rickclephas/NSExceptionKt/blob/master/nsexception-kt-core/src/c[…]in/kotlin/com/rickclephas/kmp/nsexceptionkt/core/NSException.kt>. In summary, if your crash tracker just gets a stack trace string, that'll be fairly easy. It'll have some info, but not lines numbers, etc. "Proper" tracking requires the pointer addresses, DSYM files, etc.