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


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.

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 and how many occurrences there has been of this crash, as well as the breakdown of operating systems and versions of your app affected.


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

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.

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


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.

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