In TestFlight, testers report a ski-resort app's failing lift-pass scan; how do their screenshots and crash reports reach your team, and what can stop them arriving?
answer
- a screenshot inside the beta app
- Feedback: Screenshots and Crashes
- device details beside every report
- a group with feedback disabled
- crash reports kept for 120 days
basics
~20 sTesters on TestFlight 2.3 or later send feedback from the TestFlight app or a screenshot in the beta; it lands under Feedback in App Store Connect and Xcode's Feedback organizer. Disabled group feedback and old clients block it.
solid answer
~50 sTesters running **TestFlight 2.3 or later** on iOS, macOS or visionOS send feedback from the TestFlight app or by **taking a screenshot inside the beta**; crash logs are shared with you automatically. In App Store Connect it appears under **Feedback** as **Screenshots** and **Crashes**, filterable by build, group, OS version or device, each with details such as device model, OS version, battery, connection type and app uptime, and downloadable as a .zip. **Open in Xcode** shows it in the Feedback organizer, where you can reply, share and mark items resolved, and webhooks can notify a server. Things that stop it: a group with **Tester Feedback disabled** (a tester in several groups is limited to email if any one has it off), testers on tvOS or older clients who can only email the **Feedback Email**, crash reports that are kept for **120 days**, and public-link testers who stay anonymous unless they add an email.
go deeper
Know that testers send feedback from the TestFlight app or a screenshot in the beta, and that it shows up in App Store Connect.
Explain the Screenshots and Crashes lists, the filters, the device details in a report, and Open in Xcode.
Diagnose missing feedback: a group with feedback disabled, tvOS or old clients on email, hangs without crash reports, the 120-day retention and anonymous testers.
Decide how beta feedback flows into the team's tracker, through webhooks or the API, and who triages it before reports age out.
## The scenario Season-pass holders testing a ski-resort app find that the lift-pass scan fails at the gate. Some of them take a screenshot of the error, one tester's app crashes, and the team needs all of it in one place, matched to the build and the device. TestFlight carries that feedback without any extra SDK in the app, but only under conditions worth knowing. ## How testers send it - Testers using **TestFlight 2.3 or later** on iOS, macOS and visionOS can submit feedback **through the TestFlight app** or **by taking a screenshot directly within your beta app**, adding comments. - **Crash logs** are shared with developers automatically, and a tester can add comments to a crash. - Testers on **tvOS**, or on earlier clients (TestFlight 2.2.1 or earlier on iOS 12.4 or earlier), send feedback to the **Feedback Email** you set in Test Information. - Testers on iOS 14 or iPadOS 14 or later can also send feedback on an **App Clip** experience. ## Where it lands In App Store Connect, open the app's **TestFlight** tab and look under **Feedback**: 1. **Screenshots** lists testers' screenshots and comments. 2. **Crashes** lists submission times and crash details, with the testers' comments. 3. **Add Filter** narrows either list by platform, app version, build group, build, OS version or device. 4. The download icon saves a **.zip**: the screenshot and comments, or the crash report and comments. The **detailed feedback view** carries context a bug report usually lacks: | Field | What it tells you | |---|---| | App Version | the version and build installed | | Device, iOS Version, Architecture | the hardware and OS | | App Uptime | how long the app had been running | | Battery, Disk Free | power and storage at send time | | Connection Type, Carrier | Wi-Fi, cellular or offline, and the network | | Time Zone, Screen Resolution | locale and display | **Open in Xcode** takes a report to Xcode's **Feedback organizer**, where you can email the tester, share a link with a teammate, rename and annotate reports, and **Mark as Resolved**. **Webhooks** can notify your own web server whenever new feedback is submitted. The build list also shows per-build **Sessions** (last seven days), **Crashes** and **Feedback** counts. ## What can stop it arriving, or lose it 1. **Feedback disabled for a group.** In a group's settings, *Tester Feedback* can be disabled, which stops screenshots and crash comments from the beta. A tester in several groups is limited to email from the TestFlight app if **any** of their groups has it disabled. 2. **Old or tvOS clients.** Their feedback never reaches the Feedback section or the organizer; it goes to the Feedback Email. 3. **An app that became unresponsive.** If the app becomes unresponsive due to a crash, the help page says the crash report is not included in the .zip. 4. **Retention.** Crash reports can be downloaded for **120 days**; download what you need before then. 5. **Anonymity.** Public-link testers appear as anonymous unless they type an email when submitting, and then only on that piece of feedback, so you may have no way to follow up. 6. **Deleting a tester with their feedback.** *Delete Tester & Feedback* removes the tester from TestFlight as well as the report. Tester metrics such as sessions and crashes appear only for testers who installed the app, and can take up to 24 hours to show. ## Making crashes readable A crash report is only as useful as its symbols: uploading symbols with the build lets Apple add symbol names before the reports reach Xcode's Crashes organizer. How a release pipeline keeps and uploads them, and which crash signals should gate a rollout, belong to the system design material on crash reporting. TestFlight's job is collecting the report and the tester's words beside it. ## What to take away - Ask testers to report from inside the beta with a screenshot; it arrives with the build and the device attached. - Check the group's feedback setting before assuming testers are silent. - Pull crash reports into Xcode or download them well inside 120 days. - Match each report to its build through the App Version field before chasing a fix that a newer build already contains.
- A tester in two groups can only send email feedback; why?One of their groups has Tester Feedback disabled. The help pages say that when a tester belongs to several groups and any one has feedback disabled, they can only send feedback by email from the TestFlight app. Re-enable it in that group's settings, or move the tester.
- Your app froze and a tester reported it, but the downloaded .zip has no crash report; why?The help page notes that if an app becomes unresponsive due to a crash, a crash report is not included in the .zip. You still get the tester's comments and device details, so reproduce it from those, and look at the build's crash counts for any reports that did arrive.
- How does the team hear about new feedback without watching App Store Connect?Configure a webhook: App Store Connect can send an automatic notification to your web server whenever new feedback is submitted through TestFlight. The App Store Connect API can also fetch screenshot and crash feedback for your own tools.
- TestFlight crash feedback needs a crash-reporting SDK in the beta build.
- Feedback from public-link testers always includes their email address.
- Disabling feedback in one group never affects a tester's other groups.
- Every crash feedback .zip is guaranteed to contain a crash report.
- tvOS testers send screenshot feedback from inside the beta app.
- TestFlight crash reports stay downloadable for as long as the app exists.