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

[thegarlynch]

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]

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]

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