Get TestFlight crash reports in Slack with full crash logs

The Problem

When a TestFlight tester encounters a crash, they submit a report through the TestFlight app. That report sits in App Store Connect until someone manually checks the feedback tab — which could be hours or days later.

For fast-moving teams, this delay means bugs ship to more testers, tester trust erodes, and critical issues go unnoticed.

The Solution

Yeethook catches the BETA_FEEDBACK_CRASH_SUBMISSION_CREATED webhook the moment a tester submits a crash report and delivers it to your Slack channel.

Without a p8 key: You get a Slack notification with the app name and build number.

With a p8 key (recommended): Yeethook calls the App Store Connect API and enriches the notification with:

• Full crash log with stack trace
• Tester name and email
• Device model (e.g. iPhone 15 Pro)
• OS version (e.g. iOS 18.2)
• Tester comments

Everything arrives in a single Slack message. No need to open App Store Connect.

How to Set It Up

1. Sign up at yeethook.com and create a team.
2. Upload your p8 key for enriched crash reports (recommended), or choose Manual Setup.
3. Add your app — Quick Start imports it from App Store Connect automatically.
4. Connect Slack — Create a webhook and route crash events to your #bugs channel.

That's it. The next time a tester submits a crash report, it lands in Slack.

Best Practices

• Dedicate a channel: Route crashes to #bugs or #crashes so they don't get lost in a general channel.
• Pair with screenshot feedback: Also route BETA_FEEDBACK_SCREENSHOT_SUBMISSION_CREATED to the same channel for complete tester visibility.
• Use enrichment: The p8 key is what makes this truly useful. Without it, you just get a notification that a crash happened. With it, you get the full crash log.