All Collections
Crash Reporting
Introducing Instabug Crash Reporting
Introducing Instabug Crash Reporting

Deep dive into the crash reporting product and all of its features.

Moataz avatar
Written by Moataz
Updated over a week ago

Crashes can disrupt or actually ruin the experience of your app, leaving your users frustrated because of the instability which could lead them to delete your app. None of the best apps makers want to get slammed with bad reviews about their stability. Instabug helps you address severe crashes quickly and assess their impact on users. Automatically receive detailed lightweight reports when your app crashes, monitor your app’s health, and fix issues faster. 

Here is a quick video shows you the product in action:

In this article, you can find the key functions in Instabug's Bug Reporting & Feedback:

  1. Receiving Crash Reports on Dashboard

  2. Exploring Crash Report Types

  3. Crash List and Severity

  4. Looking Into The Report Details

  5. Taking Actions on The Report

  6. Replying to Affected Users

  7. Forwarding Your Reports With Integrated Tools

  8. Automating Your Workflow With Rules

Receiving Crash Reports on Dashboard

Instabug helps you get notified when your app crashes with the exact level of detail.
Crashes are automatically captured and listed on your dashboard. The different occurrences of the same crash are grouped together.

On the crashes page, analytics about your app health during the past week are displayed. you can see the total number of crashes, the percentage of crashing sessions, the number of affected users and the distribution of occurrences over the app versions.

Exploring Crash Report Types

There are two types of crash reports; fatal and non-fatal errors.
The fatal errors are the one your application reports automatically and the non-fatal errors are the ones you can report manually

Crashes List and Severity

Crash details will show you the number of occurrences, affected users, app versions impacted, and when the last crash occurred.

Our Crash severity metric will help you identify a crash’s impact on users, and let you address the highest severity first. When the crash is reported for the first time, its severity is low. Then, depending on several parameters that we look at, its severity might change to be moderate, high or critical.

Your crash reports will be labeled by their type and you can filter them by type, severity, app version, OS, and much more.

Looking Into The Report Details

The crashes page in your dashboard lists all of your crash reports. When you select one, it opens the crash overview page, where you can find the report details.

Crash Report Details

Get an overview of the crash occurrences crashing sessions caused by this particular crash against the days of the previous month. Each line color represents a different app version, and take a more detailed look into OS, app versions, and devices

Stack Trace
The stack trace of the crash offers you a detailed under the hood look into frames and threads. The most important frames highlighted in blue. These highlighted frames are your application's frames. 

You can add custom tags to your bug reports right from the dashboard or from the SDK. These tags can later be used to filter reports or set custom rules from your dashboard.

Here you can find a detailed explanation for all the content in the crash report.

Crash Occurrence Details

If you need to narrow down the cause further, View the crash occurrences.
You can also filter occurrences to pinpoint what you’re looking for.
Some basic details will give you a quick understanding of the specific occurrence.

With every occurrence, you can get a quick overview showing the attached feedback and essential details including default, custom user attributes, and much more.

Repro Steps
With Repro steps cut down on debugging time. Easily check all of the interactions a user makes with your app up until the app crashed. Reproduce the issue by seeing the user’s actions on each screen they visited up to sending the occurrence. Here you can find all the events that get logged data and how to disable/enable this feature.

For Crash Reporting, the screenshots are always disabled as the data is silently collected without any interaction from the user. This decision is part of our ongoing commitment to end-users' privacy.

Session Profiler
With the session profiler you can identify device related issues at a glance. Device details such as CPU load, memory, storage, connectivity, battery, and orientation are highlighted 60 seconds prior to the report.

Here you can find the data breakdown and how to disable/enable this feature.

Report Logs
Multiple logs provide a breadth of contextual data, and help you highlight and solve specific issues. Here are the types of logs that are sent with the crash report:

  1. Console Logs: Capturing all console logs and displays them on your dashboard.

  2. Instabug Logs: Capturing logs that are similar to NSLog() and print(), but they have the added benefit of having different verbosity levels. 

  3. Network Logs: Tracking all network requests performed by your app; Requests details, along with their responses.

  4. User Events: Logging custom user events throughout your application and they will automatically be included with each report

  5. User Steps: Tracking each step a user has taken since the beginning of the session until a report is sent. 

Need to deep dive? Here is our technical guide for it.

Taking Actions on The Report

Updating and Assigning 

Manage issues by updating their status, priority, and assigning reports to any team member who has access to the application. All those parameters can later be used to filter the bug reports

Activity and Comments

You and your team members can leave comments on the bug reports. You can also mention a member by typing a @ before the name or tag another bug report by typing a # before the report number.

Replying to Affected Users

What if a crash affected many of your users and you fixed it. Don't you want to inform them about the new app version containing the fix? Or, maybe you want to get in touch with a reporter to check if they can help you reproduce a crash.

You can easily reply to all the affected users by a certain crash, pick a few of them, or even reply to an individual affected user. You can include saved replies, action buttons or attachments.

Once you send them a message, they receive an in-app notification. They can check your message and reply back from within your app.

Forwarding Your Reports With Integrated Tools

If your team is used to certain tools, you can forward all the data you get on the dashboard to them. You will have the same detailed issues that you get on your Instabug dashboard forwarded over there. We support a variety of tools like Slack, JIRA, Zendesk, Github, Zapier and much more. For more details about the integrations, check the following link.

Automating Your Workflow With Rules

With Rules you can optimize your workflow even further and automate most of the actions. Assign specific issues to your team, forward them directly to your chosen tools, and much more.


We take data privacy as seriously as you do. Keep your data secure and start using Instabug’s crash reporting SDK and get real time alerts.

Start using Instabug’s crash reporting today, to stay on top of crashes, and improve your app.

You can start using Instabug SDK simply by adding one line of code to your application. Here is how to integrate the Instabug SDK.

Related Articles

After you learn about bug reporting, you might want to check out Bug Reporting, In-App-Surveys, and Feature Requests.

Did this answer your question?