Skip to main content

Crashes Page

It includes all information and actions in one place to make it easier for you to have all that you need to enhance your app.

Yasmin avatar
Written by Yasmin
Updated over 2 weeks ago

Here's an overview of how it initially looks like when you start receiving crashes:

The details you can find on the crashes page:

  • Percentage of Crash-Free Sessions: The percentage of total sessions that didn't end in a crash. ANRs and non-fatal errors like caught exceptions are not counted as crashes.

  • Percentage of Crash-Free Users: The percentage of total users who did not experience a crash.

  • Number of Crashing Sessions: The total number of sessions in which a crash occurred.

  • Number of affected users: The total number of unique users who experienced a crash.

  • Number of affected sessions: The total number of sessions affected by crashes (Fatal, Non-Fatal, or ANR).

  • List of Crashes with:

    • Number of occurrences

    • Number of users affected

    • Minimum & Maximum app versions

    • First & last seen of that crash

Crash Details Page

When selecting a specific crash, additional insights and actions become available.

Actions Available on the Crash Page:

We want to maintain the same look and feel as bug reports, so you will not feel confused, as the crash page includes the same actions:

  • Mark as duplicate

  • Status update

  • Assignee assignment

  • Priority setting

  • Integrations

Among other actions, you can find as well such as:

Activity & comments

Notifications related to activities should be accessed through the crash report when the drawer is opened.
​

Public URL

You can create a public URL to share it with whomever you want.

Tags​

All created tags will be displayed, and you can add or delete them from the Tags page in settings.

Occurrences page

It opens all the users affected by the crash with the number of occurrences.

You'll be able to read more about it here.

Crash Graph

Only five curves are displayed by default.

The first 4 are the app versions with the max number of new crashes during the week, sorted descendingly.

The last item, "Others," contains an aggregation of the other app versions that had new crashes during the week.

There are two types you can choose from:

  1. Per App version:

    Each app version has a color where the x-axis is the timeline, and the y-axis is the number of occurrences

  2. Aggregated:

    Total of all app versions where the x-axis is the timeline and the y-axis is the number of occurrences.

Symbolication/Deobfuscation

For the missing dsyms or mapping files, a warning alert will be displayed and action on how to upload the files:

  1. An alert message will be displayed: "This crash isn't symbolicated/deobfuscated. Please upload the dSYMs files of app_version".

  2. A button called "Upload missing files."

Some Notes: 

  • If we have many app versions, we start grouping them into the Others category.

Did this answer your question?