Deobfuscate crash and ANR stack traces

This page contains Help content for SDK providers using Google Play SDK Console.

If you're an app developer looking for Google Play Console Help content, use the search bar or return to the homepage.

You can upload deobfuscation files for each version of your SDK listed on the SDK versions page. Proguard (ReTrace) mapping files are used to deobfuscate Java stack frames, and native debug symbols are used to deobfuscate native stack frames inside crash and ANR reports. Once you’ve uploaded these files, all newly reported stack traces in the Crashes and ANRs section of SDK Console will be deobfuscated.

Upload a deobfuscation file for each SDK version

Upload a deobfuscation file for each version by following the steps below.

Step 1: Generate the deobfuscation file

Follow the guidelines under Step 1 in this Play Console Help article to generate the appropriate deobfuscation file. Note that these guidelines were written for app developers, and are largely identical to the steps SDK providers should take.

Step 2: Upload the deobfuscation file to SDK Console

Once the deobfuscation file is generated, upload it to SDK Console:

  1. Open SDK Console.
  2. Choose an SDK.
  3. Click the three dots symbol () next to the relevant SDK version.
  4. Select Upload ReTrace mapping file (.txt or .map) or Upload native debug symbols (.zip) and upload the corresponding deobfuscation file.
  5. Once the upload is finished, a paperclip icon will indicate that the deobfuscation file is attached to that version.

Important considerations

  • To help preserve user and app developer anonymity, crashes and ANRs are only reported when the number of times they occur exceeds a set threshold. Reports do not provide additional breakdowns of the crash or ANR data, such as sharing the names of impacted apps. In addition, for a given stack trace, reports only show stack frames and line numbers if there are enough occurrences of the same crash or ANR.
  • The stack trace will be included whenever your SDK was involved in a crash or ANR error, regardless of whether it was the actual cause of the crash or ANR. SDK Console does not currently apply any logic to determine if the crash or ANR was caused by your SDK, so it’s possible that many of the crashes or ANRs that you see are unrelated to your SDK.
  • SDK Console can identify SDKs only if the app shares its library dependencies, and the app isn’t obfuscated or provides the deobfuscation files in Play Console. As a result, the number of impacted apps and users shown for a given crash or ANR can be lower than the true value.

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Main menu
18079868180995349538
true
Search Help Center
true
true
true
true
true
92637
false
false