Some Android Crash Report Stack details are still obfuscated even after uploading mapping file

Hi pajus83,

Our apologies, this is being caused by a bug in our Proguard retracing tool. We'll look at getting this fixed up for you.

-Jason Fauchelle

Hi paju83,

We have resolved the bug preventing your stacktraces from being retraced. You can reprocess your existing crash reports to see the result, and any new crash reports that you send in will be retraced correctly as long as the matching mapping file is present.

Please let us know if you have any questions.

-Jason Fauchelle

Hi,

Sorry to hear you're experiencing this issue again. First, please double check that the correct mapping file is uploaded. On an exception report that you're seeing obfuscated results, check what version number of the application is mentioned in the exception report. Then, navigate to the "ProGuard Mapping Center" which can be found in the left-hand side bar after clicking Application settings. If the application version is not listed, then that will be the problem, as that's how we are selecting which mapping file to use. Even if the version number is there, it's possible to upload the wrong mapping file against it. If you know you have the correct mapping file on hand, you could delete the mapping file for the problematic version and re-upload it. If you take any of these actions, you can then click the "Reprocess crash report" button when viewing the obfuscated exception reports.

If the problem persists, please use the "Contact Raygun" option at the bottom of the left hand side bar to send us a link to an exception you're seeing with obfuscated results - if you don't mind us taking a look to investigate this deeper.

-Jason Fauchelle

Hi Pavle,

Good to hear stack traces are being processed correctly. We don't do any processing to the message currently. I've added this to the backlog as something to look into.

-Jason Fauchelle