Release

The latest build fixes minor bugs and also includes the following new features:

New Project Overview Dashboard

We’re excited to announce the Project Overview Dashboard, a brand new view that provides key project-level analytics and insights.

Gain actionable insights into app stability and user experience, customize error views to keep an eye on errors impacting segments that matter to you, see an activity feed of the team’s progress in triaging and fixing errors, and more.

Read our blog to learn more and see the new Project Overview by clicking on “Overview” from the navigation bar on any project.

Streamline workflows with new integration labels

You can now add a label for each integration in settings, which will then be displayed with the integration name everywhere else in Bugsnag and help distinguish one integration from another.

This is especially useful for organizations that have, for example, configured multiple Jira integrations with the same Jira project and need to distinguish between these integrations in the dropdown when creating new issues for errors.

You can configure the labels in integration settings.

Breadcrumbs for Python

We’ve added support for breadcrumbs to our Python notifier. Breadcrumbs record events that happen in the run up to an error, making it easier to reproduce and fix.

Breadcrumbs will be automatically captured for HTTP requests and other errors, plus you can add your own manual breadcrumbs. All Python frameworks are supported including Django and Flask.

Upgrade the notifier to the latest version to get started.

Pod runtime mode

We have added a configuration under Kubernetes > Pod runtime mode to configure whether pods should run as root or non root. We recommend not switching between the modes in an existing installation. This is only available in Clustered.

Release

The latest build fixes minor bugs and also includes the following new features:

Major version of Unity notifier

We've released a major version of our Unity notifier (v5) including several new features, reliability improvements, and bug fixes.

The update includes app hang detection and improved out of memory (OOM) detection on iOS, improved detection of jailbroken or rooted devices, and much more.

See the Unity upgrade guide to get started.

Introducing Bugsnag support for Electron apps

You can now use Bugsnag to manage the stability of your Electron apps. Today, we have full support for capturing JavaScript errors. We’re excited to share that support for native errors is coming this Summer.

Get started by reading our docs.

Manage bookmarks in Bugsnag’s data access API

We’ve added new capabilities to our data access API to allow you to manage bookmarks, which are a set of saved error filters. Bookmarks are useful for keeping an eye on an error segment and also for customizing alerts and integrations.

Read our docs to learn more about how to create, update, or delete bookmarks via the API.

See additional metadata for macOS apps

New metadata included in macOS error reports will help you identify if your app was running through Rosetta on a Mac with Apple Silicon, providing additional information to help you prioritize and fix errors.

Rosetta allows apps built for Intel processors to run on Apple Silicon. The new metadata is shown on the “App” tab:

• runningOnRosetta will be true when the app is running on Rosetta
• binaryArch will show the CPU architecture of the binary being run

Upgrade to the latest version of our macOS notifier to see the additional metadata.

Improved Cocoa NSError grouping

An improvement to our grouping algorithm for NSErrors from iOS, macOS, and tvOS apps is now available. The improvement will prevent over-grouping of NSErrors by additionally using the ‘domain’ for grouping.

If the grouping improvement applies to your project, it is now available as an upgrade in Project Settings > Group errors > Default grouping.

Enhanced monitoring for iOS apps running on macOS

Bugsnag now has full support for iOS apps running on macOS, either through Mac Catalyst or natively on Apple Silicon Macs.

Diagnostics for errors captured include the model of Mac the app was running on, the version of macOS, and the version of iOS that Mac Catalyst provides, so you can triage and resolve errors when your iOS app is running on a Mac.

Upgrade to the latest version of our iOS notifier to take advantage of these enhancements.

Filter for an empty field to streamline error investigation

When filtering through errors, you now have the ability to filter by the absence of a default or custom field, to help you streamline error investigation and debugging. This can be useful to isolate errors that don’t have a value for a particular field, for example, when investigating errors in feature flags, you can understand if these errors are occurring outside of feature flags too.

See the new [empty] filtering options in the search builder and pivot tables.

Dashboard performance improvements

We've made some changes to the dashboard to improve the performance.

Release

Fixes issue with envoy-proxy configuration generation for containers on Docker 20.10.6

Release

The latest build fixes minor bugs and also includes the following new features:

Discard errors from Firefox browser extensions

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.

Application stability information now available in Bugsnag’s data access API

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.

Gain visibility into iOS app hangs or freezes

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.

Improved Swift stack traces for iOS apps

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 this update onwards.

Drive error prioritization and investigation with enhanced detection of jailbroken and rooted devices

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.

