Stuck falls into startup stuck and ANR stuck. When a device gets stuck, the client uploads the stuck data in real time, and the data is displayed on the console with seconds or minutes delay.
Stuck type | Android | iOS |
Startup stuck | The app fails to leave welcome page and enter home page within 30 seconds after startup. | When the app starts, the main thread does not finish executing a method within 15 seconds (30 seconds for iPhone6 and below). |
ANR stuck | System ANR stuck, see ANRs on Android Official Website for definition. | When the app starts, the main thread does not finish executing a method within 10 seconds (20 seconds for iPhone6 and below). |
To view the stuck report, ensure that you have integrated the MAS SDK and configured client tracking. For more information, see Quick start and Add SDK.
The lag report allows you to learn the total number of lags, lag rate, number of affected devices, and view the details of startup lags and ANR lags by category.
To view the stuck report, complete the following steps:
Log in to the console, click Products and Services > mPaaS, and then select an application.
From the navigation bar on the left, click Mobile Analysis Service > Performance analysis > Stuck report.
Select platform, version, and time to view the stuck statistics data.
Stuck overview
Present the minute-level statistical data of startup stuck and ANR stuck in the line chart.
Indicators | Startup stuck | ANR stuck |
Stuck count | Startup stuck times on the day. | ANR stuck times on the day. |
Stuck rate | Number of times the application startup stuck/Number of times the application is started. | Number of times the application ANR stuck/number of times the application is started. |
Affected devices | Total number of devices that have startup stuck, deduplicated by device ID. | Total number of devices that have ANR stuck, deduplicated by device ID. |
Stuck details
The data report in this area shows the Startup stuck and ANR stuck data on the selected date.
Stuck count: Total stuck count of the same type (total number of stuck logs).
Accounts: Total distinct user IDs (count by
userIDfield in the logs) in the stuck of the same type. If nouserIDfield is available in the logs, the value is 1 by default.Devices: Total distinct device IDs (count by device ID in the logs) in the stuck of the same type. If no device ID is available in the logs, the value is 1 by default.
Version: Version No. in the stuck log file.
Details: Stuck call stack in the log file.
For Android models, you can view the relevant stack information in the details of the stuck report. The stack information of the startup stuck provides the stack content of all current threads for developers to troubleshoot.
For iOS models, you can only view the stack information corresponding to non-startup stuck in the details of the stuck report. The stuck report does not provide the stack information of the startup stuck.
Stuck classification details
In the stuck classification section, click the content in the Details column to enter the stuck details page which displays the error group, error sample and other information.
Error group:
Stuck count: Total stuck count of the same type (total number of stuck logs).
Affected devices: Total count of the devices on which the stuck occurred, deduplicated by device ID.
NoteIf the device ID is empty or "-", the device will not be counted.
Proportion of affected devices: Total devices affected by current stuck type/total stuck devices.
Device models: The percentage of stuck times of different models is displayed from high to low.
Error sample: Displays the device details, log details and other information of the current sample. You can switch samples by the <and> buttons.
Device details: Shows the Device ID, Platform, User ID, Device model, and Operating system version of the current sample.
Log details: Show the stuck log of the current sample. The log can be exported. See Stuck tracking.