Upload your Android mapping files to Bugsnag.
If you are using ProGuard or DexGuard to shrink your app, this will cause method and class names to become obfuscated, which makes debugging harder as the original file names, line numbers, and method names are not available.
Bugsnag can use a mapping file to replace the obfuscated data with a human-readable stack trace. The Android Gradle plugin automatically uploads your mapping file for each release build.
For NDK applications, a shared object mapping file can be uploaded to display the original code locations.
Bugsnag’s Gradle plugin will automatically upload ProGuard mapping files and can upload NDK shared object files when you build your app. See our Gradle Plugin docs to get started.
In cases where you are not using Gradle, you’ll need to manually upload your mapping file to Bugsnag using our APIs.
For ProGuard mapping files see the Android Mapping Upload API reference for more details.
For NDK shared object files see the NDK Symbol Upload API reference for more details.
If you are using
proguard-android-optimize.txt settings then Bugsnag will convert the stack traces 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 stack traces provided to Bugsnag do not contain a valid file, then we will use the unqualified class name in place of the file name.