The BETA_FEEDBACK_CRASH_SUBMISSION_CREATED event fires when a TestFlight tester submits a crash report through the TestFlight app. This is one of the most valuable events for development teams because it provides real crash data from real devices.
When does it fire?
This event triggers whenever a tester taps "Share with Developer" after a crash occurs during beta testing. The tester can include additional comments describing what they were doing when the crash happened.
Payload highlights
The base webhook payload includes the app ID, build number, and the feedback submission ID. The real value comes from enrichment — when you provide a p8 key, Yeethook uses the App Store Connect API to pull the full crash log, tester name, email, device model, OS version, and any comments the tester attached.
How Yeethook helps
Without Yeethook, crash reports sit in App Store Connect until someone remembers to check. With Yeethook, crash reports arrive in your #bugs Slack channel within seconds, complete with the full crash log and device details. Your developers can start investigating immediately.
Common use cases
- Route crash reports to your #bugs or #crashes Slack channel
- Get full crash logs with stack traces directly in Slack
- See which device models and OS versions are affected
- Track crash frequency during beta testing periods