Crash Retrace

Tools · Crash Retrace

Release crashes show names like a.b.c(SourceFile:12). Drop the mapping.txt from the same build and paste the crash to see the real classes, methods and line numbers. Nothing leaves your browser.

1 mapping.txt

Drop your mapping.txtFrom the same release build as the crash · big files are fine · stays on your device

2 Crash stack trace

Where do I find mapping.txt?

After a release build it's in app/build/outputs/mapping/release/mapping.txt. It changes with every build, so keep a copy for each version you ship.
Lost it? Google Play keeps the one you uploaded: Play Console → your app → App bundle explorer → pick the version → Downloads → ReTrace mapping file.
Crashlytics deobfuscates for you if the Crashlytics Gradle plugin uploads the mapping file. Use this tool for crashes from Play Console, testers and logcat.
Flutter: this tool reads Java and Kotlin frames. Dart code built with --obfuscate needs flutter symbolize with your --split-debug-info files.