BugSnag automatically captures a variety of data to help you debug your errors. You may wish to avoid capturing some types of data, particularly if there are privacy implications for your users.
The following data is collected and added to the metadata field of an BugsnagEvent. This data can be removed by clearing the following keys from metadata:
| Section | Key | Description |
|---|---|---|
flutter |
buildID |
The Build ID of the app |
flutter |
errorContext |
A description of where the error was caught (from FlutterErrorDetails.context |
flutter |
errorLibrary |
The name of the library that caught the error message (from FlutterErrorDetails.library) |
flutter |
errorInformation |
Information recorded to provide help with debugging (from FlutterErrorDetails.informationCollector) |
flutter |
defaultRouteName |
The route the native application requested when launching the Flutter app (from PlatformDispatcher.defaultRouteName) |
flutter |
initialLifecycleState |
The lifecycle state of your Flutter app directly after its initialization (from PlatformDispatcher.initialLifecycleState) |
flutter |
lifecycleState |
Description of the app lifecycle state when the error was reported (from SchedulerBinding.lifecycleState) |
The following information is automatically captured by BugSnag when running a Flutter app on Android.
To prevent collection, use event callbacks and session callbacks to redact or remove the data as required.
The following information is automatically captured by BugSnag when running a Flutter app on iOS.
To prevent collection, use event callbacks and session callbacks to redact or remove the data as required.
Breadcrumbs are automatically recorded for common actions and can be helpful to reproduce errors.
See the Android and iOS guides for details of the events being recorded. Breadcrumbs are collected and can be disabled by its type using the Enabled Breadcrumb Types configuration option.