What's new

See the latest updates to BugSnag, including new features, improvements, and bug fixes.

March

Ability to support short lived tokens in Linear plugin
Added App Hang detection on Android – see docs for installation instructions.
Add support for reporting errors with HTTP requests in Android (bugsnag-android v6.23.0) and Cocoa (bugsnag-cocoa v6.36.0).
New docs for setting up the BugSnag integration with Microsoft Teams using Webhooks – see docs.
Errors introduced filter now supports matching by release stage, so you can focus on issues newly introduced in specific stages (like production) rather than across all stages.

Add commenting functionality to the public Data Access API – see docs.
Improve communication of payment attempts when a card is updated – emails now sent on each retry.
Support Pascal case property names for BugSnag configuration in a .plist (bugsnag-cocoa v6.36.0)
Expo source maps now uploaded using the BugSnag CLI inside the EAS plugin (bugsnag-expo v54.1.0)

To mitigate against malicious data injections, the dashboard now shows a warning when a user clicks a link that comes from customer-generated content.
On-Premise release: v5.2601.0

Add trace, session and device IDs to the list of event fields in the Data Access API.
Deprecation of the @bugsnag/source-maps package and repo. This has now been replaced with the BugSnag CLI and NPM wrapper @bugsnag/cli.
Add tools for snoozing errors and linking Jira issues to the MCP server.
Improve handling of permissions error on dashboard when setting default project percentile.

Fix a dashboard error when creating a performance saved search with a string value only.
Fix a dashboard glitch where the first mouse over truncated text doesn’t show the tooltip.
Fix display of “inline” marker for stackframes to identify the inlined frame, rather than the frame containing it.
Ensure tooltips close correctly when Percentiles are selected on the dashboard.
Hide Custom Filter button on dashboard for existing filters

Added new controls to the Android (v6.21.0) and Cocoa (v6.35.0) SDKs for developers to explicitly set the delivery strategy for events. This allows finer controls over whether events should be persisted to disk and when delivery attempts are made. See the Android and iOS docs for usage information on this deliveryStrategy field.
Added new options to the notify method in Android (v6.21.0) and Cocoa (v6.35.0) SDKs to report handled errors with more control. This allows developers to prevent capture of certain fields, such as stacktraces, to prevent unnecessary overheads. You can also now use the isFatal flag to treat a caught exception as an unhandled error. See the Android and iOS doc.
App start metrics for performance monitoring of React Native apps can now include the native loading period, to provide a full picture of where time is spent (available from bugsnag-js-performance v3.4.0). See docs for the setup instructions to enable this feature.
Add “any secondary” entries to release suggestions for performance comparisons in the dashboard.

Improve session timeouts – for users on multiple devices, avoid timeouts triggering logouts across all sessions.
New operation to the Data Access API for retrieving a project by its API key.
Suggestions not showing correctly for the assigned-to field – the collaborator name/email is now shown instead of ID

(BugSnag CLI) CLI doesn’t support AppleDouble metadata files in dSYMs – fixed in bugsnag-cli v3.7.0.
(Ruby SDK) Fixed issue with events reported early during startup, before SDK is configured. In bugsnag-ruby (v6.29.0) this is now output as an explicit warning rather than a URL parse error.
(Unity) Mark code-generated files as out-of-project to improve grouping.
Loading more release stages in dashboard causes the project overview to show a loader.
Default time filters should not change between error and performance views in dashboard.
Incorrect behaviour when toggling all with negative filters in the release stage selector on the dashboard.