BugSnag Enterprise updates
BugSnag Enterprise updates

New release BugSnag On-Premise Clustered v5.2302.3




Fixes scale down issues when running an advanced deployment.

New release BugSnag On-Premise Clustered v5.2302.2




Adds config for handling very high event volumes.


This release also adds some new services which might require more resources on the cluster.

Important Note:

This release also changes the behaviour for the "Maximum memory for redis to store user stability data" config option. This will now also affect the disk size of the redis (redis-session-service-users) and will set disk size to be 2x the value here in GB, eg. value of 500MB will equal disk size of 1GB. Ensure that the disk size for that redis is set to the correct value before deploying. You can follow https://docs.bugsnag.com/on-premise/clustered/resizing-disks/ to resize the redis disk.

New release BugSnag On-Premise Single Machine v3.2302.1 and Clustered v5.2302.0




The latest build fixes minor bugs and also includes the following new features:

Let BugSnag Triage Errors for You

Triaging errors can be repetitive and often follows the same decision-making process, e.g. assigning errors to a specific team or an individual collaborator. BugSnag allows you to create custom rules to automate error triaging to make sure that each error is assigned to the best individual or team for the job. Learn more about how automatic triaging improves collaboration and error response time. Stay tuned for updates about our public API, coming soon.

Read the docs to get started.

See the impact of feature flags and experiments in your Ruby applications

Bugsnag's Ruby library now allows you to attach feature flag and experiment info to your error reports. This unlocks the Bugsnag Features Dashboard which allows you to quickly understand whether a feature flag or experiment is responsible for errors.

Learn more about the Features Dashboard in our blog. To get started with features and experiments in Ruby read the docs for Rails, Rack, Rake, Sinatra, Que, Sidekiq or general Ruby.

Automate Dart symbol uploads for your Flutter apps

When building Flutter apps for release you can strip the debug symbols for a lighter app package, which can dramatically reduce the size, as well as allowing for code obfuscation.

If you do this you need to upload the symbols files to Bugsnag in order to have readable stacktraces in your error reports. This was a rather fiddly process but we've just released tooling to automate it, for both Android and iOS builds. To get going, see the docs.

Send more breadcrumbs from your mobile apps

You can now send up to 500 breadcrumbs with your error reports from your Android, iOS, React Native, Flutter and Unity apps. Seeing more activity in the run up to an error gives you better visibility and helps you fix errors faster. At the same time, we have introduced smart breadcrumb trimming so that if your error event is too large to be received by Bugsnag we will remove breadcrumbs until it is small enough.

To enable the larger breadcrumb limit, ensure you have at least

Bugsnag Cocoa v6.22.0,
Bugsnag Android v5.28.0,
Bugsnag React Native v7.18.1,
Bugsnag Flutter v2.3.0 or
Bugsnag Unity v7.5.0.

The default breadcrumb limit will be 100, which can be increased using the “Max Breadcrumbs” config option.

Report your Laravel Vapor errors to BugSnag

Laravel Vapor allows you to host Laravel sites serverlessly. BugSnag Laravel now supports Vapor, so you can receive actionable insights into your app’s stability. See the docs to get started.

Send errors from within web workers and service workers

BugSnag now supports both web workers and service workers with our new @bugsnag/web-worker package. This includes support for monitoring errors in service workers required by Chrome Extensions using Manifest V3.

Read the docs to learn more.

Important Note:

Version v3.2302.1 requires Docker version 20.10.7 or higher.

New release BugSnag On-Premise Clustered v5.2211.1




Fixes issue with metric gathering when using node selector scheduling.

New release Bugsnag On-Premise Single Machine v3.2211.0 and Clustered v5.2211.0




The latest build fixes minor bugs and also includes the following new features:

Clustered deployment changes

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.

Tame your Objective C, Swift and C++ stack traces

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:

  • For the 3 fields in each stack frame (module, source file and location, function) we show by default the simplest version we can. We remove the path from the file locations and attempt to reduce the function information down to its name.
  • When the field is expandable we show an icon (image.png) next to it to allow you to toggle between the simplified and fuller views.
  • If you shift-click the icon it will expand or collapse that field for all stack frames in the project.
  • Android NDK stack traces now look like other C++ stack traces, which means the same error will look the same in x-platform C++ frameworks like Unreal Engine

We welcome your feedback at support@bugsnag.com.

Better symbolication for Android NDK

We have introduced a new way of uploading Android NDK component symbols. The improvements will give you:

  • Faster build times, because the symbol files to upload to Bugsnag are quicker to generate
  • More accurate symbolication
  • The ability to use Bugsnag Android Gradle Plugin with NDK r23 or higher

To get started upgrade to version 7.4.0 of the Bugsnag Android Gradle plugin. See the docs for more details.

New release Bugsnag On-Premise Clustered v4.2210.4




Improves event processing when under heavy event load. Also adds new alert for user stability redis memory usage. This only affects Clustered.

New release Bugsnag On-Premise Single Machine v3.2210.1 and Clustered v4.2210.2




The latest build fixes minor bugs and also includes the following new features:

Use EAS Build in your Expo apps

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.

Automatic deletion of older unused mapping files

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.

Important Note:

This release mitigates CVE-2022-42889 Text4Shell vulnerability.

Also note that this release removes the support for Flowdock as team notification.

New release Bugsnag On-Premise Single Machine v3.2207.1




Fixes issue with minidump event processing

New release Bugsnag On-Premise Single Machine v3.2207.0 and Clustered v4.2207.1




The latest build fixes minor bugs and also includes the following new features:

Assign errors to a team to drive error ownership

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.

More capabilities for Flutter

Following hot on the heels of Bugsnag’s initial Flutter release, we have added:

  • network breadcrumbs (docs)
  • navigation breadcrumbs (docs)
  • "native-first": support for Flutter components within existing iOS and Android apps (docs)

Click on the links above to get started, or see the changelog or our original Flutter blog post.