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.


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 Enterprise, to point to your own Bugsnag endpoint:

Configuration config = new Configuration("your-api-key-here");
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.

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


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


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