Firebase-android-sdk: Improve native crashes stack traces with a stripped library

Created on 9 Jul 2020  路  5Comments  路  Source: firebase/firebase-android-sdk

What feature would you like to see?

When a native crash happens in a stripped library, the report is useless in Firebase compared to what we get in the Google Play Console.
I think it's possible to display more information, even without a properly symbolicated library, and that would allow us to deobfuscate stack traces manually.

I don't have the same crashes in both consoles but these screenshots should show what I mean.

In the Google Play console:

Screenshot 2020-07-09 at 15 29 58

In the Firebase console:

Screenshot 2020-07-09 at 15 29 45

crashlytics needs-triage feature request

Most helpful comment

Brought this back to the team for comment. This is a great idea and we're planning to look into it for the future, and we'll let you know here if there are any updates or changes to this.

All 5 comments

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

Thanks for pointing that out.
I'll leave this open as a feature request, although it does not really seem scoped strictly to the SDK.

Should I report this problem somewhere else?

I think this is the best place for it. Appreciate the feedback!

Brought this back to the team for comment. This is a great idea and we're planning to look into it for the future, and we'll let you know here if there are any updates or changes to this.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

gitton picture gitton  路  6Comments

CristianGM picture CristianGM  路  5Comments

bobsmits picture bobsmits  路  6Comments

jkasten2 picture jkasten2  路  4Comments

ANR
RodolfoGS picture RodolfoGS  路  4Comments