ProGuard Mappings

If you use a tool to minify and optimize your application you will need to upload a mapping file to see full debugging information in error reports including the original class and method names. Mapping files generated by ProGuard, DexGuard and R8 are supported.

Use the POST /proguard endpoint to upload the generated mapping.txt file in your builds.

cURL example

ProGuard settings

As the line numbers of crashes are used to help with error grouping, you’ll need to explicitly tell ProGuard to not strip this information by adding the following rule to your ProGuard configuration:

If you are using proguard-android-optimize.txt settings then the stack traces will be converted to a human-readable format, but the original file names might not be available (class name will be used instead of file name in this case).

If the stacktraces provided do not contain a valid file then the unqualified class name will be used in place of the file name.

Symbolication guide

See our symbolication guide for a higher-level overview of integrating uploads into your build systems to see full stacktraces for all your releases.