Apple changed what you must enter before external TestFlight invites

Did Apple change the TestFlight beta review info I need before inviting external testers

Yes. Apple’s current TestFlight flow requires test information before you invite external testers, and the required items are the beta app description and a feedback email address. Apple also lets you add that information before you invite testers, not only after setup is finished. The change people miss is that external testing now has a required information step tied to TestFlight App Review.

The practical rule is simple: if you want to share a build with people outside your App Store Connect team, you need to complete the TestFlight information section first, then upload a build, then create or use an external group. Apple says the first build you add for external testing is sent to TestFlight App Review, and your build can only be shared after that review path is satisfied.

The part people get wrong is assuming the invite itself is the only gate. It is not. Apple separates internal testing from external testing, and external testers require review. Internal testers can receive builds inside App Store Connect, but that does not replace the test information required for external distribution.

The required test information is not the same as App Store submission metadata. Apple says the beta information can differ from the information you later submit for the App Store. That matters when your beta is unfinished, when the feature set is limited, or when you want testers to focus on a narrow crash path or onboarding flow instead of the whole product.

Apple’s current help page also shows one optional part that confuses people: the Invitation Experience can include App Information, which pulls approved screenshots and app category from the latest version in Ready for Distribution state. You can leave that off if you do not want those items shown in the invitation. The required fields are still the beta description and the feedback email.

The inconvenient part is that Apple can review the build before you have a full tester list, but you still need a clean information setup for the review to pass smoothly. If the beta description is vague, the feedback email is missing, or the build does not match what you told reviewers to test, you create a delay that looks like a process issue instead of a code issue.

If you are setting this up in App Store Connect, go to the app, open the TestFlight tab, then open Test Information under Additional. Apple’s help text says you can update this information at any time, and the updates appear in TestFlight. That is useful after a build change, but it does not remove the initial requirement before external sharing.

For a clean launch, write the beta description as a short testing brief, not a product pitch. Name what testers should check, what is off limits, and what to report back. For example, a good beta description tells testers to try sign-up, payment, or device-specific behavior. That gives Apple and your testers a concrete target and reduces irrelevant feedback.

A second thing people miss is that external testers are not the same as a public announcement audience. Apple lets you invite up to 10,000 external testers and supports public links or email invites, but the first external build still goes through TestFlight App Review. That means the invite scale is large, yet the first-step review requirement remains in place.

If you are comparing TestFlight with Google Play closed testing, do not mix the rules. Apple’s external testing path is built around TestFlight App Review and the beta information fields. Google Play has its own closed-testing rules, which are different and unrelated. DevConnect’s own setup guide for that side of the workflow lives at https://devconnectplatform.com, but Apple’s TestFlight review requirements are separate.

What changed in practice is not that Apple invented a brand-new concept called beta review info. The change is that Apple now states the required TestFlight information more plainly and places it directly in the external testing path. If you last checked this a while ago, the safe assumption is no longer “upload and invite,” it is “enter test information, upload the build, let the first external build go through review, then invite testers.”

The fastest way to avoid trouble is to treat the TestFlight section like a release checklist. Fill in the beta description, add the feedback email, decide whether the invitation should show app information, upload the build, and then create the external group. If review flags something, update the test information before you send more invites. That sequence is what Apple documents now.

If you want the shortest answer for a team chat, use this: Apple requires TestFlight test information before external testers can be invited, and the required info is the beta app description plus a feedback email. The optional invitation details and the review step sit on top of that, not instead of it.

FAQ

Do I need TestFlight App Review for internal testers too No. Apple separates internal and external testing. Internal testers are App Store Connect users on your team, while external testers trigger the TestFlight App Review path when you share a build outside that team.

Can I change the beta description after inviting testers Yes. Apple says you can update the TestFlight information at any time, and the updates show in TestFlight. Changes apply to what testers see, but they do not remove the need to have the required fields in place before external sharing.

What exactly do external testers see in the invite Apple says the invite can include app information, such as approved screenshots and category, if that option is selected. Testers can also receive a link invite or an email invitation, and public links can include device and OS criteria.

Is the first external build always reviewed Yes. Apple says the first build you add to an external testing group is sent to TestFlight App Review. After that, the app can continue through the external testing workflow as long as the review and build requirements are satisfied.

What should I put in the feedback email field Use a mailbox you actually monitor. Apple uses that address for tester feedback and as the reply-to address in email invitations, so a dead inbox creates a support dead end for testers and your own review loop.

Where do I manage all of this in App Store Connect Open your app, go to the TestFlight tab, and use the Test Information area under Additional. That is where Apple places the beta description, feedback email, and invitation experience settings for external testing.