Comprehensive Android crash reporting to quickly debug errors

Add Bugsnag to your Android apps to automatically detect unhandled exceptions

Effortless Android crash reporting

Find and fix exceptions impacting your users

Know when your app crashes

Automatically get alerts when your users see crashes. Bugsnag's Android plugin captures unhandled and handled exceptions in real-time. You'll know which crashes happen most and which affect the most users.

Support for Android Native Development Kit

Automatically capture crashes in apps written in native code languages with Bugsnag support for NDK. A quick install and you'll get info on both the C++ and Java environment, including de-obfuscated stacktraces.

Get alerted to errors affecting users

Bugsnag automatically captures errors and alerts you via email, Slack, PagerDuty, and more. You'll also see detailed error reports in your dashboard for faster debugging.

Integrate with your Laravel ecosystem

Bugsnag works well with your Laravel tooling — integrate with the application logger, or monitor your Lumen projects, too, with Bugsnag for Lumen.

Real-time alerts where you already work

Bugsnag automatically alerts you via Slack and PagerDuty when errors are detected. Select your alerting preferences to know when new errors, regressions, or spike in your error rate occur.

Proactively address software quality

Visibility into errors is only the first step. With two-way integrations and in-app workflow, you'll also make progress prioritizing bugs and moving them through your debugging process.

Monitor release health

Use the Releases dashboard to decide if a release is successful or needs to be rolled back. The crash rate indicator shows the percentage of sessions in a release that end in a crash, allowing you to compare release health and track improvements over time.

Investigate Android App Crashes

Tests aren't enough to keep your app crash-free. Device fragmentation and environment differences impact how your app runs.

Avoid one-star reviews

Users who have negative experiences using your app can leave negative reviews. Avoid these by staying ahead of bugs and releasing quality code.

See where your app is running

Crash reports include device manufacturer, model, and OS name and version to help you understand if crashes are widespread or isolated to a specific device.

Reproduce errors with environment data

Important diagnostic data is automatically collected on each error like the browser and version, OS, request, and React specific data. You can also send custom data if what we capture isn’t enough.

Automatically collected user activity

Efficiently reproduce errors with a timeline of user and system events leading up to each error, like clicks, console logs and errors, page load, and more.

See the state of the device

Debugging is more efficient when you know the state a device was in during a crash. Bugsnag reports details on memory, hardware features, other apps open, rooted, permissions, battery, and more.

Identify crashes from other sources

Bugsnag lets you know when severe crashes are caused by backend or API changes, and alerts you to spiking error rates. You can even snooze alerts until they reach a critical level.

User and environment data

Bugsnag automatically captures diagnostic data like request information, session data, and more. It also captures user information in order to correlate errors with customers.

Customize your error reports

Bugsnag automatically captures as much information as possible, but since all apps are unique, you can easily customize your reportand send the data you need to assess and reproduce every error.

In-depth Android Crash Reports

Automatically captured reports give you the answers you need to pinpoint the source of crashes

See the code that crashed

See the full de-obfuscated stacktrace for each exception, even full thread state information. If you're using ProGuard, our Gradle plugin uploads your mapping files for each build so you can see the line of code that crashed.

See breadcrumbs

Bugsnag automatically captures breadcrumbs, a timeline of navigation events and system broadcasts leading up to the crash being detected. Use them to easily reproduce crashes.

User information

Every exception is tagged with user details so you can correlate errors with customer support requests.

Mobile specific diagnostics

Exceptions on mobile require special context, like the screen open when a crash happened and out of memory errors.

Detect and Fix ANRs

Quickly get to the code responsible for Application Not Responding (ANR) errors with a full stack trace. ANRs are grouped by cause, making it easy to prioritize the errors that are happening the most and determine which ones to fix. Read our docs.

Correlate errors with users

Looking at error counts alone won't give you a full understanding of an error's severity. Correlate errors with users to see how widespread an error really is.

Decrease noisy errors

Cross-browser error grouping, domain whitelisting, discarding errors from legacy browsers, and stripped out browser extension errors help to decrease noisy React errors and keep you focused on the ones that matter. Learn more JS monitoring best practices.

Production ready Android crash reporting

Resilient Android crash reporting that's used on some of the world's most popular apps including Airbnb, Pandora, and Square

Lightweight library

With less than 800 methods, our Android SDK doesn't add any noticeable overhead to your app loads.

Open source

All Bugsnag notifiers are open source so you can see the exception handling code and even make pull requests to suggest improvements.

Enterprise level security

Send errors to our servers using 256-bit SSL, the same encryption used by the world’s leading enterprises. You can host Bugsnag on-premise for complete data control.

Breakup with Crashlytics

Frustrated with Crashlytics? Watch our video on why Andi and Ashly are breaking up. Breakups are usually tough, but see why this one isn’t for Andi.

If you’re increasingly frustrated with Crashlytics, watch our video on why Andi and Ashly are breaking up. Although breakups are usually tough, see why this one isn’t for Andi because among many disappointments, Ashly isn’t interested in speaking to Andi’s relatives in React Native.

If you’re increasingly frustrated with Crashlytics, watch our video on why Andi and Ashly are breaking up. Although breakups are usually tough, see why this one isn’t for Andi because among many disappointments, Ashly isn’t interested in meeting Andi’s Kotlin friends.

Start free with Bugsnag
Gold tiles decorative accent.

What customers are saying