All Products
Search
Document Center

Crash report

Last Updated: Sep 10, 2021

Crash refers that an app stops functioning properly and exits unexpectedly. When a crash occurs, the client uploads the crash data in real time, and the data is displayed on the console with seconds or minutes delay.

Crash report shows app crash data such as crash count, crash rate, and crash trend over a period of time. The crash report aggregates crash data by the causes for crash, and displays statistics on the crash count, device count, and main device models of a specific type of crash.

Note: To view the crash report, ensure that you have accessed the MAS SDK and configured client tracking. For more information, see Access Android and Access iOS.

To view the crash report, complete the following steps:

  1. Log in to the console, click Products and Services > Mobile PaaS, and then select the target app.
  2. From the navigation bar on the left, click Mobile Analysis Service > Performance analysis > Crash report.
  3. Filter the crash analysis data by platform, app version, and time.

Crash overview

Present the minute-level crash count and crash rate in the line chart.

  • Crashes on the day: Total count of crash log files of the day (not distinct).
  • Crash rate on the day: Total crash log files (not distinct) divided by total active user/device logs that the client uploaded.

1

Crash classification

The data report in this area shows the data of crashes on the selected date.

Crash log files can be symbolized (iOS crash log files need to be symbolized while Android crash log files do not need), and classified according to the crash causes.

  • Crashes: Total count of the crashes of the same type (total number of log files of the same-type crash).
  • Accounts: Total distinct user IDs (counted by userID field in the logs) in the crashes of the same type. If no userID field is available in the logs, the value is 1 by default.
  • Devices: Total distinct device IDs (counted by device ID in the logs) in the crashes of the same type. If no device ID is available in the logs, the value is 1 by default.
  • Version: Version No. in the crash log file.
  • Details: Crash call stack in the log file.

2

Crash details

In the Crash classification section, click the content in the Details column to enter the crash details page which displays the error group, error sample and other information.

  • Error group:

    • Crashes: Total count of the crashes of the same type (total number of log files of the same-type crash).
    • Affected devices: Total count of the devices on which the crash occurred, deduplicated by device ID.
    • Proportion of affected devices: The proportion of total devices affected by such type of crash in the total devices experiencing crash.
    • Device models: Show the proportion of different device models experiencing crashes, and the device model with the highest proportion ranks top.
  • Error sample: Show the device details, log details and other information. You can switch the samples by clicking < and >.

    • Device details: Show the device ID, platform, user ID, device model, operating system version, and UUID.
    • Symbol parsing: Show the parsing state of the current log sample. For the log failed to be parsed, the failure reason (Failed to find the symbol file, Invalid symbol file, UUID not matched, etc) is displayed. It is supported to upload the symbol file for manual parsing.
      Note: For iOS app, crash log files can be symbolized with symbol file. If no symbol file is uploaded, the original content of the log file is displayed by default. Crash log files are symbolized in real time when crash log files are uploaded with minutes delay.
    • Log details: Show the crash log of the current sample. The log can be exported. See Crash tracking.
Note: If the device ID is empty or “-“, the device will not be counted.