At BugSplat, we have a unique view of how uncaught crashes can impact individual teams (and entire companies) through our work building tools to find and fix bugs in live applications. We've seen firsthand the difference it can make when teams have a workflow for reporting every defect that makes it into production and when they don't.

BugSplat's new auto-grouping feature is a powerful way to automatically group crashes in a way that's meaningful to your team. Normally, crashes are grouped by the top of the call stack. But sometimes this grouping isn't ideal. For example, if the top of your call stack is KERNELBASE!RaiseException (a Windows OS function) you'd probably prefer the crashes were grouped by a different stack frame. That's what BugSplat's auto-grouping feature does!

As React is the most popular JavaScript framework for creating component-based applications, you have access to a solid ecosystem of tools, resources, and best practices that can help with React debugging when something goes wrong. To create a high-quality React application, you can’t skip over the debugging phase of your software development life cycle including everything from addressing error messages coming up in the development phase to monitoring live errors in production.

Finding and fixing bugs is a critical part of the development process, both in development and production, but is it possible to be more effective in less time? A poll of thousands of software industry members conducted by Stripe revealed that the average software development team spends up to 42% (Stripe/Harris) of their time on tasks in service of fixing bugs. That's almost half of all developer time spent maintaining old code instead of writing new code.

Let’s start by stating the obvious: an exception is a problem that occurs during the runtime of a program which disrupts its conventional flow and exception handling is the process of responding to an exception. In Android, not handling an exception will lead to your application crashing and you seeing the dreaded “App keeps stopping” dialog. This makes handling exceptions incredibly important, and let’s face it: no one is going to use an app that continually crashes.

In this blog post, I’m going to talk about how to integrate Raygun4JS with React at a deeper level than what is provided out-of-the-box. None of these things are needed for Raygun4JS to do its primary job (reporting errors that happen on your website) but provide useful extra value for determining how your React application is performing and what is going wrong when an error occurs.

React Native has become the predominant development framework for cross-platform mobile applications. By interacting with native APIs largely under the hood and requiring only a fractional proportion of platform-specific code, it allows you to build applications for iOS, Android, and the browser using the same declarative JavaScript. But this cross-platform adaptability has its downsides.

Picking the best iOS crash reporting tools available in 2023 is a tall order. The market has continued to get more competitive, and a best-in-breed tool needs to monitor crashes, generate crash reports, filter and group errors, plus perform other tasks on top. In this article, we’ve collected the 15 best iOS crash reporting tools to help you make the right decision for your particular requirements.

One of the most requested features for Crash Reporting has been the ability to perform a search across all of your applications rather than by one application at a time (the default behavior). It’s not hard to see why it’s a popular feature request - rather than manually performing the same search across many applications, it would be super handy to perform one search and understand the impact of the search results across all of your applications immediately.