title: Debugging Obfuscated Stack Traces pulled from Android Developer Console Error Reports
body: <p>I've had an app on Google Play for a little while now which hasn't historically been obfuscated.  From time to time there will be an error on the user's device and I will get a report through the Android Developer Console Application Error Reports, which lets me see a stack trace of the crash which I can use to fix the bug.  I've just released a new version of my app which is obfuscated for the first time (ProGuard), and am curious whether I can use the ProGuard <code>retrace</code> tool to de-obfuscate the Stack Traces reported through the Android Developer Console specifically.</p>
  
  <p>I have read the <em>Decoding Obfuscated Stack Traces</em> section <a href="http://developer.android.com/tools/help/proguard.html" rel="nofollow">here</a>, but I'm still not certain what the format is of the stack trace file (or standard input) that the <code>retrace</code> command accepts and whether this is the same format errors are reported in by the Android Developer Console Error Reports.  I've kept the all important <code>mapping.txt</code> file.  Basically all I want to know is, when the first new error stack trace rolls into the Android Developer Console, is it going to be presented in a format that I can run the <code>retrace</code> tool on, or, do I need to be collecting stack traces in some other specific format using some other tool if I want a hope of reconstructing the stack trace using <code>retrace</code>?</p>