Did Apple Change TestFlight Invite Requirements?

Did Apple change what info I need before inviting TestFlight testers

Yes. Before you invite external TestFlight testers, Apple requires test information for TestFlight App Review, and the core items are still the beta app description, the feedback email address, and any review details Apple asks for. Apple also says you can add the information before you invite testers.

The part people get wrong is mixing up internal testing with external testing. Internal testers can be added through App Store Connect once your build is uploaded, but external testers need an external group, test information, and Apple’s approval for the first build of a version before that build can go out.

Apple’s current help page says the TestFlight tab is where you add test information that tells people what to test and what else they should know. It also says the feedback email is required so testers can contact you through TestFlight, and that the beta app description is required when you share with external testers.

The inconvenient part is that external testing is not just a link or an email list. You need a build uploaded to App Store Connect, an external group created, and the first build of the version submitted for TestFlight App Review. Apple says the review is required for the first build of a version, while later builds may not need a full review.

Apple also lets you control how much of your app identity shows up in the invite. The Invitation Experience can include approved screenshots and app category from the latest approved version, and you can turn that off if you do not want those items shown. That is useful when the beta is not ready to be judged by store-style marketing assets.

For external testers, Apple says you can invite people by email or by public link, and public links can use tester criteria such as device and OS requirements. That is useful when you want a specific kind of tester, such as someone on a certain device or operating system version, instead of sending blind invites.

If you are coming from the App Store release flow, the important difference is that TestFlight review information is its own set of fields. Apple says the beta app information can differ from the information you later submit for App Store review, so you should not copy production wording and assume it covers beta review needs.

A practical way to handle this is to fill in the TestFlight tab before you upload a build for external testing. Put in the beta description, choose whether to show approved app screenshots and category, add the feedback email, upload the build, then create the external group and invite testers after the build is approved. That sequence matches Apple’s workflow.

One useful check is to separate what Apple needs for review from what testers need to succeed. Apple’s review side needs the required TestFlight information, while testers need a clear note about what to test and where to send feedback. If you want a simple place to keep those tasks organized, you can track the beta process alongside your own workflow at https://devconnectplatform.com.

If a build is not approved, the usual cause is missing or incomplete review information, not the invite step itself. Apple states that TestFlight App Review is the review process for apps distributed to external testers, and that a submission is required before external testing. In practice, that means the invite can be ready, but the build still cannot reach external testers until review clears.

So the short answer is yes, Apple still wants specific info before external invites go out, and the main required pieces are stable: beta app description, feedback email, and TestFlight review details. What changed in practice is not the existence of the fields, but the way Apple structures the flow around external groups and review approval.

FAQ

Do internal testers need the same information

No. Apple treats internal and external testing differently. Internal testers are App Store Connect users, while external testers are people outside your App Store Connect account, and the extra TestFlight review information is tied to external distribution.

Do I need Apple approval for every build

No. Apple says the first build of a version goes through TestFlight App Review, and subsequent builds may not need a full review. That is why teams often keep the same beta version open while they ship multiple test builds.

Can I invite testers before the build is approved

You can set up the group and the invite flow, but external testers cannot actually test the build until Apple approves it for TestFlight. Apple’s help pages make the approval step part of making a build available for external testing.

What information can testers see in TestFlight

Apple says tester data can include name, email, invitation method, status, app version, device, OS, sessions, crashes, and feedback, depending on how the tester was invited. Public-link testers can appear as anonymous, which matters if you are expecting to match feedback to a person.

Can I skip showing screenshots or the app category in the invite

Yes. Apple says the App Information checkbox is selected by default, but you can deselect it if you do not want approved screenshots and app category to appear in the invitation experience.

Sources - Apple Developer, TestFlight: https://developer.apple.com/testflight/ - Apple Developer Help, Invite external testers: https://developer.apple.com/help/app-store-connect/test-a-beta-version/invite-external-testers - Apple Developer Help, Provide test information: https://developer.apple.com/help/app-store-connect/test-a-beta-version/provide-test-information - Apple Developer Help, TestFlight overview: https://developer.apple.com/help/app-store-connect/test-a-beta-version/testflight-overview/ - Apple Developer Help, TestFlight App Review: https://developer.apple.com/help/glossary/testflight-app-review/ - Apple Developer Help, TestFlight tester information: https://developer.apple.com/help/app-store-connect/reference/testflight/testflight-tester-information