TestFlight feedback: where to find it, what's in it, and where it stops

TestFlight feedback is what your beta testers send you while they use a build: a screenshot with a comment, a note from the TestFlight app, or a crash report with a few words of context. It all lands in App Store Connect, and finding it the first time takes longer than it should. If your beta isn't running yet, start with how to beta test an iOS app with TestFlight.

This guide covers where it lives, what each report contains, how testers send it, and where TestFlight stops being enough. The examples use a made-up app called Plant Diary.

The short answer

Open your app in App Store Connect, click the TestFlight tab, and below Feedback in the sidebar click Screenshots or Crashes. Each report holds the tester's comment, their screenshot or crash report, and details about their device. Testers send it by taking a screenshot inside your beta app, or with Send Beta Feedback in the TestFlight app.

Where to find it in App Store Connect

1. In Apps, open your app and click the TestFlight tab.
2. In the sidebar, below Feedback, click Screenshots for screenshot feedback or Crashes for crash reports.
3. Click Add Filter to narrow the list by platform, app version, build group, build, OS version or device.
4. Click a report to see the full screenshot, the comment and the details. The download icon at the top right saves it as a .zip file, and Open in Xcode shows it in Xcode.

Plant Diary Distribution TestFlight Xcode Cloud

Builds

iOS

Feedback

Crashes

Screenshots

Testers

All (24)

ScreenshotsAdd Filter

Can it remind me every 3 days instead of 7? My cactus doesn't need that much water.

Tester

Anna

Email

anna@example.com

Group

Friends and Family

App Version

1.4 (32)

App Uptime

12 minutes

Device

iPhone 16 Pro

iOS Version

26.0

Connection Type

WiFi

Battery

64%

Disk Free

38 GB

Crash reports can be downloaded for 120 days. If you want feedback to reach you without opening App Store Connect, Apple offers webhooks that call your server when a tester submits feedback, and App Store Connect API endpoints that return the screenshot and crash submissions.

What each report contains

Besides the comment and the screenshot or crash report, Apple lists what the detailed feedback view shows about every report:

• Who sent it: the tester's name and email if available, and their tester group.
• Which build: the app version and build number, and how long the app had been running.
• Which device: the model, iOS version, CPU architecture, screen resolution, and the paired Apple Watch when you test a watch app.
• In what state: battery level, free disk space, connection type, carrier and time zone.

Whether you see the tester's name and email depends on how you invited them:

"When a tester is invited by an invitation email, their email address is displayed in the detailed feedback view. If a tester is invited using a public link, they appear as anonymous unless they enter their email address when submitting feedback."

That matters for follow-ups. A tester from a public link who left no email is a dead end: you can read what they wrote, but you can't ask what they meant.

How testers send feedback

From a screenshot

1. Take a screenshot while using the beta.
2. Tap the thumbnail in the lower left corner, mark it up if it helps, and tap Done.
3. Tap Share Beta Feedback, add a comment, and tap Submit.

Comments can be up to 4,000 characters, according to Apple's TestFlight guide for testers. Testers who joined through a public link can add their email address, but they don't have to.

From the TestFlight app

Open TestFlight, tap the app, tap Send Beta Feedback, choose whether to include a screenshot, write the comment and tap Submit.

After a crash

When the beta crashes, TestFlight asks the tester whether to send the crash details, and they can add a comment. You can switch screenshot and crash feedback off for a tester group in the group's Settings tab, below Tester Feedback. Testers in that group can still email you from the TestFlight app.

Most testers know none of this. Put one line in What to Test, the notes testers see for each build: "Take a screenshot anywhere in the app to send feedback." It is the cheapest way to get more of it.

Where TestFlight feedback stops

TestFlight is excellent for bugs. A screenshot with a red circle, the exact build and the device is most of a bug report. For ideas and feature requests it has four gaps:

• No votes. Three testers asking for the same thing arrive as three separate reports, and counting them is up to you.
• No conversation. Apple's help page covers viewing, filtering, downloading, deleting and disabling feedback. Replying is not on the list, so follow-ups go out by email, and only to testers whose email you have.
• Nobody sees the rest. Testers can't see each other's feedback or what you plan to build, so the same request keeps arriving.
• It ends with the beta. Apple's TestFlight overview says "You can test a build for up to 90 days." Once the app is on the App Store, your users have no TestFlight to send feedback from, and their requests end up in App Store reviews, which brings problems of its own.

Put a feedback board in the beta

The fix for all four gaps is a feature request board inside the app, in the beta and in the release. Testers post ideas, vote on each other's, and see what is planned. The votes from the beta are still there on launch day.

That is what WishKit does. You add the Swift package, configure it once and show the board from a settings row or a tab, as in the SwiftUI tutorial. The beta and the App Store build use the same project, so requests posted during the beta carry over to your first real users.

Keep both. Let TestFlight handle bugs and crashes, where its device details shine, and let the board handle ideas, where votes matter.

Frequently asked questions