ProGuard - decoding obfuscated stack traces


If you develop and publish mobile apps you will most likely see some crash reports with some kind of stack trace attached. If you used ProGuard to obfuscate the code it may be difficult to read such error message / stack trace.
Luckily for us it can be easily decoded using the same tool.

Following command does the trick: [-verbose] mapping.txt <stacktrace_file>

Retrace tool is available in your proguard/bin path which usually is <sdk_root>/tools/proguard/bin directory

Important thing is to use the same mapping.txt file that has been used to obfuscate the code (this can be find in you <app_project_root>\proguard )