Debug symbols provide information that 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 Dart error, out of the box, unless you use
obfuscate. In those cases, you need to upload the debug information files generated by the
flutter build, so Sentry can show you proper stack traces.
For Flutter Desktop (Windows/macOS/Linux)
obfuscate flags are not supported yet. See this issue.
Errors raised from the native layer in Flutter apps require certain debug information files to be uploaded. For example, an Android app can use
proguard for minification and obfuscation. And when using NDK, dwarf debug files need to be uploaded. Flutter Web requires sourcemaps and iOS apps also require dwarf debug information files.
Try out the Beta version of the Sentry Dart Plugin, which uploads debug symbols automatically for you, or follow the manual steps below.
Sentry requires a dSYM upload to symbolicate your crash logs. The symbolication process unscrambles Apple’s crash logs to reveal the function, file names, and line numbers of the crash. Learn how to upload the dSYM files.
If you are using
sentry_flutter version earlier than 5.1, native symbolication on Android requires a specific configuration. For good symbolication, set
android:extractNativeLibs="true" in your
AndroidManifest.xml file or
android.bundle.enableUncompressedNativeLibs=false for Android App Bundle in your
Sentry's Flutter SDK doesn't currently support the
uploadNativeSymbols flag from the Sentry Gradle Plugin.
You can also use our CLI to upload source maps for Flutter Web.