See every piece of tester feedback in Slack

The Problem

TestFlight testers submit feedback (crashes, screenshots, comments) through the TestFlight app. But that feedback sits in App Store Connect, buried in a tab that nobody checks often enough. Testers feel ignored, and bugs slip through to production.

The Solution

Yeethook routes all TestFlight feedback to Slack the moment it's submitted:

• Crash reports — With enrichment, includes full crash log, tester name, device details.
• Screenshot feedback — With enrichment, includes the screenshot image, tester comments, and device info.
• Build state changes — Know when builds are approved for external testing.

How to Set It Up

1. Sign up at yeethook.com.
2. Upload your p8 key for enriched feedback (strongly recommended).
3. Add your app and enable TestFlight event types.
4. Connect Slack — Route feedback to #testflight or #bugs.

Why Enrichment Matters

The base webhook just tells you "a crash was submitted" or "a screenshot was submitted." With your p8 key, Yeethook calls the App Store Connect API to fetch the actual crash log, the actual screenshot, and the tester's name and device info. This is the difference between a vague alert and actionable feedback.

Best Practices

• Respond to testers: Even though TestFlight doesn't have a reply feature, following up via email shows testers you value their feedback.
• Triage by channel: Route crashes to #bugs and screenshots to #feedback for different triage workflows.
• Pair with build states: Route external build state events to the same channel so you know which builds testers are using.