Efficiently investigate and fix every Application Not Responding (ANR) error in your Android applications with enhanced stack traces for ANRs when the root cause is native or NDK code. The new NDK stack frames along with the existing JVM stack traces will provide complete visibility into the part of the code that was running when an ANR occurred.
To get started, upgrade to the latest version of our Android notifier.
Our Laravel, Syfony, and PHP notifiers now detect and report out of memory errors (OOMs). To get started, upgrade to the latest version and see the docs for any additional configuration.
We’ve improved how JavaScript errors are grouped for React Native projects to minimize duplicate errors being reported upon code modifications and to provide complete visibility into the impact of all errors over time.
New error groupings will no longer be created due to the line numbers changing because the improved grouping algorithm is based on the section of code an error is originating from rather than the line number, which can change when code is modified.
To upgrade, go to Project Settings > Default grouping.
Sometimes teams work in multiple issue tracker projects, such as a different one for each team responsible for a segment of the application’s codebase. Now, you can drive code ownership by automatically creating and linking issues to your team’s issue tracker project for errors occurring in your team’s codebase.
Linked issues can also be clearly seen in the Error Inbox and 2-way sync between Bugsnag and your issue tracker helps streamline debugging.
Contact us to gain access to this feature or see our docs for more details.
Existing snooze options allow errors to be snoozed until an event or time threshold is reached. Now, you can also snooze an error until it impacts additional users, so you are only alerted of it again when it becomes more important to fix. Customize the number of additional users impacted or select from some pre-set thresholds.
See the new options in the snooze menu.
Head to the Breadcrumbs tab of an event to see the new search and filtering capabilities. Select the type of breadcrumb or search from keywords to quickly find the specific breadcrumb you need to investigate the event.
Set up the new integration and configure notifications to drive real-time decisions about error prioritization and resolution in your Microsoft Teams channels. Streamline error triaging by changing the status of an error in Bugsnag to fixed, snooze, or ignore directly from within Microsoft Teams.
If you’re using the unofficial integration, migrate to this one to take advantage of notification filtering and streamlined triaging. Get started by reading our docs.
We’ve improved how errors are grouped for Ruby, PHP, Python, and Node.js projects to minimize duplicate errors being reported upon code modifications and to provide complete visibility into the impact of all errors over time.
New error groupings will no longer be created due to the line numbers changing because the improved grouping algorithm is based on the section of code an error is originating from rather than the line number, which can change when code is modified.
To upgrade, go to Project Settings > Default grouping.
Upgrade to our new tool for uploading source maps so you can unminify JavaScript stack traces reliably and with ease.
The @bugsnag/source-maps tool is a replacement for bugsnag-sourcemaps and can be used to upload source maps during your build process for React Native, browser JavaScript, and Node.js apps. Learn more in our docs.
You can now clearly see in the Error Inbox which application type, whether Android or iOS, was impacted by each error occurring in multi-platform projects, including React Native and Unity. Segmenting by this field can provide additional context to streamline error prioritization and debugging.
