Common Issues Concerning CrashSight Integration and Reporting in iOS

Below are some common issues concerning CrashSight integration and reporting in iOS:

1.1 Crashes not reported post SDK Integration?

• Verify the AppId.
• Ensure SDK initialization occurred before the crashes.
• Check internet connectivity.
• If crashes were reported during testing but ceased, you might need to uninstall and retest the app   due to CrashSight's data protection mechanism.
• Ensure no third-party crash detection components (like Firebase, Facebook, Google Mobile Ads) are causing compatibility issues.
• Check if system-induced app terminations are causing the crashes.

1.2 Why the need for Java Runtime Environment for symbol table uploads?

• The symbol table extraction tool requires it.

1.3 Symbol table upload failed due to UUID mismatch?

• Symbol table's UUID changes with each build. The current build's symbol table is needed to reproduce post-build crashes.

1.4 Why are dependency library extensions different?

• iOS SDK 9.0 and above use libc++.tbd extension. Other versions use libc++.dylib extension.

1.5 Different SDKs and their features?

• iOS SDK: Collects iOS app crashes and lags, computes app operation statistics.
• Cocos Plugin: Collects crashes and script errors of Cocos-based apps.
• Unity Plugin: Collects crashes and script errors of Unity-based apps.

Unreal Plugin: Collects crashes and script errors of Unreal-based apps.