Debug exceptions in your Kotlin applications to improve software quality for your users
Find and fix exceptions impacting your users
Setup is quick using our Android or Java SDK. Thanks to Kotlin being 100% interoperable, you can leverage our Android and Java libraries and immediately begin detecting bugs in your Kotlin application.
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.
See which crashes happen most and which affect the most users, so you can assess a crashes' impact and prioritize your work.
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.
Kotlin crash reports from Bugsnag include device manufacturer, model, and OS name and version to help you understand if crashes are widespread or isolated to a specific device.
Debugging and error handling is easier 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 errors
See the full de-obfuscated stacktrace for each exception, even full thread state information. If you're using ProGuard on Android, 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.
Check the health of your latest release, or find an error reported by a user using filters to find specific crashes.
Resilient Kotlin exception reporting that's used on some of the world's most popular apps
Weighing in at 73kb and less than 700 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 Bugsnag servers using 256-bit SSL. Users can also host Bugsnag on-premise.
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.
Billy Pham
Technical Program Manager
Software Engineer, Chime
Nahuel Barrios
Engineering Manager
Antonio Niñirola
Engineering Manager