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.

Specifying options

Most configuration options can be specified in two ways; By initialising Bugsnag and then calling the relevant set method


or by setting up a configuration object and passing it into Bugsnag init

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

Some of the options must be passed in using a configuration object because they affect the way that Bugsnag is initialized.

Build Variants

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
    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}"/>

Finally, initialize Bugsnag in your Application class.



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:



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:


Note: Bugsnag uses Semantic Versioning for app version sorting and filtering on the Bugsnag dashboard.


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, it is useful to set this to be your currently active Activity.

If you enable the GET_TASKS permission, then this is set automatically for you. If you would like to set the bugsnag context manually, you can call setContext:



Set the endpoint to which error reports are sent. By default, reports are sent to endpoint, but this option should be overridden if you are using Bugsnag On-premise, to point to your own Bugsnag endpoint:

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


Sets the ErrorReportApiClient implementation used to make network calls to the Error Reporting API. This may be useful if you have requirements such as certificate pinning and rotation, which are not supported by the default implementation.

Bugsnag.setErrorReportApiClient(new CertPinnedApiClient());

Implementations of ErrorReportApiClient must throw a BadResponseException if the response code is not 200, and a NetworkException if the request could not be completed. The request body must match the structure specified in the Error Reporting API documentation.

An example of a custom client which uses certificate pinning is provided below.

 * A custom API client which uses Square's OkHttp3 Library to pin certificates.
class CertPinnedApiClient implements ErrorReportApiClient {
    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 postReport(String urlString, Report report)
        throws NetworkException, BadResponseException {
        try {
            MediaType mediaType = MediaType.parse("application/json");
            Request request = new Request.Builder()
                .post(RequestBody.create(mediaType, getReportJson(report)))
            Response response = okHttpClient.newCall(request).execute();

            if (response.code() != 200) {
                throw new BadResponseException("", response.code());
        } catch (IOException e) {
            throw new NetworkException("Network Call failed", e);


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.

Bugsnag.setFilters(new String[]{"password", "credit_card_number"});

By default, filters is set to new String[] {"password"};


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

Bugsnag.setIgnoreClasses("", "com.example.Custom");


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");
Bugsnag.init(context, 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:

Bugsnag.setNotifyReleaseStages("production", "development", "testing");


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.

Bugsnag.setProjectPackages("", "");

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.


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.



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");


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);