All Products
Search
Document Center

Stuck analysis

Last Updated: Jun 23, 2021

Stuck analysis provides statistics on stuck times, stuck rate, and affected devices.

Definition of stuck

Stuck includes the following conditions:

  • Android:
  • iOS:
    • Startup stuck: The main thread did not complete the execution of a method within 5 seconds when the App started.
    • ANR stuck: The main thread of the App runtime did not complete the execution of a method within 5 seconds.

View stuck report

In the console, choose Mobile Analysis Service > Performance analysis > Stuck report and view the stuck rate, stuck times, affective devices, and stuck logs. In the stuck classification area, click the information in the Details column to view detailed stuck information.

  • Device details:
    • Device ID: The format is IMSI|IMEI.
    • Platform: Consists of 3 fields, which are appId-Platform-workspaceId.
  • Log details: Log records are separated by comma and contain complete error stacks. For the specific meaning of each field, see Log model > Performance tracking > Stuck tracking.

Stuck analysis is in quasi real time. Namely, you can view the preceding report after the App stucks and a stuck log is reported.

Integrate stuck analysis function

Android

Complete the following steps to integrate stuck analysis function to Android client:

  1. Access Mobile Analysis Service. For more information, see Access Mobile Analysis Service.
  2. Enable stuck monitoring. Based on the SDK version, see Add performance log.

iOS

Complete the following steps to integrate stuck analysis function to iOS client:

  1. Access Mobile Analysis Service. For more information, see Access Mobile Analysis Service.
  2. Enable stuck monitoring. Based on the SDK version, see Add performance log.