Statistics
Last updated
Last updated
The IMQA Crash statistics page shows diversified statistical indexes based on measured errors. This page enables you to analyze how many errors have occurred in a specific app version and the user environment the error mainly occurred in. You can also analyze by class, device, and screen.
The IMQA Crash statistics screen consists of the following.
❶ Daily Errors ❷ Rate by rank/OS/country ❸ Crash rates (by version) ❹ Class error rate ❺ Device error rate ❻ Activity error rate
You can check the error count trends and error count on a specific date by recording the error count by date for the last 15 days. For web/hybrid apps, ‘Web Crash’ is additionally displayed.
Crash: Counts the number of crashes that occurred for the last 15 days. (Excluding ANR, Web Crash)
Web Crash: Counts the number of web crashes that occurred for the last 15 days.
ANR: Counts the number of ANR that occurred for the last 15 days. * Android project only
If the error count increased sharply on a specific date, see if there were any changes in the app version in question. In addition, if you check both the session count and app launches on that date, it will be helpful to analyze the indexes that show the cause of the error.
Currently the distinction between crash and ANR is only visible in Android projects.
You can check the rate of the errors occurring for the last 15 days by rank, OS, and country. (The storage period may vary depending on the customer.) Through a stacked bar graph, you can determine the number of errors occurring in a specific version and the degree of optimization of that version.
You can check the total error count and the rate of several OS versions on a cumulative bar graph based on a specific app version. If you place a mouse pointer on the bar of individual app versions, tooltips will be displayed.
Total error count: Counts the number of errors occurred in the specific app version. You can check the error count by OS version in the displayed tooltip.
Error count by OS version: Counts the number of errors occurred in each OS version.
The following can be analyzed using the index of the OS rate by app version.
The OS version with many errors.
The app version with many errors.
The OS version with many errors based on the app version.
For example, if many errors occurred in OS8.8.0 of the app version 1.5, but the errors of OS 8.8.0 decreased dramatically in the app version 1.6, we can analyze that the OS 8.8.0 version is optimized in the app version 1.5.
You can check the rate of the errors that occurred in a specific class for the past 15 days. (The storage period may vary depending on the customer.)
Error rate: Displays the rate of the errors occurred in each class.
You can analyze the class that caused many errors.
You can check the number of the errors occurred in a specific device for the past 15 days. (The storage period may vary depending on the customer.)
Error Count: Counts the number of errors occurred in each device.
You can analyze the device that caused many errors. “Unknown Device” means the device information was not collected. An example of this is a case where a device, such as Mac, was tested with a simulator.
You can check the rate of the errors occurring in a specific activity for the past 15 days. (The storage period may vary depending on the customer.)
Error rate: Displays the rate of the errors occurred in each activity.
You can analyze the activity that caused many errors. If an item is displayed as “null”, it means that the error occurred before the activity is loaded.
