You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think a crucial requirement here will be that we keep the released app supportable. Specifically the crash logs added to Github tickets, will become obfuscated and thus unreadable.
We need to retain the mapping files (from obfuscation back to code)
for all released builds (gplay, fdroid, huawei)
and for every released version
Somewhere accessible, also to the community, so they can help with triaging
And even if we retain the mapping files, it will still be a real pain to triage the Github log excerpts. Not only will you not see familiar bugs at a glance, but you also need to painstakingly retrieve the exact matching mapping file, and de-obfuscate it. This adds at least +5 minutes of work before you can even start the actual investigation.
Activity
PhilLab commentedon Sep 23, 2026
I think a crucial requirement here will be that we keep the released app supportable. Specifically the crash logs added to Github tickets, will become obfuscated and thus unreadable.
We need to retain the mapping files (from obfuscation back to code)
And even if we retain the mapping files, it will still be a real pain to triage the Github log excerpts. Not only will you not see familiar bugs at a glance, but you also need to painstakingly retrieve the exact matching mapping file, and de-obfuscate it. This adds at least +5 minutes of work before you can even start the actual investigation.
@alperozturk96 @tobiasKaminsky
feat(build): First step towards R8 minify - still crashing
feat(build): First step towards R8 minify - still crashing
feat(build): First step towards R8 minify - still crashing