EdwardvanRaak
commented
4 years ago Oh apperently there was already an issue for this (sort off)? #6773
I guess I'll just close this.
Closed EdwardvanRaak closed 4 years ago
EdwardvanRaak
commented
4 years ago Oh apperently there was already an issue for this (sort off)? #6773
I guess I'll just close this.
This might have to be moved to realm-core, but I was just wondering about this.
In the latest Android Developers blog there is a part about Symbolication for native crash reports.
Here is the direct quote:
Symbolication for native crash reports
When a crash or ANR occurs in native code, the system produces a stack trace, which is a snapshot of the sequence of nested functions called in your program up to the moment it crashed. These snapshots can help you to identify and fix any problems in the source, but they must first be symbolicated to translate the machine addresses back into human-readable function names.
If your app or game is developed using native code, like C++, you can now upload debug symbols files to the Play Console for each version of your app. The Play Console uses these debug symbols files to symbolicate your app's stack traces, making it easier to analyze crashes and ANRs. To include debug symbols in your app bundle, add the following line to your project’s build.gradle file:
android.buildTypes.release.ndk.debugSymbolLevel = 'SYMBOL_TABLE'As far as I'm aware you guys have the ability to unroll native stack traces but it would be great if we can easily do this as well.
So my question: will you provide symbol files for us to upload to the playstore? Or is that impossible due to software licencing or some other limitations? And if not, are there any future plans to make debugging native crashes easier to debug/recover from?
Oh and I might have missed a guide somewhere on how to unroll native crashes ourselves. My question is specifically about doing it through the play console.