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.
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:
Upgrade to the latest version of our macOS notifier to see the additional metadata.
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.
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.
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.
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.
