Parent: #1182
Problem
Each minified Android build produces a build-specific mapping.txt needed to retrace obfuscated Java and Kotlin stack traces. The local output is overwritten by later builds, so it must be retained with the exact release artifacts it belongs to.
Google Play receives the mapping from an AAB automatically. A separate archived copy is still needed for internal APKs, GitHub releases, exported logs, and manual retracing outside Play Console.
Scope
- Collect
app/build/outputs/mapping/<release-variant>/mapping.txt from each stable and internal release workflow run.
- Give it a build-numbered name so it can be matched unambiguously to the APK/AAB and
native-debug-symbols archive.
- Include it in the corresponding CI release artifact and checksum manifest.
- Attach the stable mapping file to the GitHub release alongside the APK and native debug symbols.
- Update the release documentation with its location and its use with R8 Retrace.
No automated repository test is required for this build-configuration change. A manual retracing smoke check may be performed while implementing it.
Parent: #1182
Problem
Each minified Android build produces a build-specific
mapping.txtneeded to retrace obfuscated Java and Kotlin stack traces. The local output is overwritten by later builds, so it must be retained with the exact release artifacts it belongs to.Google Play receives the mapping from an AAB automatically. A separate archived copy is still needed for internal APKs, GitHub releases, exported logs, and manual retracing outside Play Console.
Scope
app/build/outputs/mapping/<release-variant>/mapping.txtfrom each stable and internal release workflow run.native-debug-symbolsarchive.No automated repository test is required for this build-configuration change. A manual retracing smoke check may be performed while implementing it.