TestFlight feedback: how testers send it and where you see it

How testers send TestFlight screenshot and crash feedback, where developers see it in App Store Connect, what comes with it, how to turn it off, and a triage workflow.

Storewatch blog cover: TestFlight feedback: how testers send it and where you see it

Testers send TestFlight feedback from the TestFlight app or by taking a screenshot inside your beta. Developers read it in App Store Connect: open your app, go to the TestFlight tab, and look under Feedback in the sidebar, where Screenshots and Crashes are listed separately.

This guide covers both kinds of feedback, what data comes with each, how to switch feedback off for a group, and a simple way to triage it so it doesn't pile up. Facts are from Apple's View tester feedback help article and the TestFlight overview, as of November 2026.

How testers send feedback

Apple says testers on TestFlight 2.3 or later on iOS, macOS and visionOS can send feedback from the TestFlight app or by taking a screenshot. Apple's TestFlight page adds that the screenshot can be marked up before it is sent.

Screenshot feedback

A tester takes a screenshot while using your beta. A thumbnail appears in the lower-left corner of the device, and the tester taps Share Beta Feedback, adds comments and submits. You get the screenshot and the written comment together.

Crash feedback

When your beta crashes, TestFlight shows a crash alert on the next launch. The tester taps Share, can add comments about what they were doing, and submits. Apple notes that testers automatically share crash logs with developers, so the comment is a bonus, not a requirement.

Older setups

Testers on tvOS, or on earlier versions of TestFlight and iOS, can't use the in-app flow. They send feedback by email to the Feedback Email you entered in your test information. That address is also the reply-to on invitation emails, so use one you read.

Where you see it

  1. In App Store Connect, open Apps and pick the app.
  2. Click the TestFlight tab.
  3. In the sidebar, under Feedback, click Screenshots or Crashes.
  4. Click an item to open the full screenshot or crash details and the tester's comments.

Who can see it: Apple lists the Account Holder, Admin, App Manager, Developer and Marketing roles.

The download icon at the top right of an item gives you a .zip: the screenshot and comments, or the crash report and comments. Apple says crash reports can be downloaded for 120 days. If the app became unresponsive because of the crash, the .zip won't include a crash report.

Xcode

Apple documents an Open in Xcode button in the detailed feedback view, so you can open the item in Xcode from App Store Connect. Apple's build status and metrics page mentions the same button for crash feedback. I couldn't verify a separate TestFlight section in Xcode Organizer in Apple's TestFlight help, so this page doesn't describe one.

What comes with each piece of feedback

You getNotes
Tester commentsWhatever they typed. Optional on crashes.
Screenshot or crash detailsDepends on the feedback type.
Tester, app and device informationShown in the detailed view.
Tester emailShown when the tester was invited by email.

Testers who joined through a public link appear as anonymous. If they type an email when they submit, it shows only on that one item.

You can filter the list by platform, app version, build group, build, OS version and device. The build filter is the one to use first, since feedback on an old build is often already fixed.

Turning feedback off or on

Feedback is controlled per tester group:

  1. Open the app's TestFlight tab.
  2. Under Testers & Groups, pick a group.
  3. Open the group's settings, find Tester Feedback, and click Disable (or Enable to bring it back).

Apple says disabling stops in-app screenshot feedback and crash feedback for that group, but testers can still send email feedback from the TestFlight app. A tester in several groups, where one has feedback disabled, can only send it by email.

To remove one report, open it and click Delete. Delete Tester & Feedback also removes the tester from TestFlight, and you can invite them again later.

A workflow for triaging feedback

Apple documents the inbox, not a process. This is the one I'd use, built on the filters above.

  1. Crashes first, newest build only. Filter Crashes by the current build. Open the worst ones in Xcode and read the stack.
  2. Group duplicates. Several testers on the same device or OS version usually means one bug. Keep one item as the reference and note the others in your tracker.
  3. Read screenshots for layout bugs. Filter by device. Truncated text and overlaps often show only on one screen size.
  4. Move each item to your tracker with the build number, device and OS, then delete or leave the original. Apple doesn't document a status field for feedback, so App Store Connect can't mark one "done".
  5. Close the loop. Say in the next build's What to Test note what you fixed, so testers know to look.

If you'd rather not check by hand, Apple says webhooks can notify your server when new feedback arrives, and the App Store Connect API has endpoints for crash and screenshot feedback submissions (see our guide to API keys).

Tip: Ask for one thing in the "What to Test" text, like "try checkout on a slow connection". Feedback to a specific question is much easier to act on than open-ended comments.

After the beta

TestFlight feedback only covers your testers. Once the build is live, crash rate by version and Apple's launch, hang and memory numbers matter more. Storewatch shows your release pipeline (Build uploaded, TestFlight, In review, Approved, Live) and compares your newest version's crash rate with the one before, from Apple's own reports. It doesn't read TestFlight feedback itself, so keep using App Store Connect for that.

Frequently asked questions

Where do I find TestFlight feedback in App Store Connect?

Open your app, click the TestFlight tab, and use the Feedback section in the sidebar. Screenshots and Crashes are listed separately.

How do testers send screenshot feedback?

They take a screenshot in your beta, tap the thumbnail that appears, then tap Share Beta Feedback, add comments and submit. This needs TestFlight 2.3 or later on iOS, macOS or visionOS.

Can testers send feedback without a crash?

Yes. Apple says testers can send feedback from the TestFlight app as well as by screenshot, and you can read it in the same Feedback section.

Why don't I see a tester's email?

The email shows for testers you invited by email. Testers who joined through a public link appear as anonymous, unless they typed an email into that piece of feedback.

How do I turn TestFlight feedback off?

Open the tester group's settings and click Disable under Tester Feedback. In-app screenshot and crash feedback stops for that group, though testers can still email feedback from the TestFlight app.

How long can I download crash reports?

Apple says crash reports can be downloaded for 120 days. Download the ones you need to keep.