Configuration
User-specified configuration storage object, contains information specified at the client level, api-key and endpoint configuration.
Functions
Link copied to clipboard
Add a single feature flag with no variant.
Add a single feature flag with an optional variant.
Link copied to clipboard
Add a collection of feature flags.
Link copied to clipboard
Adds a map of multiple metadata key-value pairs to the specified section.
Adds the specified key and value in the specified section.
Link copied to clipboard
Add an "on breadcrumb" callback, to execute code before every breadcrumb captured by Bugsnag.
Link copied to clipboard
Add a "on error" callback, to execute code at the point where an error report is captured in Bugsnag.
Link copied to clipboard
Add a callback which will be invoked prior to an event being delivered to Bugsnag.
Link copied to clipboard
Add an "on session" callback, to execute code before every session captured by Bugsnag.
Link copied to clipboard
Remove a single feature flag regardless of its current status.
Link copied to clipboard
Clear all of the feature flags.
Link copied to clipboard
Removes all the data from the specified section.
Removes data with the specified key from the specified section.
Link copied to clipboard
If your app's codebase contains different entry-points/processes, but reports to a single Bugsnag project, you might want to add information denoting the type of process the error came from.
Link copied to clipboard
Set the application version sent to Bugsnag.
Link copied to clipboard
If you want to disable automatic detection of all errors, you can set this property to false.
Link copied to clipboard
Sets whether or not Bugsnag should automatically capture and report User sessions whenever the app enters the foreground.
Link copied to clipboard
Bugsnag uses the concept of "contexts" to help display and group your errors.
Link copied to clipboard
The Delivery implementation used to make network calls to the Bugsnag Error Reporting and Sessions API.
Link copied to clipboard
Allows you to specify the fully-qualified name of error classes that will be discarded before being sent to Bugsnag if they are detected.
Link copied to clipboard
By default we will automatically add breadcrumbs for common application events such as activity lifecycle events and system intents.
Link copied to clipboard
Bugsnag will automatically detect different types of error in your application.
Link copied to clipboard
By default, Bugsnag will be notified of events that happen in any releaseStage.
Link copied to clipboard
Set the endpoints to send data to.
Link copied to clipboard
Set whether or not Bugsnag should generate an anonymous ID and persist it in local storage If disabled, any device ID that has been persisted will not be retrieved, and no new device ID will be generated or stored
Link copied to clipboard
Sets the threshold in milliseconds for an uncaught error to be considered as a crash on launch.
Link copied to clipboard
Sets the maximum number of breadcrumbs which will be stored.
Link copied to clipboard
Sets the maximum number of persisted events which will be stored.
Link copied to clipboard
Sets the maximum number of persisted sessions which will be stored.
Link copied to clipboard
Gets the maximum number of threads that will be reported with an event.
Link copied to clipboard
Gets the maximum string length in any metadata field.
Link copied to clipboard
Link copied to clipboard
Sets the directory where event and session JSON payloads should be persisted if a network request is not successful.
Link copied to clipboard
Set whether or not Bugsnag should persist user information between application sessions.
Link copied to clipboard
Sets which package names Bugsnag should consider as a part of the running application.
Link copied to clipboard
Sets which values should be removed from any Metadata objects before sending them to Bugsnag.
Link copied to clipboard
If you would like to distinguish between errors that happen in different stages of the application release process (development, production, etc) you can set the releaseStage that is reported to Bugsnag.
Link copied to clipboard
Sets whether or not Bugsnag should send crashes synchronously that occurred during the application's launch period.
Link copied to clipboard
Controls whether we should capture and serialize the state of all threads at the time of an error.
Link copied to clipboard
Link copied to clipboard
Gets the maximum time for collecting threads and traces.
Link copied to clipboard
We'll automatically pull your versionCode from the versionCode field in your AndroidManifest.xml file.
Link copied to clipboard
Whether Bugsnag should try to send crashing errors prior to app termination.
Link copied to clipboard
Removes a previously added "on breadcrumb" callback
Link copied to clipboard
Removes a previously added "on error" callback
Link copied to clipboard
Remove a callback previously added with addOnSend
Link copied to clipboard
Removes a previously added "on session" callback
Link copied to clipboard
If your app's codebase contains different entry-points/processes, but reports to a single Bugsnag project, you might want to add information denoting the type of process the error came from.
Link copied to clipboard
Set the application version sent to Bugsnag.
Link copied to clipboard
Whether Bugsnag should try to send crashing errors prior to app termination.
Link copied to clipboard
If you want to disable automatic detection of all errors, you can set this property to false.
Link copied to clipboard
Sets whether or not Bugsnag should automatically capture and report User sessions whenever the app enters the foreground.
Link copied to clipboard
Bugsnag uses the concept of "contexts" to help display and group your errors.
Link copied to clipboard
The Delivery implementation used to make network calls to the Bugsnag Error Reporting and Sessions API.
Link copied to clipboard
Allows you to specify the fully-qualified name of error classes that will be discarded before being sent to Bugsnag if they are detected.
Link copied to clipboard
By default we will automatically add breadcrumbs for common application events such as activity lifecycle events and system intents.
Link copied to clipboard
Bugsnag will automatically detect different types of error in your application.
Link copied to clipboard
By default, Bugsnag will be notified of events that happen in any releaseStage.
Link copied to clipboard
Set the endpoints to send data to.
Link copied to clipboard
Set whether or not Bugsnag should generate an anonymous ID and persist it in local storage If disabled, any device ID that has been persisted will not be retrieved, and no new device ID will be generated or stored
Link copied to clipboard
Sets the threshold in milliseconds for an uncaught error to be considered as a crash on launch.
Link copied to clipboard
Sets the maximum number of breadcrumbs which will be stored.
Link copied to clipboard
Sets the maximum number of persisted events which will be stored.
Link copied to clipboard
Sets the maximum number of persisted sessions which will be stored.
Link copied to clipboard
Sets the maximum number of threads that will be reported with an event.
Link copied to clipboard
Sets the maximum string length in any metadata field.
Link copied to clipboard
Sets the directory where event and session JSON payloads should be persisted if a network request is not successful.
Link copied to clipboard
Set whether or not Bugsnag should persist user information between application sessions.
Link copied to clipboard
Sets which package names Bugsnag should consider as a part of the running application.
Link copied to clipboard
Sets which values should be removed from any Metadata objects before sending them to Bugsnag.
Link copied to clipboard
If you would like to distinguish between errors that happen in different stages of the application release process (development, production, etc) you can set the releaseStage that is reported to Bugsnag.
Link copied to clipboard
Sets whether or not Bugsnag should send crashes synchronously that occurred during the application's launch period.
Link copied to clipboard
Controls whether we should capture and serialize the state of all threads at the time of an error.
Link copied to clipboard
Set which telemetry will be sent to Bugsnag.
Link copied to clipboard
Sets the maximum time for collecting threads and traces.
Link copied to clipboard
We'll automatically pull your versionCode from the versionCode field in your AndroidManifest.xml file.