Bugsnag updates
Bugsnag updates

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.

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.

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.

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.