De-obfuscate stack traces!!?
Enabling Proguard for android In this article I had told How to obfuscate the code. If you don’t know How obfuscate the code, not the data be clear? Proguard is obfuscating the code.
A good engineer thinks in reverse and asks himself about the stylistic consequences of the components and systems he proposes. — — Helmut Jahn
When we obfuscate the code the class names and method names are converted into some random obfuscated names such as a,b,c, etc. The problem is encounter when some exception raised or the application is crashed How to decode that stack trace is the big question developer having.
Exception, errors, and Bugs are fact of developer's life. So many developers requested and asked me How to de-obfuscate the stack trace? I answered a couple of developers but any email you’ve written twice should be a blog post.
where there is a will there is a way.
Once proguard shrinks your code, reading obfuscated stack trace is difficult because filed, method, and class names are obfuscated. Fortunately to help developers Proguard provides you mapping file. Every time you run and obfuscate the code, proguard is generating a mapping.txt file.
ProGuard outputs the following files:
dump.txt:- Describes the internal structure of all the class files in the APK.
mapping.txt:- Provides a translation between the original and obfuscated class, method…
