The latest build fixes minor bugs and also includes the following new features:
Bugsnag fully supports Hermes, React Native’s new JavaScript engine for Android, in Bugsnag React Native v2.22.6 and above.
Learn more about how to get started in our blog.
If your organization uses SSO to access Bugsnag, you can now configure your SSO provider to encrypt SAML assertions.
Learn more about SSO in our docs.
The latest build fixes minor bugs and also includes the following new features:
Easily monitor errors happening in your experiments, A/B tests, and feature flags with Bugsnag’s new custom filters for arrays.
This allows you to efficiently discover and fix problematic issues introduced by a new feature or experiment without having to set up a new custom filter for each feature flag or experiment.
Find out more in our blog and contact us to get started.
Bugsnag’s new Clustered version of On-Premise is now available.
Organizations who need to process high error volumes and need their Bugsnag instance to be highly available can deploy Clustered On-Premise to scale Bugsnag across multiple machines. Contact us to upgrade.
Fixes intermittent issue with downloading the docker image for iOS/macOS/tvOS support during installation/upgrades.
The latest build fixes minor bugs and also includes the following new features:
We're excited to announce full stability monitoring for your Expo apps.
Expo is a free and open source toolchain built on React Native to help you rapidly build native iOS and Android apps from the same JavaScript codebase.
Bugsnag for Expo includes all the features of our popular React Native support including full deobfuscated stack traces, diagnostic metadata, breadcrumbs, and release stability.
Find out more in our blog or get started with our docs.
We've added support for React Native's Random Access Modules (RAM) bundle format.
RAM bundles can improve the performance of apps with a large number of screens by loading sections progressively as they are needed.
Source maps generated with the react-native ram-bundle command can now be uploaded to Bugsnag and will be used to unminify stack traces to identify the line of code where an error is originating.
Find out how to generate and upload source maps for RAM bundles in our docs.
Bugsnag now provides the ability to set stability score targets so you have full control over your release dashboard.
There are two targets:
Your project's stability targets have been automatically set based on stability over the last 30 days, but we recommend that you review them and set targets appropriate for your apps.
Set your targets in project settings, or find out more in our blog.
The latest version of our Android notifier will automatically detect Application Not Responding (ANR) errors in your Android and React Native apps.
ANRs happen when the app is unresponsive to user input for 5 seconds, because the UI thread is blocked. The user is given the choice to close the app or wait.
Actionable ANR error reports in Bugsnag will be grouped by cause and include all the diagnostic information needed to prioritize and fix them. They'll also contribute to the stability score of your releases so you can measure improvement over time.
Find out more in our blog.
If you are upgrading from a version lower than v3.1805.0 then the "method" field will be reindexed. The dashboard will still be usable, but it may take some time to be able to search on the "method" field for historical events after upgrading.
The latest build fixes minor bugs and also includes the following new features:
We've launched an enhancement to our Data Access API to make it easier to respond to GDPR requests from your users, if you are reporting personally identifiable information in your Bugsnag errors. The new endpoints allow you to retrieve and delete data in bulk.
Learn more about how to use the API in our GDPR examples.
We’ve released Universal JavaScript support. This launch combines our previous browser JS and Node.js libraries into a single, cohesive library that supports all JavaScript projects whether they run in the browser or on the server.
Bugsnag Node users will benefit from the greatly modernized and improved interface. To learn more about Universal JS and this release, see our blog.
We've released a major new version of the Bugsnag notifier for Unity. Version 4.0.0 includes support for Unity games and apps running on Windows, in addition to existing support for Android, iOS, macOS, tvOS and WebGL.
Find out more in the changelog and the docs.
If you are upgrading from a version lower than v3.1803.0 then events will be reindexed into Elasticsearch. The dashboard will still be usable, but it may take some time before all historical events and errors are visible. You can monitor the progress of the reindex by running replicated admin status | grep elasticsearch_events_indexed. It can take around 1 hour to reindex 1 million events.
If you are upgrading from a version lower than v3.1805.0 then the "method" field will be reindexed. The dashboard will still be usable, but it may take some time to be able to search on the "method" field for historical events after upgrading.
The latest build fixes minor bugs and also includes the following new features:
We’ve released first-class support for Spring, including automatic session tracking that unlocks the Releases dashboard and the stability score. If you’re currently using Bugsnag Java on a Spring application, we recommend upgrading to take advantage of the automatic functionality and improvements. Learn more.
We've recently rolled out some improvements for JavaScript projects bundled using webpack.
Now, only the stack frames that relate to your code are shown by default, and frames from library code are hidden. Click the 'full trace' button to show all the frames.
Additionally, if you are reporting builds using our build tool integration you can now click on the icon on the right hand side of the stack trace to deep link to the line of code in GitHub, GitLab, or Bitbucket.
If you are upgrading from a version lower than v3.1803.0 then events will be reindexed into Elasticsearch. The dashboard will still be usable, but it may take some time before all historical events and errors are visible. You can monitor the progress of the reindex by running replicated admin status | grep elasticsearch_events_indexed. It can take around 1 hour to reindex 1 million events.
If you are upgrading from a version lower than v3.1805.0 then the "method" field will be reindexed. The dashboard will still be usable, but it may take some time to be able to search on the "method" field for historical events after upgrading.
The latest build fixes minor bugs and also includes the following new features:
We've released a major new version of our Android NDK notifier library.
We recommend upgrading to the new version to take advantage of better reliability and more detailed debugging information for errors originating from your native C and C++ code.
Additionally, recent updates to our Android Gradle plugin significantly improve the performance of generating the mapping file uploaded to Bugsnag during your build.
If you are upgrading from a version lower than v3.1803.0 then events will be reindexed into Elasticsearch. The dashboard will still be usable, but it may take some time before all historical events and errors are visible. You can monitor the progress of the reindex by running replicated admin status | grep elasticsearch_events_indexed. It can take around 1 hour to reindex 1 million events.
If you are upgrading from a version lower than v3.1805.0 then the "method" field will be reindexed. The dashboard will still be usable, but it may take some time to be able to search on the "method" field for historical events after upgrading.
The latest build fixes minor bugs and also includes the following new features:
We've added pre-built Grafana dashboards to allow you to monitor the performance and health of your Bugsnag instance and set up alerts.
See monitoring your instance for more information on how to get started with Grafana and setting up notifications for alerts.
If you are upgrading from a version lower than v3.1803.0 then events will be reindexed into Elasticsearch. The dashboard will still be usable, but it may take some time before all historical events and errors are visible. You can monitor the progress of the reindex by running replicated admin status | grep elasticsearch_events_indexed. It can take around 1 hour to reindex 1 million events.
If you are upgrading from a version lower than v3.1805.0 then the "method" field will be reindexed. The dashboard will still be usable, but it may take some time to be able to search on the "method" field for historical events after upgrading.
The latest build fixes minor bugs and also includes the following new features:
We’ve launched the stability score which you can now see in your updated Releases dashboard. The stability score replaces the crash rate—it is shown for every release and helps you quickly see when app stability drops so you can take action and fix problematic bugs.
Learn more on our blog or go to the documentation.
If you are upgrading from a version lower than v3.1803.0 then events will be reindexed into Elasticsearch. The dashboard will still be usable, but it may take some time before all historical events and errors are visible. You can monitor the progress of the reindex by running replicated admin status | grep elasticsearch_events_indexed. It can take around 1 hour to reindex 1 million events.
If you are upgrading from a version lower than v3.1805.0 then the "method" field will be reindexed. The dashboard will still be usable, but it may take some time to be able to search on the "method" field for historical events after upgrading.
The latest build fixes minor bugs and also includes the following new features:
You can now share bookmarks with everyone on your project.
Shared bookmarks make segments of errors visible for other teammates to enable quicker debugging.
Create a bookmark or edit one you already use and share it with everyone on the project. To share a bookmark click on the context menu for that bookmark and select "Share".
Find out more in our blog post or documentation.
If you are upgrading from a version lower than v3.1803.0 then events will be reindexed into Elasticsearch. The dashboard will still be usable, but it may take some time before all historical events and errors are visible. You can monitor the progress of the reindex by running replicated admin status | grep elasticsearch_events_indexed. It can take around 1 hour to reindex 1 million events.
If you are upgrading from a version lower than v3.1805.0 then the "method" field will be reindexed. The dashboard will still be usable, but it may take some time to be able to search on the "method" field for historical events after upgrading.
Bugsnag Enterprise updates