- Documentation
Application Performance Management Plus
User guide
Client monitoring
App monitoring
FAQ
iOS-side monitoring
Crash events cannot be displayed
iOS-side monitoring
Crash events cannot be displayed
Crash events cannot be displayed
- First, check that the initialization configuration is correct, especially the appId and appToken fields. The appID must be the ID of the application you created on APMPlus.
- Check that your trigger method is correct. The correct trigger method is as follows:
- Add a crash simulation event in your code
- Use Xcode to compile and install your app onto a simulator or a real device
- Start the app on the simulator or the real device and trigger the crash simulation event
- Start the app again to trigger crash event reporting
- Do not use Xcode Run to launch the app and trigger a crash event. Xcode disconnects when the app crashes, so the SDK cannot record the crash event.
- Crash events must be triggered after SDK initialization. If the crash is triggered automatically, add an appropriate delay before triggering it. This prevents the scenario where a new crash occurs before the previous one is reported when restarting the app.
- After confirming that the above flow is correct, you can capture packets locally and filter by /monitor/collect/c/crash. If this endpoint is captured, the crash has been reported.
Last updated: 2026.10.23 11:17:23