-
Notifications
You must be signed in to change notification settings - Fork 566
Wrong K/N stack trace in debug iOS framework #3234
Comments
Have you enabled rebuild from bitcode when uploading to AppStore? |
I haven't upload this project to AppStore yet. Bitcode for the iOS project is disabled. I took a dSym file for the iOS project from DerivedData/etc../ and uploaded it to Crashlytics. Is it should be enough to show a good stack trace? Or I have to upload it to appstoreconnect first (actually I don't see any reason why)? |
Yes.
Please ensure that you can manually symbolicate crash log, e.g.
You should get properly symbolicated stack trace, and verbose output should contain |
MATCH line contains path to dSym I am using for KN.
There is stack trace I got:
It looks better (I can figure out what kind of exception happened), but some function's names is still unavailable. |
So Crashlytics appears to ignore "Last Exception Backtrace" of the crash, reporting terminating thread backtrace instead.
Could you provide an example? |
In backtrace 3d and 4th lines:
Ok, got it. Is there any ways to handle it? |
What's wrong with 3rd line?
This is likely a bridge, it is not supposed to be decrypted.
Consider reporting unhandled Kotlin exception to Crashlytics explicitly. Unhandled exception can be detected using https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.native/set-unhandled-exception-hook.html |
Typo, I meant 4th and 5th lines, but I guess 5th line is just a bridge too.
Yes
I'll try it, thank you so much. |
This is Swift (or Objective-C) code, K/N has nothing to do with this line. |
Btw, is it short(or middle) term fix? Do you have a plan to handle it? Is it even possible to fix? |
We are improving support for analyzing production crashes currently, some of this work will be included into 1.3.60. |
Closing as duplicate of https://youtrack.jetbrains.com/issue/KT-29279 |
We have a trouble with stack trace on iOS side. As it mentioned here #2600 in release mode we cannot have a good stack trace for now, but we compiled KN lib in debug mode and stack trace is still wrong. We have an iOS project and a K/N project. When we got a crash it's logged to Crashlytics. Stack trace looks like:
KotlinNativeExample - iOS project
KNModule - K/N lib
The crash happened inside a testCrash() func by throw NotImplementedError()
The K/N project was compiled (in debug mode) by using https://github.com/AlecStrong/kotlin-native-cocoapods plugin. After compilation we have dSYM files. The first one for iOS project and the second one for the K/N lib. (dSyms also was generated by AlecStrong/kotlin-native-cocoapods plugin). Both dSym files was uploaded to Crashlytics but the stacktrace is still wrong. Is there any idea how to get a good stacktrace in Crashlytics? This is happening only with Crashlytics, If I got a crash in Xcode it has a good stack trace.
The text was updated successfully, but these errors were encountered: