Add BugSnag to your Android apps to automatically detect unhandled exceptions
Find and fix exceptions impacting your users
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.
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.
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.
Tests aren't enough to keep your app crash-free. Device fragmentation and environment differences impact how your app runs.
Users who have negative experiences using your app can leave negative reviews. Avoid these by staying ahead of bugs and releasing quality code.
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.
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.
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.
Automatically captured reports give you the answers you need to pinpoint the source of crashes
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.
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.
Every exception is tagged with user details so you can correlate errors with customer support requests.
Exceptions on mobile require special context, like the screen open when a crash happened and out of memory errors.
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.
Resilient Android crash reporting that's used on some of the world's most popular apps including Airbnb, Pandora, and Square
With less than 800 methods, our Android SDK doesn't add any noticeable overhead to your app loads.
All BugSnag notifiers are open source so you can see the exception handling code and even make pull requests to suggest improvements.
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.
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.
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.
Stacey Snyder
Sr. Director of Engineering, Recurly
Software Engineer, Chime
Nahuel Barrios
Engineering Manager
Antonio Niñirola
Engineering Manager