. . .

Crash reporting

To help ensure you deliver a great user experience and a stable application, ApiOmat Analytics includes crash reporting in real-time. You can view which errors are occurring, which users are experience crashes and identify crashes based on OS, device, carrier network and other criteria so that developers can fix issues as quickly as possible.

images/download/attachments/19433135/crashes-overview.png

The crashes page comes with an overview dashboard as well as a detailed list of crashes. You can apply filters to the list to identify specific issues, devices, app versions any other relevant information.

images/download/attachments/19433135/2017-11-17_13h04_49.png

Actions

Crash reporting helps developers fix bugs, and ApiOmat Analytics allows you to take actions on specific crashes that have occurred. You can select an action or multiple actions and take the following actions:

  • Mark as resolved

  • Mark as unresolved

  • Mark as seen

  • Mark as hidden

  • Mark as not hidden

  • Delete

Simply select the errors from the list and click on perform action, as shown in the image below.

images/download/attachments/19433135/2017-11-17_13h07_43.png

Detailed reports

You can access a detailed report by clicking on view from the list of crashes. The detailed view offers details into the error message, the state of the devices at the time of the crash (RAM usage, Disk usage, battery level, time app was running) as well as detailed information about what devices and app versions are effected, how often the crash occurred.

images/download/attachments/19433135/crash-details.png

Users can share the report with developers who do not have access to ApiOmat Analytics and comments can be made. Once the error has been addressed, it can be marked as resolved.

Additionally, if you are using the user profiles, you can view exactly which app users have been effected by the error.

* link only available in Enterprise Documentation