Reporting from Apple TV apps
Apple TV apps are among the hardest to debug from the field: a tester sees a glitch in the living room and has to describe it from memory, or film the screen with a phone. On a TV there is no keyboard and no screenshot key, so Everframe does not put a reporter on the TV. The iOS SDK reports crashes and errors from the Apple TV app on its own, with the trail of what happened before, and a linked Apple TV files a quick capture when you hold Play/Pause. Quick capture on real devices covers linking, team devices and the gestures.
Linked Apple TVs
An Apple TV is linked to one teammate, whose captures are private drafts, or to the project as a team device, whose captures land in the shared inbox. It can pass from one person to the next in seconds, and each capture is attributed to whoever held it. Admins can change the gesture in the app’s Quick capture card, or record it from a real Siri Remote.
The same envelope as every other screen
The same Swift SDK that powers your iPhone app targets tvOS. A tvOS report is the same envelope as one from your phone or web app, so webhooks, triage rules and the dashboard treat it the same way — the stack, the trail of screens and the device.
Release health for tvOS
The Swift SDK records foreground sessions for each shipped Apple TV app version. Release health shows tvOS separately, with a platform filter and crash-free session rates. Native crashes count when they are tied to the session; inferred memory kills and unexplained exits remain unknown outcomes. Debug builds are excluded by default, and disabling the reporter keeps crash-only health collection active.
Without an SDK
Xcode’s Crashes organizer, a paired Apple TV in Xcode and TestFlight feedback each cover part of the picture. tvOS crash logs walks through what each one gives you on Apple TV, and which failures none of them record.