Can we use mapping after dex build to map the error ?

mlegy / red-screen-of-death

A simple screen that is shown when your app gets crashed instead of the normal crash dialog. It's very similar to the one in Flutter.

Apache License 2.0

176 stars 11 forks source link

Can we use mapping after dex build to map the error ? #8

Open thegarlynch opened 3 years ago

thegarlynch commented 3 years ago

Usually after minifyEnabled every code is shortened according to proguard rules. using the same mechanism of crashlytics. can we use it to map the error ? or is it making mapping dex become a bit useless after loading mapping file ?

mlegy commented 3 years ago

Thanks for taking the time to share your suggestion!

The library is not supposed to be enabled in release builds but only debug builds and usually in debug builds people don't enable proguard, so I don't think we need to do this.

Let me know what you think.

thegarlynch commented 3 years ago

I think since moshi or other library tends to have some miscofiguration at runtime after dex build. This could be useful, crashlytics or any similar app have built this already, albeit with upload dex mapping mechanism. Well, the best way is to just archive it with application together. (But off course, not for release mode). I would help however i can