2026 Release Notes

January

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.