Once configured, any unhandled exceptions that lead to crashes (along with any caught exceptions you choose to report) will be recorded automatically and shown in the Crash section for your app.

Click on the app, expand Crash in the left hand menu and select "Issues"

Issues

Each issue will show the platform (iOS or Android) on which the issue occurred, when the issue was opened (i.e. when the crash first occurred), how many installs are affected and how many device models are affected.

Issue

Filtering Issues

If you have both iOS and Android versions of your app, then all issues affecting your apps will be shown here, in a single-pane-of-glass. However, you can use the drop down menus at the top of the Issues view to filter the list of issues shown.

Filtering Issues

You can filter issues by:

  • Type (Fatal or Non-Fatal)
  • Status (New, In Progress, Blocked, Fixed, Unable to Reproduce, Rejected)
  • Operating System version
  • Timeframe (Past 30 days, Past 60 days or Past 90 days)

You can multi-select options from each drop-down. Click "Apply" to update the list of issues.


Viewing an Issue

To view more details about an issue, select that issue in the list.

The panel to the right-hand side will show how many installs have been affected, how many occurrences there has been of this crash, as well as a breakdown of operating systems and versions of your app affected. It will also show when the issue first occurred and when the issue last occurred.

Occurrences

Multiple occurrences of the same crash are grouped together in the same issue. This lets you prioritize the issues that are having the biggest impact on your user-base (i.e. those issues with the highest number of affected installs).

The middle pane shows the stack-trace for the latest occurrence of an issue as well as important information about the install that this occurrence of the crash affected, including:

  • Device model (or if this occurrence was on a simulator)
  • App Version
  • Location when issue occurred
  • Date and time the issue occurred
  • Free memory on device when issue occurred (iOS only)
  • Locale setting of device when issue occurred

Stack Trace

You can navigate between occurrences of the same crash using the Prev and Next buttons to view other stack traces and information about the install that those occurrences of the crash affected.

For issues that occur on Android, you can also view the system logs (providing your app has this permission).

System Logs

Finally, you can view all status changes and any comments left on an issue by your team in the bottom pane.

Comments


Updating an Issue

You can update the status of an issue by clicking the drop down at the top right of the middle pane and selecting a new status.

Update Status

Status changes are saved automatically and recorded in the comments section of the issue.

Issue Status and Workflow

Issues can be in one of three open status types (New, In Progress, Blocked) or one of three closed status types (Fixed, Unable to reproduce, Rejected). The table below describes each status as well as what happens when there is a new occurrence (as this depends on the status of that issue).

State Status Description New Occurrence?
Open New A new issue requiring attention. Occurrence will be added to same issue.
Open In Progress Issue has been acknowledged and a fix is in progress. Occurrence will be added to same issue.
Open Blocked Fix cannot be progressed at this time e.g. further information required. Occurrence will be added to same issue.
Closed Fixed Issue has been resolved. Occurrence will be added and issue re-opened to New status.
Closed Unable to reproduce Unable to identify cause and attempts to reproduce have been unsuccessful. Occurrence will be added and issue re-opened to New status.
Closed Rejected Issue is not being fixed e.g. only affected older operating systems Occurrence will be added only. Issue remains in Rejected status.

If there are one or more issues in an open state, the App Dashboard will show an amber, warning alert for Crash. If one or more of these issues have New status, the App Dashboard will show a red, critical alert.

Commenting on an Issue

When working on an issue or updating the status of an issue, it is good practice to leave a comment for your team and/or your future self explaining what you are doing.

Add comment

Merging Issues

Multiple occurrences of the same crash are grouped together in the same issue. This lets you prioritize the issues that are having the biggest impact on your user-base (i.e. those issues with the highest number of affected installs).

However, should you decide that two issues that are not grouped together are in fact caused by the same crash, then you can manually merge issues. From the context menu for the duplicate issue, select "Merge"

Merge

Enter the number of the issue you want to merge into and click "Merge"

Merge into Issue