Sign up

beta_feedback_crash_submission_created

Learn about the BETA_FEEDBACK_CRASH_SUBMISSION_CREATED webhook event. Fired when a TestFlight tester submits a crash report with logs and device details.

App Store ConnectTestFlight
beta_feedback_crash_submission_created

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 a timestamp and the feedback submission ID, and nothing else. 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 channel in Slack or Discord within seconds, complete with crash diagnostics and device details. Your developers can start investigating immediately.


Common use cases


  • Route crash reports to your #bugs or #crashes channel
  • Get crash logs with stack traces directly in Slack or Discord
  • See which device models and OS versions are affected
  • Track crash frequency during beta testing periods

Example payload

Everything except the timestamp is a reference: no crash log, no tester, no device. Note that the submission ID is an opaque Apple string rather than a UUID, so validating it as one will reject real events.

{
  "data": {
    "type": "betaFeedbackCrashSubmissionCreated",
    "id": "a4319bc8-ed16-460b-8de6-ba9734b55631",
    "version": 1,
    "attributes": {
      "timestamp": "2026-09-12T20:53:20.729Z"
    },
    "relationships": {
      "instance": {
        "data": {
          "type": "betaFeedbackCrashSubmissions",
          "id": "AK7UjG-qL5QxXf3gIOGjbpQ"
        },
        "links": {
          "self": "https://api.appstoreconnect.apple.com/v1/betaFeedbackCrashSubmissions/AK7UjG-qL5QxXf3gIOGjbpQ"
        }
      }
    }
  }
}

What it looks like in Slack

Critical

Crash report from Priya Raman on iPhone 16 Pro (iPhone17,1) (18.6)

Email
priya@example.com
Device
iPhone 16 Pro (iPhone17,1)
Build
2.1.0 (4821)
Locale
en-US

Enrichment with p8 key

With a p8 key, Yeethook enriches this event with the full crash log, stack trace, tester name and email, device model, OS version, carrier, locale, and any comments from the tester.

Questions about beta_feedback_crash_submission_created

Does the webhook include the crash log?

No, it includes a submission ID and nothing else. Yeethook makes two calls with your p8 key — one for the submission and tester, one for the crashLog relationship — and still posts the message without the stack trace if the second call fails.

Why does the Build field show two numbers?

Apple does not return the build separately on a crash submission, so Yeethook reads the "Version: 2.1.0 (4821)" line out of the crash log text. The marketing version comes first and the build number sits in parentheses; when only one of the two is present the field shows just that one.

What does this event look like without a p8 key?

The headline falls back to "Crash report from a tester" and the message has no field rows, because the raw payload holds no state change for the fallback extractor to render. Tester, device, build and locale all depend on enrichment.

Why is the device model written twice?

Apple returns a hardware identifier such as iPhone17,1. Yeethook prints the marketing name and keeps the identifier in parentheses, so the raw value stays searchable when you are matching a report against a specific device generation.

Learn More

Official Apple documentation:

Get this event in Slack or Discord

Connect Yeethook to receive beta_feedback_crash_submission_created notifications in your team's Slack or Discord channels.

Get Started Free