Debug Symbols

Debug symbols help provide you with readable stack traces, which Sentry displays on the Issue Details page, to help you triage an issue. We offer a range of methods to provide Sentry with debug symbols.

With default settings, complete stack traces are available in your Java/Kotlin error, out of the box, unless you use enableProguardInReleaseBuilds. In this case, you need to upload the ProGuard/R8 mapping files generated by the Android Gradle Plugin, so Sentry can show you proper stack traces.

Upload the Android ProGuard/R8 mapping files and native symbols by the recommended method of using our Gradle integration.

Errors raised from the native layer in Android apps require certain debug information files to be uploaded. For example, DWARF debug files need to be uploaded for an Android app with NDK support.

To upload native symbols for React Native Android builds, use the Sentry Gradle Plugin's uploadNativeSymbols option.

To upload native iOS debug symbols, set up a Run Script build phase for uploading debug symbols to Sentry with the Sentry CLI. You can find documentation for this on the Manual Configuration page.

Upload the Android ProGuard/R8 mapping files and native symbols manually by using sentry-cli upload-proguard and debug-files.

To enable Source Context use the includeSourceContext Sentry Gradle Plugin option.

To enable Source Context set up a Run Script build phase for uploading debug symbols to Sentry and set SENTRY_INCLUDE_NATIVE_SOURCES=true before the build.

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").