Release
Fixes issue with metric gathering when using node selector scheduling.
Fixes issue with metric gathering when using node selector scheduling.
The latest build fixes minor bugs and also includes the following new features:
Bugsnag On-Premise Clustered now uses Replicated KOTS for installations and management. KOTS makes it easier to manage Bugsnag On-premise Clustered, via an admin console. Our documentation has been updated for this change and can be found here.
Stack traces can contain a lot of information, to the point that it can sometimes be quite hard to see the wood for the trees. Usually the first thing a developer wants to know when looking at a stack trace is simply “what was the chain of function calls that led to this error?” But between full paths for source code files, long method signatures, template / generic arguments and attributes there can be a lot of noise, making this harder than it should be.
We’ve just rolled out some visual changes to simplify the data we show for Objective-C, Swift and C++ stack frames (including Android NDK, minidumps and Unreal Engine).
To spell it out in a little more detail:
We welcome your feedback at support@bugsnag.com.
We have introduced a new way of uploading Android NDK component symbols. The improvements will give you:
To get started upgrade to version 7.4.0 of the Bugsnag Android Gradle plugin. See the docs for more details.
Improves event processing when under heavy event load. Also adds new alert for user stability redis memory usage. This only affects Clustered.
The latest build fixes minor bugs and also includes the following new features:
Bugsnag’s support for Expo is now compatible with Expo Application Services (EAS) Build. By installing the Bugsnag config plugin to your Expo app you will get your source maps uploaded and your release tracked automatically.
To find out more see the docs.
Bugsnag will automatically remove old unused mapping files as a scheduled job based on configured retention period. We have introduced new configuration options for enabling/disabling deletion job, retention period, job schedule and throttling deletions. Note that if you are upgrading to this version the first run of the job will occur 1 week after the upgrade due to some changes required for the job to process correctly.
This release mitigates CVE-2022-42889 Text4Shell vulnerability.
Also note that this release removes the support for Flowdock as team notification.
Fixes issue with minidump event processing
The latest build fixes minor bugs and also includes the following new features:
You can assign errors to a team in addition to assigning to an individual collaborator.
Assigning errors is a great way to encourage ownership of errors and drive progress towards your stability goals. By assigning errors you can avoid errors being left unresolved by making teams or individuals accountable.
To begin assigning errors to a team, click the person icon on the error details page and find the team in the list.
Following hot on the heels of Bugsnag’s initial Flutter release, we have added:
Click on the links above to get started, or see the changelog or our original Flutter blog post.
Fixes issue with SCIM accessibility
The latest build fixes minor bugs and also includes the following new features:
We've launched support for Teams to help you streamline the management of project access within your Bugsnag organization.
Organization Administrators can create teams and assign collaborators to them, and then grant project access to both teams and individual collaborators.
Soon we'll be rolling out support for automatic provisioning of teams from your single sign-on (SSO) provider via SCIM.
Visit your Bugsnag settings to get started.
You can now use Bugsnag to manage the stability of your Electron apps. Earlier this year, we released support for capturing JavaScript errors including unhandled exceptions and unhandled promise rejections in the main process and the renderer processes. We’re excited to share that you can now also capture native crashes via minidumps.
Get started by reading our blog.
Our .NET library is now officially compatible with all versions of .NET, including .NET Core, .NET 5 & 6 and .NET Framework.
Find out more in the changelog and our .NET docs.
We’ve added watchOS to our range of supported Apple platforms (alongside iOS, macOS, tvOS).
Unhandled exceptions are automatically captured by Bugsnag, allowing you to gain actionable insights into stability, and make data-driven decisions about prioritizing and fixing the bugs that matter.
Take a look at our docs to get started.
We're excited to support error monitoring and stability management for Flutter mobile applications. Now, you can automatically capture bugs impacting the user experience, gain actionable insights into stability, and make data-driven decisions about prioritizing and fixing the bugs that matter.
The new Flutter notifier library initially supports Android and iOS apps.
Check out our blog to learn more and get started by reading our docs.
The latest version of our Unity library uses a new mechanism for detecting C# exceptions, giving more informative stack traces and now including inner exceptions.
This release has a major version bump release as it has an impact on grouping for some errors. Please see the upgrade guide for more details.
PHP developers can now join those from platforms in making data-driven decisions about new feature rollouts and gaining confidence in accelerating releases with actionable observability insights from the Features Dashboard.
Learn more about the Features Dashboard in our blog. To get started, see our docs for Laravel, Lumen, Symfony and other PHP.
We’ve released a minor improvement to stack traces in iOS. If a stack frame comes from a function in an embedded framework, we now show the name of that framework. Previously we showed the name of the containing app.
This release removes support for Bugzilla 4 as an issue tracker.
Also note that the configuration backup command for Single Machine has been updated, ensure that your backup process uses the new command. The updated command can be found here
The latest build fixes minor bugs and also includes the following new features:
When configuring frequently occurring error notifications, you can now filter them by user impact thresholds so that you only get alerted when an error impacts a certain number of users in a timeframe, such as 100 users in an hour.
User thresholds filters are available to configure notifications for email, Slack, and other team chat integrations. They can also be applied to automatic issue creation rules for Jira and other issue trackers.
We’re excited to introduce an integration with Linear, allowing teams to automatically create issues in Linear from Bugsnag to manage bug fixes and streamline debugging workflows.
You can configure an integration with Linear in Project Settings > Issue tracker. Learn more about issue tracker integrations in our docs.
We’ve released more updates to our Unity notifier.
C# events and exceptions raised while the device is disconnected from the internet are now persisted until connection is restored.
Similarly, when running on Windows or WebGL, events and sessions will persist until a connection is available and the device ID will persist between game launches.
Our packages also now support External Dependency Manager for Unity (EDM4U).
Find out more in the changelog (releases 6.2.0 and 6.3.0) and upgrade your notifier to gain access to these updates.
We've released a major version of our Cocos2d-x notifier (v2), to include several new features, reliability improvements, and bug fixes.
See the Cocos2d-x upgrade guide to get started.
The latest build fixes minor bugs and also includes the following new features:
Make data-driven decisions about new feature rollouts and gain confidence in accelerating releases with the observability and actionable insights in the Features Dashboard.
Real-time visibility into errors introduced by each feature or experiment variant helps you understand how it is impacting the quality of the application and user experience.
Learn more about the new dashboard in our blog and get started by reading our docs.
In addition to Android and iOS games, our Unreal Engine notifier library now also supports macOS games. Automatically capture bugs impacting the gaming experience, gain actionable insights into stability, and make data-driven decisions about prioritizing and fixing the bugs that matter.
Learn more in our recent blog and get started by reading our docs.
We've released a major version of our Unity notifier (v6). It includes UPM (Unity Package Manager) support, automatic Bugsnag initialization prior to the first scene being loaded, and consistency and usability improvements.
See the Unity upgrade guide to get started.
We're excited to support error monitoring and stability management for Unreal Engine mobile games. Now, you can automatically capture bugs impacting the gaming experience, gain actionable insights into stability, and make data-driven decisions about prioritizing and fixing the bugs that matter.
The new Unreal Engine notifier library initially supports Android and iOS games.
Check out our blog to learn more and get started by reading our docs.