Building native mobile apps can be a daunting challenge. Even if you ignore the choice of building separate iOS/Android apps or using cross-platform technology, writing native apps is hard. The development process of native apps involves a lot of testing and debugging. While the app is still under initial development this usually happens on test devices of the developers or dedicated testers. When problems arise or the app crashes, these incidents are often observable and can be debugged.

Everyone’s software crashes. As an engineer, you don’t feel your users’ frustration unless they reach out to customer support, write bad reviews, or tweet about it. This feedback is often lacking relevant information to resolve the issue. In some cases, you can re-engage with the customer, but that process is time-consuming and inefficient. Another option would be to examine the crash reports, but sometimes they don’t give sufficient insight to fix the problem.

BugSplat recently added Crash Grouping and Aggregation in Search. Grouping crashes provides new insight into your product's stability and allows you to prioritize fixes based on a wide variety of criteria. To try out this new feature, navigate to the Crashes page.

This article will focus on debugging JavaScript code within Firefox’s Developer Tools. The Dev Tools within Firefox are extremely powerful which will speed up finding and fixing bugs. We’ll be using Raygun Crash Reporting to find the stack trace and the line of code the error occurred on. You can sign up for a free 14-day trial here. So, let’s dive in!

We've just released a way to track the number of users affected by a crash! If you navigate to the Summary page, you'll now see a column labeled 'Users Affected’, this column shows how many unique users have been affected for each row in the crash summary table. With the data provided by this new column, you’ll have additional information available for prioritizing fixes. The ‘Count’ column is unchanged, and reports the total number of crashes reported by all users.

Working with Serverless computing is like riding an electric bike. You get speed, flexibility, automatic assistance to scale with ease. Development is usually hassle-free because you can focus on code and only pay for usage of the service. Except when your users hit an error. Debugging that issue feels like your bike’s battery just died while climbing a steep hill.