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.
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.
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.
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
The default breadcrumb limit will be 100, which can be increased using the “Max Breadcrumbs” config option.
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.
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.
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).
A gif speaks at least a 1000 words so see the changes in action 👇
To spell it out in a little more detail:
) next to it to allow you to toggle between the simplified and fuller views.If you have any feedback on this new feature please contact us through the Bugsnag dashboard.
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.
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.
Starting today 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.
