Explanation of Common Terminology of Mobile APP Crash Capture Solution CrashSight (Part 1)

CrashSight provides all-platform (mobile/PC/host) developers with full-link closed-loop professional services such as crash exception capture, reporting, analysis, and avoidance solutions. Help developers quickly locate and solve abnormal problems, reduce product crash rate, and improve user experience.

Domestic: https://crashsight.qq.com
Overseas/Overseas: https://crashsight.wetest.net

Common terms for CrashSight are as follows:
● abnormal
The crashes, freezes, ANRs, and errors that occur during the running of the app are collectively referred to as exceptions.
● Crash A crash occurs when a user crashes while using the app, which is counted as a crash.
● Stalling occurs when a user is using the app, and it is counted as one stalling. The default stalling time is 5s, and custom time is also supported.
● ANR
When the user is using the app, a pop-up box appears, indicating that the app is unresponsive, which is counted as an ANR, and the ANR is only used for Android platform applications.
● Errors actively reported Exception, Error, or script (such as C#, Lua, JS, etc.) errors are collectively referred to as errors.
● Occurrence Times When an exception occurs and is recorded and reported, it is counted as an exception occurrence.
● If an exception occurs on one device that affects users, it is counted as one affected user. Within the specified time range, if a device has multiple exceptions, only one will affect the user.
● User abnormal rate, such as user crash rate, user freeze rate, user ANR rate, user error rate, etc., will affect the ratio of users/connected users.
● The abnormal rate of times, such as the number of times of crash rate, the number of times of freeze rate, the number of times of ANR rate, the number of times of error rate is the ratio of the number of occurrences / the number of times of networking ● The number of times of networking is the number of startups + the number of times of networking across the sky.
● Cross-sky networking users do not start the application, only the application process runs in the background, and it exceeds zero, it is counted as a cross-sky networking.
● The following scenarios are counted as one startup. 1. After the app is completely exited and restarted, it is counted as one startup; 2. After the app is switched to the background, it is switched to the foreground after 30 seconds, and it is counted as one startup. If it does not exceed 30 Switching to the foreground in seconds does not count as a startup.
● Networked users take the device as the judgment indicator, and each connected device is a networked user. Within a specified time range, if a device repeatedly conducts networking behavior, it is only counted as one networking user.

Write at the end:
CrashSight provides developers with exception capture, reporting and analysis services. Help developers quickly locate and solve abnormal problems, reduce product crash rate, and improve user experience. Support all mobile/PC/host platforms, including:
platform:
Mobile: iOS, Android
PC side: Windows
Host side: Nintendo Switch, PS4, XBOX
language:
C/C++/C#, Java, Object-C/Swift
engine:
Unity, UE4, Cocos
Go to the official website now:
Domestic: https://crashsight.qq.com
Overseas/Overseas: https://crashsight.wetest.net