Troubleshooting

If you need help solving issues with Sentry's Flutter SDK, you can read the edge cases documented here. If you need additional help, you can view our forums, and customers on a paid plan may also contact support.

Known Limitations

• Flutter split-debug-info and obfuscate flags aren't yet supported on iOS/macOS; they are supported only on Android. If this feature is enabled, Dart stack traces are not human readable, this is a tooling limitation, See: 43612 and 43274.
• If you enable the split-debug-info feature, you must upload the Debug Symbols manually.
• Also, Issue's titles might be obfuscated as we rely on the runtimeType, but they may not be human-readable, See: Obfuscate Caveat
• Layout related errors are only caught by FlutterError.onError in debug mode. In release mode, they are removed by the Flutter framework. See Flutter build modes.
• On Windows, you have to set the version and build number manually, see this issue on GitHub. To do so:
  • Use Dart defines to build the app: flutter build windows --dart-define=SENTRY_RELEASE=my_app@1.0.0+1
  • Or, set the release on SentryOptions options.release = 'my_app@1.0.0+1' during SDK initialization.

Building Specific ABI on Android

The Sentry Flutter SDK includes the Sentry Android SDK, which bundles multiple native libraries for multiple ABIs. Building a Flutter app for a specific ABI using the --target-platform argument, for example an ARM 32bit apk, looks like this, which should also include the --split-per-abi flag:

flutter build apk --target-platform=android-arm --split-per-abi

Native Symbolication on Android

The configuration for symbolication of Native events (C/C++) is documented in our Android Native Development Kit content. If you are having issues with symbolication in Flutter, check that your configuration is correct, as discussed in our Flutter content that covers Uploading for Android NDK