Crashes and Issues¶
Crashlytics aggregates crashes into what we identify as the source issues- particular lines of code that seem to be causing the same type of crash. If, for example, you had 30,000 crashes reported, these may be attributable to 20 issues. Crashlytics will identify those 20 and assign them a level of severity, called an impact level.
When looking at your dashboard, you will see a list of issues. Clicking on an individual issue will take you to an issue summary page, with aggregate information about all the crashes (e.g. device type and OS). You will also see any versions that have experienced the crash in previous versions of your app. To see individual crash reports, click the “View All Sessions” button to navigate to individual crash reports. Details like custom keys and logs can be found on the individual crash reports.
We rank each issue based on a number of different factors, including the number of unique users affected and the total count and frequency of the crash.
Our goal is to show you the most significant, high impact issues first. This way, you know which ones to address that will have the most positive impact on your user base. Crashlytics will also alert you if the impact level of a given issue changes.
When you’ve fixed an issue, you can “close” it from the Fabric dashboard. For any crashes that come in on that version of your app or any version of your app that we have already seen that crash occur in, it will remain closed. Any crashes for it are still handled and added to the closed issue.
However, if the same crash comes in for a version of your app that hasn’t yet experienced this crash, for example, a new version of your app, we will re-open that issue. Also, you can choose to be notified by email that an issue regression has happened.
If you don’t want an issue to ever be re-opened automatically due to an issue regression, then after closing the issue, click on the lock to lock the issue. If you ever need to unlock the issue, just click on the lock once more.
Filter Closed Issues¶
On the Issue list page, you can use filters to see all closed issues or issues for a certain version using those filters.
On the Issue list page, for any issue that has occured on multiple versions, you will see the earliest and latest version that the issue has occured.
If you’re looking for a specific crash, you can search on all user information, custom keys, and the following issue details:
- File name
- Method name
- Exception Type
- Line Number
- Issue notes
Search tokens must be >=4 characters long. All searches by default are trailing wildcard searches and are searchable for the most recent 30 days.
The “Crash-Free Users” percentage represents the percentage of users that have not experienced a crash in the past n days, where n is the number you’ve selected from the dropdown menu.
For example, if your app has 10 users, and, over the course of a week, one person per day experiences a crash, your Crash-Free User percentage for the past 7 days is 30%.
This number is different from the Crash-Free Users percentage in our graphs, which calculates the number of Crash-Free Users on a daily basis. For the example above, this graph would show each day’s Crash-Free User percentage as 90%.