Event details

Select any event from the list to open the detail panel. On desktop this appears on the right side of the page. On mobile it opens as a full-screen overlay with a back button.

The detail panel has several sections, described below.

Summary

The top of the panel shows the event's key metadata:

• Event type — the Apple event constant (e.g. beta_feedback_crash_submission_created) and subtype if present. You can copy the full event type string with the copy button.
• Status — a color-coded badge showing the delivery outcome.
• App — the name and bundle ID of the app the event belongs to.
• Timestamps — when the event was received and when it was delivered (if applicable).
• Event ID — the unique identifier for this event, with a copy button.

If the event type has a reference page on the Yeethook site, a link takes you there for more context about what the event means and when it fires.

Key fields

Below the summary, key fields are extracted from the payload and displayed in a readable format. The fields shown depend on the event type. For example, a build processing event might show the build number and version string, while a subscription event might show the product ID and expiration date.

These key fields give you a quick overview without needing to dig into the raw JSON.

Raw payload

A collapsible section containing the full JSON payload as received from Apple. Click to expand, and use the copy button to copy the entire payload to your clipboard.

Enriched payload

A collapsible section containing the enriched data that Yeethook fetched from the App Store Connect API using your p8 key. This includes additional context like crash logs, tester details, device info, screenshots, and transaction history, depending on the event type.

If the enriched payload is missing and the event type supports enrichment, a Retry enrichment button appears. This is useful if:

• The original enrichment call to Apple's API timed out or failed
• You connected your p8 key after the event was received
• You re-uploaded your p8 key after a previous one expired

Clicking "Retry enrichment" calls the App Store Connect API again and updates the stored enriched payload. The detail panel refreshes automatically when enrichment succeeds.

Not all event types support enrichment. Events like TEST, REFUND_DECLINED, and REFUND_REVERSED don't have additional data to fetch from Apple.

Screenshot card

For BETA_FEEDBACK_SCREENSHOT_SUBMISSION_CREATED events, a screenshot card appears showing the image the TestFlight tester attached. This is pulled from the enriched payload, so it requires a p8 key.

Deliveries

The bottom of the panel lists every delivery attempt for this event, one per Slack channel (target). Each delivery shows:

If an event was routed to multiple Slack channels, you'll see a separate delivery entry for each one. This makes it easy to spot which channels received the event and which didn't.