TestFlight feedback is two taps for the tester, and nobody sends you an email.

How does a tester actually send feedback?

There are two routes and they produce the same kind of item. The long way goes through the TestFlight app: open TestFlight, tap the app in the Apps list, tap Send Beta Feedback, then in the share dialog tap Include Screenshot to pick one or Don't Include Screenshot to send text alone. The tester adds comments of up to 4,000 characters, optionally enters an email address if they joined through a public link, and taps Submit. On a Mac the same flow is Send Beta Feedback plus Attach Screenshot, and screenshots can be dragged into the comment field. On Apple Vision Pro the button is Send Feedback and submitting is a pinch.

The short way is the one that makes beta testing work, and it starts with a gesture people already know. The tester takes a screenshot on the device while the beta app is open. A thumbnail appears in the lower-left corner. They tap the thumbnail, add drawings or text with Markup if the bug needs pointing at, tap Done, then tap Share Beta Feedback. Comments and an email address are optional from there. On a Mac the thumbnail is in the lower-right corner, clicking it opens Quick Look, and Send Beta Feedback sits in that window's Share menu. Two taps, no app switching, and the screenshot is already attached.

Crashes have their own prompt. Apple's instructions for testers say that if you experience a crash while testing a beta app or beta App Clip, you receive an alert asking whether to send crash details to the developer through TestFlight. On iOS the tester taps Share, adds any comments and taps Submit. On a Mac it is Report, then OK, Send or Reopen. The alert only appears if the developer has that feedback enabled, which is the same switch described further down.

Three exceptions are worth knowing before you promise a tester it will work. Testers running TestFlight 2.2.1 or earlier on iOS 12.4 or earlier send feedback to the address you put in the Feedback Email field in Test Information. On tvOS there is no in-app form at all: the tester opens the app's page in TestFlight, reads your email address under App Details in the Information section, and writes to you. And email feedback always exposes the tester's address, even for someone who joined by public link and stayed anonymous everywhere else.

App Store Connect Help, view tester feedback, read 10 October 2026

Does it reach you automatically, or only when you ask?

It arrives without you asking, and then it waits. The path is Apps, select your app, the TestFlight tab, and in the sidebar below Feedback either Screenshots or Crashes. Screenshots shows testers' images and comments. Crashes shows submission times and crash details. Add Filter narrows either list by platform, app version, build group, build, OS version or device, which is how you answer the only question that matters during a beta: is this still happening on the newest build. Reading it needs the Account Holder, Admin, App Manager, Developer or Marketing role.

Nothing pushes it to you, and two documented options fix that. Apple supports webhooks that send automatic notifications to your own web server whenever new feedback is submitted through TestFlight. The App Store Connect API also exposes crash feedback and screenshot feedback, so a nightly job can pull both into wherever your bugs live. Either one turns a page you forget to open into a message in the channel you already read. Without one of them, assume the feedback list is a place you visit, not a thing that finds you.

Each item does more than it looks like it does. Click one and you get the full screenshot and the written comments, plus information about the tester, the app and the device. Open in Xcode moves screenshot feedback into the editor. The download icon in the top right gives you a .zip holding the screenshot or crash report together with the comments, which is the version to attach to an issue. Delete removes a single item, and Delete Tester & Feedback removes the tester from TestFlight entirely, though removed testers can be invited again later.

You can also close the channel, and the switch is per group, not per app. In the TestFlight tab, under Testers & Groups, select a group, open its settings tab, and click Disable under Tester Feedback. That stops screenshots and in-app feedback for that group, including details about crashes, and all testers can still send email feedback from the TestFlight app. Apple documents the trap in its own FAQ: a tester who belongs to several groups, where any one of them has feedback disabled, can only send feedback by email. Worth checking before you decide the feature is broken, and worth deciding on while you are planning testing before launch.

App Store Connect Help, view tester feedback, read 10 October 2026

Are crash reports separate from the written feedback?

Yes, as two lists in the same place. Screenshots and Crashes are separate entries in the Feedback sidebar, and an item never shows up in both. A screenshot item is an image, any Markup the tester added and their comments. A crash item is the crash report plus whatever the tester typed into the alert after the app died. The filters and the detailed view behave the same way in both lists, and both download as a .zip with the attachment and the comments together.

Two limits on the crash side are in the documentation and surprise people anyway. Crash reports are available for download for 120 days, so anything older is a note, not an artefact. And if an app becomes unresponsive due to a crash, the crash report will not be included in the .zip file, which is exactly the case where you wanted it most. Both facts were checked on 10 October 2026.

The part that quietly saves you a conversation is what the detailed feedback view carries without anyone typing it. Apple's reference for beta tester feedback lists the tester name and email where available, the groups they belong to, App Version meaning the version and build installed, App Uptime, Device model, iOS Version, Battery level, Carrier, Time Zone, Architecture, Connection Type including the mobile network type, the paired Apple Watch model and watchOS version, Disk Free and Screen Resolution. That is most of a bug report, collected for free, from someone who would otherwise have written the word broken.

What it is not is a crash reporting service. Every item here needs a tester to act: take the screenshot, or tap Share on the crash alert. A crash nobody noticed, or one that happens after you ship, leaves no trace in this list at all. TestFlight tells you what your testers hit while they were paying attention. Production monitoring is a separate decision, and it is the one that still matters once strangers are using the app.

Does Google Play work the same way?

No, and the differences are big enough to plan around. There is no screenshot gesture and no feedback form inside the build. A tester on a closed or an open test sends private feedback through Google Play itself, and you read it in Play Console under Monitor and improve, Ratings and reviews, Testing feedback. Google states that beta feedback from users is only visible to you and cannot be seen on Google Play. You can reply to it from that page, which TestFlight gives you no way to do, and you can filter by date, language, reply state, app version and device, or search for words in the text.

Internal testing is the gap to watch. Google's own track guidance tells you to provide a feedback URL or an email address to collect feedback from testers, and only lists private feedback through Google Play for the closed and open tracks. So on the track most people start with, the one that gets a build to twelve colleagues in seconds, the feedback channel is whatever you built yourself. Set up the form before you send the invite. If you are mapping the two systems build for build, the Android equivalent covers the tracks and the invitations.

Crashes live somewhere else entirely. In Play Console they are under Monitor and improve, Android vitals, Crashes and ANRs, and the data comes from Android devices whose users have opted in to automatically share their usage and diagnostics data. Crashes are grouped into clusters so you can spot a shared root cause, and nothing about it depends on a tester writing to you. If the issue was found while generating a pre-launch report, that cluster also carries device information, the Logcat from the device and a video of the error. Richer than TestFlight on crashes, and completely disconnected from the feedback page.

There is one more reason to take Play feedback seriously. A personal Play Console account created after 13 November 2023 has to run a closed test with a minimum of 12 testers who have been opted in continuously for at least 14 days before it can apply for production access. Google says you must summarise your testing feedback when you apply, and the application form asks how the feedback was collected and what the testers did with the app. Checked on 10 October 2026. Keeping notes as the feedback arrives costs nothing. Reconstructing a fortnight of it on the form is miserable.

Play Console Help, view and analyze your app's ratings and reviews, read 10 October 2026