Crash Reporting-CrashSight

FAQs

FAQs for the CrashSight Android SDK

1.How can I view the Logcat log in CrashSight during development?

• Refer to the parameter configuration and set the debug mode to True during initialization.

2.Why do hundreds of crash reports come from the same user in a single day? Will this consume the user’s mobile data?

• Reporting from a single user has mobile data limit, and before CrashSight reaches that limit, it will report normally.

3 .When is the timing by which CrashSight reports crashes?

• CrashSight will try to make a report whenever a crash occurs. If the network condition is poor when a crash occurs, or some other factor causes the report to fail to be made, it will be reported the next time reporting conditions are met.

4.Why can’t I see the logs on the page after completing the CrashSight integration?

• If you only load CrashSight-related plug-ins and JAR packages, CrashSight will not work. You need to initialize CrashSight within the code and configure the debug mode parameters. After the initialization process, you can view the CrashSight log.

5.Do I need to configure a symbol table for each version?

• Yes.

6.If I do not configure the restoration of the symbol table, will this affect the reporting of anomalies? What factors influence the reporting?

• Restoring the configuration of the symbol table will not affect the reporting function.
• If the configuration is not configured, the web page will only display the original crash stack, which is not conducive to troubleshooting.

7.If the configuration of the symbol table is restored, why does the display log still contain no line numbers?

• It is required that the software version of the log must match the software version of the restored symbol table being configured.

8.Crash after SDK access not reported

• Check whether APPID is set correctly
• Whether the initialization of SDK is completed before Crash;
• Whether the network is available;
• If a report is suddenly not reported during the test, it may trigger CrashSight’s traffic protection mechanism. Please uninstall the App and test it again (it will not affect the Crash accuracy rate of real users).
• Is there any other third-party component with the ability to capture Crash used? If so, put the initialization of CrashSight after this component;
• Whether because of insufficient memory is killed by the system, whether because of insufficient memory and stuck (these two situations often occur in the low-end machine, often extremely stalled before the occurrence).

9.UnsatisfiedLinkError (UnsatisfiedLinkError) failed to start when using CrashSight’s library.

10.What information does CrashSight collect about the device?Is there user privacy?

11.What does the “visible” message in the Crash page mean?

12.Found a security vulnerability in the “AddJavaScriptInterface” of the CrashSight SDK through (third party) static code?

3 Unity SDK FAQ:

1.After initializing the SDK, why can’t I catch reporting C# exceptions?

A. check whether there are other registered Application. RegisterLogCallback (LogCallback) logic, due to the system default LogCallback is unicast, so only keep a callback instance, you can call the CrashSightAgent. RegisterLogCallback (CrashSightAgent. LogCallbackDelegate) method to replace the log callback registration;
B. Check whether the SDK components of the corresponding platform have been integrated into the project
C. Check if CrashSight is repeatedly initialized in the platform and Unity script
D. Check if the test crash was caught internally

2.Why does the application crash directly after a C# exception?

A. If you encounter this scenario, you can annotate initWithAppID in the script, preserve the EnableExceptionHandler method call, and initialize the SDK component in the corresponding Android or iOS project.