Gain visibility into crashes happening during launch

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.

Introducing improved project permissions

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.

Please contact us to gain access or see our docs for more details.

Introducing support for Node.js on AWS Lambda

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.

Release

The latest build fixes minor bugs and also includes the following new features:

Enhanced stack traces for Android ANRs

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.

Out of memory (OOM) detection for Laravel, Syfony, and PHP

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.

Improved grouping for JavaScript errors in React Native projects

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.

Integrate with multiple issue tracker projects to drive code ownership and streamline the debugging workflow

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.

Prioritize errors more efficiently with new snooze options

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.

Streamline debugging with breadcrumb search and filtering

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.

Introducing Microsoft Teams integration

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.

Improved error grouping for Ruby, PHP, Python, and Node.js projects

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.

New source map upload tool

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.

Quickly understand whether errors occurring in React Native and Unity apps are impacting Android or iOS users

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.

Introducing flexibility to edit comments

Comments you leave on errors can now be edited. After you save an edited comment, it will be marked as such.

Streamline debugging with enhanced stack traces and threads for errors in cross-platform projects

In cross-platform projects, such as React Native, Expo, Unity, and Universal JavaScript, stack traces and threads for errors in the native layers are now shown in a consistent format, allowing you to more easily understand where the errors originated in the code.

Hide releases from your Releases dashboard

You can now make sure your Releases dashboard shows only the releases you want to see by selecting to “Hide this release” using the dropdown menu at the top right corner of the release card. Should you want to undo this, select “Show hidden releases” from the dropdown menu at the top of the Releases dashboard.

Check it out in your Releases dashboard and see our docs for more details.

Upload compressed mapping files for Android projects

Shorten the time it takes to upload mapping files by upgrading to version 5.4.0 of our Android Gradle Plugin, which now supports compressed ProGuard, DexGuard and R8 mappings.

See our docs for more details.

Release

The latest build fixes minor bugs and also includes the following new features:

Introducing a streamlined experience for managing access to projects

Admin users can now more easily search and bulk update project access for collaborators in organization collaborator settings. This is especially useful for organizations with many projects in Bugsnag.

Configurable scaling options for Event Storage Service

Adds configuration for scaling event storage service in Single Machine and Clustered. Increasing the number of event storage services should give greater capacity and reliability when traffic is very high. This should be set to at least half the value of the event worker scale.

Release

The latest build fixes minor bugs and also includes the following new features:

Introducing user stability analytics

Gain comprehensive insights into application health and user experience with the new user stability analytics for all mobile and web project types. You’ll need to upgrade your notifier to the latest version to see the user and session stability analytics in the Stability Center and the Releases dashboard.

Get started by reading our blog.

Note: This feature requires further configuration in the settings Performance > Maximum memory for redis to store user stability data for Single Machine and Application performance (Advanced) > Maximum memory for redis to store user stability data for Clustered.

Introducing audit logs

Admin users can now see an audit log of key actions collaborators take in Bugsnag, such as deleting a project or changing an integration, providing them visibility into user permissions, and the ability to investigate and rectify unexpected changes.

Contact us to gain access to this feature or see our docs for more details.

Automatically provision and deprovision collaborators via SSO

You can now securely manage user permissions in Bugsnag via your SSO provider, so you can streamline new user onboarding, deprovision access for users who have left, and automatically synchronize any user attribute changes between your SSO provider and Bugsnag.

Contact us to gain access to this feature or see our docs for more details.

Improved Unity symbolication on Android

You can now get human readable stack traces from Unity library code on Android with our improved symbolication capabilities.

Upgrade to version 5.3.0 of the Bugsnag Android Gradle Plugin to automatically upload the new mappings when you build your app. See the docs for more details.

Set thresholds for automatic issue creation

We’ve released an enhancement to our issue tracker integration which allows you to set thresholds for automatic issue creation by specifying what frequency an error must reach before an issue is automatically created. This prevents new issues from being created for low priority errors with a few events.

Get started by reading our docs and find the new option in your issue tracker integration settings in Bugsnag.

Release

The latest build fixes minor bugs.

Important Note:

If you are upgrading from a version lower than v3.1909.0 or v4.1909.0 then any NDK SO mapping files will be migrated. The dashboard will still be usable, but it may take some time for new events to be processed after upgrading.

Release

Fixes issues with slow event processing with source maps when in folder format. Also allow configuration for using S3 as an alernative for storing mapping files.

Release

Allow maximum number of concurrent connections for minio to be configurable.