Configuration options

The Bugsnag client object has several properties which can be set to customize the content of error reports and how the reports are sent.

Most configuration options should be specified by creating a Configuration object and passing it into Bugsnag.init:

Configuration config = new Configuration("your-api-key-here");
Bugsnag.init(this, config);

alternatively, you can initialize Bugsnag then call the relevant set method:


Please note that if you initialize using Bugsnag.init(this, config) it is not necessary to set an API key in your manifest.

To set different configuration values based on build variants or product flavors, see Customizing by build setting.


By default we will automatically add breadcrumbs for common application events such as activity lifecycle events and system intents. To disable this behavior, set this property to false:

Configuration config = new Configuration("your-api-key-here");
Bugsnag.init(this, config);


Add a callback to be executed code before every notification to Bugsnag.

You can use this to add or modify information attached to an error before it is sent to your dashboard. You can also return false from any callback to halt execution.

Bugsnag.beforeNotify(new BeforeNotify() {
    public boolean run(Error error) {
        return true;

See the customizing error reports reference for more information.


By default, Bugsnag reports unhandled exceptions in your application automatically. To disable this behavior, call disableExceptionHandler:



Resumes a session which has previously been stopped, or starts a new session if none exists. If a session has already been resumed or started and has not been stopped, calling this method will have no effect. You should disable automatic session tracking via setAutoCaptureSessions if you call this method.

It’s important to note that sessions are stored in memory for the lifetime of the application process and are not persisted on disk. Therefore calling this method on app startup would start a new session, rather than continuing any previous session.

You should call this at the appropriate time in your application when you wish to resume a previously started session. Any subsequent errors which occur in your application will be reported to Bugsnag and will count towards your application’s stability score.


Also see startSession and stopSession.


Sets the time in milliseconds at which an ANR is detected by Bugsnag. By default, Bugsnag will record an ANR whenever the main thread has been blocked for 5000 milliseconds or longer.

If you wish to disable ANR detection completely, you should set the setDetectAnrs property to false.

Configuration config = new Configuration("your-api-key-here");
Bugsnag.init(this, config);

Attempting to set this property to any value below 1000ms will result in the anrThresholdMs being set as 1000ms.


We’ll automatically pull your app version from the versionName field in your AndroidManifest.xml file. If you’d like to override this you can call setAppVersion:

Configuration config = new Configuration("your-api-key-here");
Bugsnag.init(this, config);


By default, Bugsnag will automatically capture and report session information from your application.

If the notify endpoint is changed and the sessions endpoint is not, this option will be set to false and session tracking will be disabled.

To disable automatic session capturing:

Configuration config = new Configuration("your-api-key-here");
Bugsnag.init(this, config);

If you want control over what is deemed a session, you can switch off automatic session tracking with the setAutoCaptureSessions option, and manage the session lifecycle using startSession(), stopSession() and resumeSession().


Bugsnag uses the concept of “contexts” to help display and group your errors. Contexts represent what was happening in your application at the time an error occurs. In an android app the “context” is automatically set as the foreground Activity.

If you would like to set this value manually, you can call setContext:


If your bugsnag-android version is older than 4.3.2, it is necessary to add the GET_TASKS permission to your manifest to enable automatic context tracking.


Sets the Delivery implementation used to make network calls to the Bugsnag Error Reporting and Sessions API.

This may be useful if you have requirements such as certificate pinning and rotation, which are not supported by the default implementation.

Configuration config = new Configuration("your-api-key-here");
config.setDelivery(new CertPinnedDelivery());
Bugsnag.init(this, config);

To provide custom delivery functionality, create a class which implements the Delivery interface. Please note that request bodies must match the structure specified in the Error Reporting and Sessions API documentation.

If delivery fails but you wish to retry the request at a later date, then throw a DeliveryFailureException. The notifier will catch this exception, automatically cache the payload and trigger delivery later on.

For example, if the device has no network connectivity, it may make sense to store the report and send it later:

if (!hasNetworkConnection) {
    throw new DeliveryFailureException("No network connection - try again later!");

Custom Delivery Example

A full example of a custom Delivery which uses certificate pinning is provided below.

 * A custom API client which uses Square's OkHttp3 Library to pin certificates.
class CertPinnedApiClient implements Delivery {

    OkHttpClient okHttpClient;

    // The public key hash(es) for your cert
    // can be found by following OkHttp3 instructions:
    CertPinnedApiClient() {

        CertificatePinner certificatePinner = new CertificatePinner.Builder()
            .add("", hash1) // expires in 2019
            .add("", hash2) // expires in 2020

        okHttpClient = new OkHttpClient.Builder()

    String getReportJson(Report report) {
        try {
            ByteArrayOutputStream baos = new ByteArrayOutputStream();
            JsonStream jsonStream = new JsonStream(new PrintWriter(baos));
            return baos.toString("UTF-8");
        } catch (IOException e) {
            throw new RuntimeException("Failed to generate request", e);

    public void deliver(Report report, Configuration config) throws DeliveryFailureException {
        try {
            MediaType mediaType = MediaType.parse("application/json");
            Request request = new Request.Builder()
                .post(RequestBody.create(mediaType, getReportJson(report)))
            Response response = okHttpClient.newCall(request).execute();
        } catch (IOException e) {
            throw new DeliveryFailureException("No network connection", e);

    public void deliver(SessionTrackingPayload payload,
                        Configuration config) throws DeliveryFailureException {
        // implement as per Error Report, but use config.getSessionEndpoint() and config.getSessionApiHeaders()


Sets whether ANRs should be reported to Bugsnag. By default, Bugsnag will record an ANR whenever the main thread has been blocked for 5000 milliseconds or longer, when no debugger is attached to the app.

If you wish to disable ANR detection, you should set this property to false; if you wish to configure the time threshold required to capture an ANR, you should use the setAnrThresholdMs property.

Configuration config = new Configuration("your-api-key-here");
Bugsnag.init(this, config);


By default we will send error reports to and sessions to

If you are using Bugsnag On-premise you’ll need to set these to your Event Server and Session Server endpoints. If the notify endpoint is set but the sessions endpoint is not, session tracking will be disabled automatically to avoid leaking session information outside of your server configuration, and a warning will be logged.

To set the endpoints:

Configuration config = new Configuration("your-api-key-here");
config.setEndpoints("", "");
Bugsnag.init(this, config);


Sets which values should be removed from any MetaData objects before sending them to Bugsnag. Use this if you want to ensure you don’t send sensitive data such as passwords, and credit card numbers to our servers. Any keys which contain these strings will be filtered.

Configuration config = new Configuration("your-api-key-here");
config.setFilters(new String[]{"password", "credit_card_number"});
Bugsnag.init(this, config);


Sets for which exception classes we should not send exceptions to Bugsnag.

Configuration config = new Configuration("your-api-key-here");
config.setIgnoreClasses("", "com.example.Custom");
Bugsnag.init(this, config);


Sets the threshold in milliseconds for an uncaught error to be considered as a crash on launch. If a crash is detected on launch, Bugsnag will attempt to send the report synchronously. By default, this value is set at 5,000ms. Setting the value to 0 will disable this behaviour.

Configuration config = new Configuration("your-api-key-here");
Bugsnag.init(this, config);


Sets the maximum number of breadcrumbs which will be stored. Once the threshold is reached, the oldest breadcrumbs will be deleted.

Configuration config = new Configuration("your-api-key-here");
Bugsnag.init(this, config);


Add information to attach to every report. To attach information dynamically at the time of capture, use beforeNotify.

Configuration config = new Configuration("your-api-key-here");
config.getMetaData().addToTab("account", "name", "Acme Co.");
Bugsnag.init(this, config);


By default, Bugsnag will be notified of exceptions that happen in any releaseStage. If you would like to change which release stages notify Bugsnag of exceptions you can call setNotifyReleaseStages:

Configuration config = new Configuration("your-api-key-here");
config.setNotifyReleaseStages("production", "development", "testing");
Bugsnag.init(this, config);


Set whether or not Bugsnag should persist user information between application sessions. If set then any user information set will be re-used until Bugsnag.clearUser() is called.

Configuration config = new Configuration("your-api-key-here");
Bugsnag.init(this, config);


Sets which package names Bugsnag should consider as a part of the running application. We mark stacktrace lines as in-project if they originate from any of these packages.

Configuration config = new Configuration("your-api-key-here");
config.setProjectPackages("", "");
Bugsnag.init(this, config);

By default, projectPackages is set to be the package you called Bugsnag.init from.


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.

Configuration config = new Configuration("your-api-key-here");
Bugsnag.init(this, config);

If you are running a debug build, we’ll automatically set this to “development”, otherwise it is set to “production”.


Sets if we should collect and send thread state along with errors.

By default sendThreads is set to true.

Configuration config = new Configuration("your-api-key-here");
Bugsnag.init(this, config);


Bugsnag helps you understand how many of your users are affected by each error. In order to do this, we need to send along user information with every exception.

If you would like to enable this, set the user. You can set the user id, which is usually the unique id to represent that user across all your apps, the user’s email address and the user’s name:

Bugsnag.setUser("userId", "", "User Name");


Starts tracking a new session. You should disable automatic session tracking via setAutoCaptureSessions if you call this method.

You should call this at the appropriate time in your application when you wish to start a session. Any subsequent errors which occur in your application will be reported to Bugsnag and will count towards your application’s stability score. This will start a new session even if there is already an existing session; you should call resumeSession if you only want to start a session when one doesn’t already exist.


Also see resumeSession and stopSession.


Stops tracking a session. You should disable automatic session tracking via setAutoCaptureSessions if you call this method.

You should call this at the appropriate time in your application when you wish to stop a session. Any subsequent errors which occur in your application will still be reported to Bugsnag but will not count towards your application’s stability score. This can be advantageous if, for example, you do not wish the stability score to include crashes in a background service.


Also see resumeSession and startSession.

Customizing by build setting

Manifest placeholders

Bugsnag can be set up to use different configuration values for different build variants, by using the following manifest placeholders in your app’s build.gradle script.

android {
    defaultConfig {
        manifestPlaceholders = [
            // omit any of the following placeholders to use the default values
            bugsnagApiKey: "<api-key>",
            bugsnagBuildUUID: "<build-uuid>",
            bugsnagAppVersion: "1.0.0",
            bugsnagEndpoint: "",
            bugsnagReleaseStage: "<release-stage>",
            bugsnagSendThreads: true,
            bugsnagEnableExceptionHandler: true,
            bugsnagPersistUserBetweenSessions: false,
            bugsnagAutoCaptureSessions: true
    productFlavors {
        free {
            manifestPlaceholders = [
                // override defaultConfig values here

For all the values you wish to configure, provide a meta-data element at the bottom of your manifest file.

    <meta-data android:name="" android:value="${bugsnagApiKey}"/>
    <meta-data android:name="" android:value="${bugsnagBuildUUID}"/>
    <meta-data android:name="" android:value="${bugsnagAppVersion}"/>
    <meta-data android:name="" android:value="${bugsnagEndpoint}"/>
    <meta-data android:name="" android:value="${bugsnagReleaseStage}"/>
    <meta-data android:name="" android:value="${bugsnagSendThreads}"/>
    <meta-data android:name="" android:value="${bugsnagEnableExceptionHandler}"/>
    <meta-data android:name="" android:value="${bugsnagPersistUserBetweenSessions}"/>
    <meta-data android:name="" android:value="${bugsnagAutoCaptureSessions}"/>

Finally, initialize Bugsnag in your Application class.


Using Resource values

Gradle resource values allow you to share custom fields and values between build files and app code. For example, to set API key in your build configuration, set a resource value in your Gradle file:

def bugsnag_api_key = project.hasProperty("api-key")
 ?"api-key") : "your-api-key-here"

buildTypes {
    release {
        resValue("string", "bugsnag_api_key", "${bugsnag_api_key}")

To load the value automatically when Bugsnag initializes, set a placeholder in your AndroidManifest.xml for the value:

<application ...>
    <meta-data android:name=""

Properties can also be loaded at runtime if needed (though not required if placeholders are set in AndroidManifest.xml):

Configuration config = new Configuration(getString(R.string.bugsnag_api_key));
Bugsnag.init(this, config);