Bugsnag updates www.bugsnag.com

Bugsnag automatically discards errors from Chrome browser extensions because they are not actionable for you to fix. Now, errors from Firefox extensions will also be automatically discarded. If you want visibility into errors from browser extensions, read our docs.

We’ve updated our data access API to provide stability information, so you may extract this information from Bugsnag to include in your other dashboards.

Data now available includes the application’s overall daily user and session stability scores as well as user and session stability scores for each release.

See our API docs for more details.

An app hang or freeze is when your app fails to respond to user interactions, causing a negative impact on user experience. Bugsnag now captures app hangs with complete diagnostic information, including stack traces and breadcrumbs, to help you investigate and fix the underlying problems causing them.

Fatal app hangs, where the app does not recover, are reported by default. Additionally, Bugsnag can be configured to capture other non-fatal app hangs. See our docs to learn more and upgrade to the latest version of our iOS notifier to start reporting on app hangs.

We’ve improved the way Swift stack traces for iOS apps are displayed to help you identify the source of errors more quickly. The method name is now displayed more clearly—in some cases simplified and in other cases providing more detail.

These improvements are automatically applied to all newly received events from today onwards.

We’ve enhanced our detection to help you better understand if the app was being used on a jailbroken iOS device or rooted Android device when the error occurred. These insights are now more prominent in the average device state section of the error details page and you can also filter by them in the environment tab of the search builder.

Upgrade to the latest version of our Android, iOS, and React Native notifiers to take advantage of these enhancements.

For Android, iOS, and React Native apps, you can now identify whether a crash occurred while the app was launching. Crashes during launch have a high impact on user experience, so you can filter them in the dashboard and prioritize fixing them. Additionally, you can use Bugsnag to identify if your app is in a crash loop and dynamically deactivate features or clear data to prevent further crashes.

You’ll need to upgrade to the latest version of our Android, iOS, and React Native notifiers to gain access to this additional insight. See our Android and iOS docs for configuration details.

We've added a new Project Member role to give you more control over permissions on your Bugsnag projects. The new role allows collaborators to work on fixing errors but they cannot modify project settings or discard errors.

As part of these changes all existing Collaborators have become Project Owners. They now have the additional ability to manage access to their projects. As previously, Organization Admins have full permissions on all projects.

The new Project Member role is available on Enterprise plans. Please contact us to gain access or see our docs for more details.

Use Bugsnag to manage the stability of Node.js applications running on AWS Lambda. Details of the AWS Lambda context will automatically be included in error reports for effective debugging.

To get started, see our docs.

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, Symfony, 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.