Android NDK integration

Add Bugsnag to your Android NDK projects to automatically capture and report crashes in released applications.

New to Bugsnag? Create an account now.


Using Android Studio or Gradle

Add bugsnag-android-ndk to the dependencies section of your Module Gradle Settings, usually found at <project_dir>/app/build.gradle:

compile 'com.bugsnag:bugsnag-android-ndk:1.+'

Don’t forget to run Sync Project with Gradle Files after updating this file.

Using Maven

Add bugsnag-android-ndk as a dependencies in your pom.xml:


Manual AAR installation

Download the Android NDK latest release and the dependent release of bugsnag-android and place them in your app’s libs folder. Then add flatDirs as a repository and the archives to your module-level gradle settings:

repositories {
    flatDir {
        dirs 'libs'
dependencies {
    compile(name:'bugsnag-android-ndk', ext:'aar')
    compile(name:'bugsnag-android', ext:'aar')

Basic configuration

Set your API key

Configure your integration API key in the <application> tag of your App Manifest file.

<application ...>
    <meta-data android:name="" android:value="your-api-key-here "/>

You can find your integration API key immediately after creating a new project from your Bugsnag dashboard, or later on your project’s settings page.

Initialize the Bugsnag client

Import the Bugsnag package in your Application subclass:


In your application’s onCreate function, initialize Bugsnag:


Further configuration

If you’d like to configure Bugsnag further, check out the configuration options reference.

Showing full stacktraces

Configuring ProGuard

If you are using ProGuard to shrink your app, this will cause method and class names to become obfuscated, which makes debugging harder, and causes error grouping problems for Bugsnag.

In order to replace the obfuscated data with a human-readable stack trace, Bugsnag can use a mapping file, check out our Android mapping guide for more details.

Showing native stacktraces

A native stacktrace consists of a list of addresses and numeric offsets. In order to replace the addresses with files and method names, Bugsnag uses a shared object mapping file.

If you’re using Android Studio and/or Gradle to build your Android projects, the best way to send your shared object mapping files to Bugsnag is to use the Bugsnag Android Gradle plugin. See the NDK symbol upload API guide for more information.

Using the Native API

By default Bugsnag will collect and report information if your application crashes. If you would like to use the native API to send other information to Bugsnag from you C or C++ code, add Bugsnag as a dependency of your CMake target. The shared object files and headers are included in the release archive.

add_library(lib_bugsnag SHARED IMPORTED)
set(BUGSNAG_DIR ${CMAKE_SOURCE_DIR}/build/intermediates/exploded-aar/com.bugsnag/bugsnag-android-ndk/${BUGSNAG_VERSION})
set_target_properties(lib_bugsnag PROPERTIES
target_include_directories(your-native-lib PRIVATE ${BUGSNAG_DIR}/assets/include)
target_link_libraries(your-native-lib lib_bugsnag) # Insert your target name

Then you can set JNI environment which Bugsnag will use when sending error reports.

#include <bugsnag.h>

// ...

Alternately, you can use the _env variants of the native API.

Reporting unhandled exceptions

After completing installation and basic configuration, unhandled exceptions will be automatically reported to your Bugsnag dashboard.

Reporting handled errors

If you would like to send handled exceptions to Bugsnag, you can pass any Throwable object to the Bugsnag.notify method:

try {
    // Some potentially crashy code
} catch (Throwable exception) {

It can often be helpful to adjust the severity or attach custom diagnostics to handled exceptions. For more information, see reporting handled errors.

Alternately, from C or C++, you can invoke bugsnag_notify with a title, description and severity:

bugsnag_notify("Invalidation Error", "No name specified", BSG_SEVERITY_WARN);

Sending diagnostic data

Automatically captured diagnostics

Bugsnag will automatically capture and attach the following diagnostic data to every exception report:

  • A full stacktrace
  • Application information (package name, app name, version)
  • Device information (manufacturer, brand, model, total memory)
  • Screen information (density, dpi, resolution, orientation)
  • System information (android version, locale, rooted state)

Attaching custom diagnostics

It can often be helpful to attach application-specific diagnostic data to exception reports. This can be accomplished by setting a callback which will be invoked before any reports are sent to Bugsnag:

Bugsnag.beforeNotify(new BeforeNotify() {
    public boolean run(Error error) {
        // Attach customer information to every error report
        error.addToTab("account", "name", "Acme Co.");
        error.addToTab("account", "paying_customer", true);

        return true;

For more information, see customizing error reports.

Identifying users

In order to correlate errors with customer reports, or to see a list of users who experienced each error, it is helpful to capture and display user information.

This can be accomplished by calling setUser:

Bugsnag.setUser("123456", "", "James Smith");

Or bugsnag_set_user from C or C++:

bugsnag_set_user("123456", "", "James Smith");

For more information, see configuration options.

Disabling error reporting

If you wish to disable error reporting, you can return false within Bugsnag.beforeNotify. This would allow for users to opt out of sending error reports, for example:

Bugsnag.beforeNotify(new BeforeNotify() {
    public boolean run(Error error) {
        return false; // no error report will be sent

Logging breadcrumbs

In order to understand what happened in your application before each crash, it can be helpful to leave short log statements that we call breadcrumbs. The last several breadcrumbs are attached to a crash to help diagnose what events lead to the error.

Automatically captured breadcrumbs

By default, Bugsnag captures common events including:

  • Activity Lifecycle callbacks
  • Network connectivity changes
  • Bluetooth connectivity changes
  • Battery state changes
  • Device rotation
  • Media Scanner events
  • Telephony events
  • Other device metrics and more

Attaching custom breadcrumbs

Leaving breadcrumbs can be accomplished by calling leaveBreadcrumb:

Bugsnag.leaveBreadcrumb("App loaded");
Bugsnag.leaveBreadcrumb("User clicked a button");

Additional data can be attached to breadcrumbs by using the longer form of leaveBreadcrumb:

Map<String, String> metadata = new HashMap<>();
metadata.put("from", "moka");
metadata.put("to", "french press");
Bugsnag.leaveBreadcrumb("Preference updated", BreadcrumbType.STATE, metadata);

From C or C++, leave breadcrumbs using bugsnag_leave_breadcrumb, including a message and the type:

bugsnag_leave_breadcrumb("App loaded", BSG_CRUMB_STATE);

When logging breadcrumbs, we’ll keep track of the timestamp, and show both the message and timestamp on your dashboard. Individual breadcrumb size is limited to 4kb after serialization. Any larger breadcrumbs will be dropped from the payload while logging a warning.

Next steps

  • View bugsnag-android-ndk, the library powering Bugsnag for Android NDK, on GitHub
  • Get support for your questions and feature requests