The previous release v3.2111.1 and v4.2111.2 mitigates CVE-2021-44228 (log4j remote command execution) and CVE-2021-45046 (log4j DOS) vulnerabilities in line with Elasticsearch guidance.
Customers who wish to also remove the class that contains the affected code (JndiLookup) can upgrade to this release.
We anticipate making a further release in January to include an updated version of Elasticsearch when it is available.
Mitigates CVE-2021-44228 (log4j remote command execution) vulnerability
The Elasticsearch service included as part of the Busgnag installation may be vulnerable to CVE-2021-44228 (log4j remote command execution) prior to this release, as input to the Bugsnag services could potentially be logged to the Elasticsearch slow log and therefore a crafted input string could be used to exploit the log4j vulnerability. We believe the risk to your Bugsnag installation is low as an exploit is only possible if the attacker has access to the Bugsnag On-Premise services. However, we recommend that you upgrade your installation as soon as possible, and if not already done restrict access to your Bugsnag services (see guidance here).
The latest build fixes minor bugs.
Fixes performance regression of handling larger payloads
The latest build fixes minor bugs and also includes the following new features:
You can now specify where Bugsnag pods are scheduled in your cluster by configuring node selector labels under Kubernetes > Pod scheduling, once configured you will need to add the corresponding labels to the nodes in your cluster to ensure that Bugsnag pods are scheduled correctly. This is only available in Clustered.
We’ve made enhancements to the memory diagnostics we capture for errors in Android apps, including total memory, free memory, memory usage, memory limit, low memory, and memory trim level. Understanding the memory pressure leading up to a crash and the overall memory health of a device can help you prioritize and fix errors caused by memory pressure with speed and precision.
Read our blog to learn more and upgrade to the latest version of our Android notifier to start capturing these memory diagnostics.
Streamline investigation into your most complex errors by understanding the state of each thread at the time the error occurred in your Android or iOS app. Errors captured in Android apps will now also include NDK thread states in addition to the existing JVM threads.
Upgrade to the latest version of our Android and iOS notifiers to see new thread state information.
If the user’s device is overheating, sometimes the OS can shut down the phone or kill apps and processes that are using too much CPU so that the device can cool down.
Bugsnag now captures thermal kills to provide visibility and diagnostics into these issues. Additionally, new breadcrumbs and thermal state metadata provide further insight so you can streamline investigation and debugging.
Upgrade to the latest version of our iOS notifier to take advantage of these enhancements.
Breadcrumbs will now be automatically captured to provide visibility into network requests that your app made in the run up to an error and how long these requests took. These diagnostics can help you understand if failed or slow network requests are causing errors so you can streamline investigation and debugging.
Upgrade to the latest version of our notifiers to see these additional breadcrumbs and see the Android and iOS docs for configuration instructions.
You can now see scene state and scene lifecycle breadcrumbs for errors in iOS and iPadOS apps built with UIScene. These breadcrumbs log user actions leading up to an error to help you streamline investigation and debugging workflows.
Upgrade to the latest version of our iOS notifier to see these additional breadcrumbs.
The daily and weekly summary emails provide an overview of important errors and team activity. Now, you can also see the app stability score and target indicators in these emails to help you gauge the current health of the app and progress against stability goals.
You have the flexibility to configure these emails to only notify you if the app’s stability is critical or below target. Ready our docs to learn more and get started in Settings under My email notifications.
You can now configure integrations for your projects via Bugsnag’s data access API. This will help streamline the management of integrations such as Slack and Jira, especially for organizations with many projects.
Read our docs to get started.
The latest build fixes minor bugs and also includes the following new features:
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.
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.
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.
We have added a configuration under Kubernetes > Pod runtime mode to configure whether pods should run as root or non root. We recommend not switching between the modes in an existing installation. This is only available in Clustered.
The latest build fixes minor bugs and also includes the following new features:
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.
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.
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.
We've made some changes to the dashboard to improve the performance.
Fixes issue with envoy-proxy configuration generation for containers on Docker 20.10.6
The latest build fixes minor bugs and also includes the following new features:
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 this update 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.
For Android, iOS, and React Native apps, you can now identify whether a crash occurred while the app was launching. Crashes during launch have a high impact on user experience, so you can filter them in the dashboard and prioritize fixing them. Additionally, you can use Bugsnag to identify if your app is in a crash loop and dynamically deactivate features or clear data to prevent further crashes.
You’ll need to upgrade to the latest version of our Android, iOS, and React Native notifiers to gain access to this additional insight. See our Android and iOS docs for configuration details.
We've added a new Project Member role to give you more control over permissions on your Bugsnag projects. The new role allows collaborators to work on fixing errors but they cannot modify project settings or discard errors.
As part of these changes all existing Collaborators have become Project Owners. They now have the additional ability to manage access to their projects. As previously, Organization Admins have full permissions on all projects.
Please contact us to gain access or see our docs for more details.
Use Bugsnag to manage the stability of Node.js applications running on AWS Lambda. Details of the AWS Lambda context will automatically be included in error reports for effective debugging.
To get started, see our docs.
The latest build fixes minor bugs and also includes the following new features:
Efficiently investigate and fix every Application Not Responding (ANR) error in your Android applications with enhanced stack traces for ANRs when the root cause is native or NDK code. The new NDK stack frames along with the existing JVM stack traces will provide complete visibility into the part of the code that was running when an ANR occurred.
To get started, upgrade to the latest version of our Android notifier.
Our Laravel, Syfony, and PHP notifiers now detect and report out of memory errors (OOMs). To get started, upgrade to the latest version and see the docs for any additional configuration.
We’ve improved how JavaScript errors are grouped for React Native projects to minimize duplicate errors being reported upon code modifications and to provide complete visibility into the impact of all errors over time.
New error groupings will no longer be created due to the line numbers changing because the improved grouping algorithm is based on the section of code an error is originating from rather than the line number, which can change when code is modified.
To upgrade, go to Project Settings > Default grouping.
Sometimes teams work in multiple issue tracker projects, such as a different one for each team responsible for a segment of the application’s codebase. Now, you can drive code ownership by automatically creating and linking issues to your team’s issue tracker project for errors occurring in your team’s codebase.
Linked issues can also be clearly seen in the Error Inbox and 2-way sync between Bugsnag and your issue tracker helps streamline debugging.
Contact us to gain access to this feature or see our docs for more details.
Existing snooze options allow errors to be snoozed until an event or time threshold is reached. Now, you can also snooze an error until it impacts additional users, so you are only alerted of it again when it becomes more important to fix. Customize the number of additional users impacted or select from some pre-set thresholds.
See the new options in the snooze menu.
Head to the Breadcrumbs tab of an event to see the new search and filtering capabilities. Select the type of breadcrumb or search from keywords to quickly find the specific breadcrumb you need to investigate the event.
Set up the new integration and configure notifications to drive real-time decisions about error prioritization and resolution in your Microsoft Teams channels. Streamline error triaging by changing the status of an error in Bugsnag to fixed, snooze, or ignore directly from within Microsoft Teams.
If you’re using the unofficial integration, migrate to this one to take advantage of notification filtering and streamlined triaging. Get started by reading our docs.
We’ve improved how errors are grouped for Ruby, PHP, Python, and Node.js projects to minimize duplicate errors being reported upon code modifications and to provide complete visibility into the impact of all errors over time.
New error groupings will no longer be created due to the line numbers changing because the improved grouping algorithm is based on the section of code an error is originating from rather than the line number, which can change when code is modified.
To upgrade, go to Project Settings > Default grouping.
Upgrade to our new tool for uploading source maps so you can unminify JavaScript stack traces reliably and with ease.
The @bugsnag/source-maps tool is a replacement for bugsnag-sourcemaps and can be used to upload source maps during your build process for React Native, browser JavaScript, and Node.js apps. Learn more in our docs.
You can now clearly see in the Error Inbox which application type, whether Android or iOS, was impacted by each error occurring in multi-platform projects, including React Native and Unity. Segmenting by this field can provide additional context to streamline error prioritization and debugging.
Comments you leave on errors can now be edited. After you save an edited comment, it will be marked as such.
In cross-platform projects, such as React Native, Expo, Unity, and Universal JavaScript, stack traces and threads for errors in the native layers are now shown in a consistent format, allowing you to more easily understand where the errors originated in the code.
You can now make sure your Releases dashboard shows only the releases you want to see by selecting to “Hide this release” using the dropdown menu at the top right corner of the release card. Should you want to undo this, select “Show hidden releases” from the dropdown menu at the top of the Releases dashboard.
Check it out in your Releases dashboard and see our docs for more details.
Shorten the time it takes to upload mapping files by upgrading to version 5.4.0 of our Android Gradle Plugin, which now supports compressed ProGuard, DexGuard and R8 mappings.
See our docs for more details.
