I'm using Touchlab's CrashKiOS to try to view my crashes happening in the KMM module, I'm still not able to view the actual crashes and the stack trace I see on the portal is from Xcode only, i.e., till the KMM interface visible in Xcode. I've located all the dSYMs in the system and added them to the upload script. I'm using the latest version for Crashlytics, i.e., Firebase Crashlytics for the same.

I can recommend another multiplatform lib for this - https://github.com/icerockdev/moko-crash-reporting

If you're running from Xcode and trying to test crashes, Xcode prevents crashes from happening when you're attached to it. This isn't specific to Kotlin. It's true for Swift/Objc dev as well. You'll need to hit "stop" and run the app directly in the simulator.

Hey Kevin, thanks for chiming in. So from what I can understand, every time an exception is thrown from the KMM module, we'll be able to get the stack trace from Kotlin, but not for an unhandled exception? Also, instead of generating a single crash, can we give the Kotlin stack trace for the hard crashes as well?

So from what I can understand, every time an exception is thrown from the KMM module, we'll be able to get the stack trace from Kotlin, but not for an unhandled exception?

Kotlin bubbles up exceptions in a manner similar to Java/JVM. Swift and Objc are different and exception bubbling up isn't as ingrained. If you call a Kotlin method from Swift/Objc, whatever happens after that border happens in "Kotlin land" with Kotlin rules. So, if you call code that throws an exception, you can catch it in Kotlin at any point up until it gets to the border of where you called it from Swift/Objc. If it gets to that point, it's "unhandled". By default, what happens then is the Kotlin runtime tells Swift/objc to abort. If you have Crashlytics set up as usual, you'll get an unhandled exception that will basically say Kotlin called abort. It will look something like this

Thanks a lot for the insights Kevin, resolved my issue.