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.
This documentation is for version 5 of the BugSnag Unity notifier. We recommend upgrading to the latest release using our Upgrade guide. Documentation for the current release can be found here.
Information about Unity can be useful to identify if an error occurs in certain versions.
| Data | Default value | Preventing collection |
|---|---|---|
| Unity Version | The version of the Unity runtime used to play the content. | Modify Metadata in a callback |
| Platform | The application platform (iOS, Android, macOS) | Modify Metadata in a callback |
| OS Language | The operating system language (e.g. English) | Modify Metadata in a callback |
| Bundle Identifier | The application identifier at runtime. On Apple platforms this is the ‘bundleIdentifier’ saved in the info.plist file, on Android it’s the ‘package’ from the AndroidManifest.xml. | Modify Metadata in a callback |
| Version | The app version according to Unity | Modify Metadata in a callback |
| Company Name | The application company name | Modify Metadata in a callback |
| Product Name | The application product name | Modify Metadata in a callback |
Breadcrumbs are automatically recorded for common actions and can be helpful to reproduce errors.
| Data | Default value | Preventing collection |
|---|---|---|
| Scene Loaded | The scene/level name | Modify breadcrumbs in a callback |
The following information is automatically captured by BugSnag when running a Unity app on Android.
The following information is automatically captured by BugSnag when running a Unity app on iOS.
The following information is automatically captured by BugSnag when running a Unity app on macOS.