Yes, Apple changed TestFlight external testing info

Did Apple change what TestFlight information I have to submit for external testing

Yes. When you distribute a build to external testers, Apple requires additional TestFlight test information for beta app review, and that information is separate from the App Store submission flow. Apple says you can enter it before you invite external testers or when you add the app to App Store Connect.

The part people get wrong is assuming TestFlight only needs the same metadata as the App Store listing. Apple says the beta app information can differ from what you submit later for the App Store, so the text you write for testing does not have to match your public store copy. That matters when the beta is unfinished, has placeholder flows, or needs a narrower test focus.

Apple’s current TestFlight help page names the required items clearly. You need a beta app description, which is required, and a feedback email address, which testers use in the TestFlight app. Apple also lets you choose whether invitation experience shows app information pulled from the latest approved version, including screenshots and app category, and you can turn that off if you do not want those details shown.

For external testing, Apple also routes the first build in a group through TestFlight App Review. Apple says when you add the first build of your app to a group, it gets sent to App Review to make sure it follows the App Review Guidelines, and testing can begin once that build is approved. Later builds may not require the same full review.

The inconvenient part is that external testing is not just a distribution toggle. You need the extra beta review fields, you need the first build approved, and you need an internal group before you can create an external group. Apple also caps external testers at 10,000 per app and internal testers at 100 App Store Connect users with access to your content.

If you are trying to start testing and nothing appears to happen, check the beta app description first, then the feedback email, then whether the build has actually been approved for TestFlight. Apple says you can update the test information at any time, and the updates show in the TestFlight app, so missing fields or stale text are usually fixable without rebuilding.

A practical example: if your app is only ready for login testing, write that directly in the beta app description, list the exact screens you want feedback on, and use a monitored inbox for the feedback email. That keeps testers focused and gives you a place to receive reports without sending them to a dead address. Apple expects that feedback path to exist.

What has not changed is the basic structure. External testers are still people outside App Store Connect who get invited by email or public link, TestFlight still handles the install flow, and Apple still expects the build and its accompanying metadata to pass review before outside testers can use it. The change is in the required beta information and the way Apple treats that information as part of review.

If you are already using DevConnect to find testers for your own app, the workflow still starts the same way, with a testable build, a clear beta description, and a real feedback channel. You do not need anything more exotic than that to get through TestFlight’s external testing setup. The expensive mistake is skipping the review fields and assuming the invite alone is enough.

Apple’s documentation is explicit, so the safest reading is simple: yes, Apple requires TestFlight-specific information for external testing, and that information is not the same as your App Store metadata. If you are preparing a release, treat the beta review fields as their own checklist item, not as an optional note you can fill in later.

FAQ

What exact information does Apple require for TestFlight external testing Apple’s help page says the beta app description is required, and a feedback email is required so testers can contact you through TestFlight. Apple also offers optional invitation experience settings, including app information from the latest approved version.

Do I need App Store Review before external testers can use TestFlight Apple says the first build added to an external testing group goes to TestFlight App Review, and testing starts after approval. Subsequent builds may not need the same full review.

Can I change the TestFlight beta information after I submit it Yes. Apple says you can update the test information at any time, and the updates appear in the TestFlight app.

Is the beta app description the same as the App Store description No. Apple says the information you enter for your beta app can differ from what you submit later for the App Store.

How many external testers can I invite in TestFlight Apple says you can invite up to 10,000 external testers per app.

Do internal testers count the same way as external testers No. Apple says internal testers are App Store Connect users with access to your content, and external testing has its own group setup and review flow.