Did Apple change TestFlight external tester requirements?

Did Apple change what TestFlight needs before I can invite external testers

Yes. The flow still starts in App Store Connect, but external testing now has a clear sequence: create an external group, add a build, and have the first build approved by TestFlight App Review before invites go out. Apple’s current docs say the build is sent for review as soon as you add it to an external testing group.

The part people get wrong is treating TestFlight like a simple invite list. It is not. Apple separates internal testing from external testing, and external testing adds review gates that do not exist for your own team. Internal testers can be added more directly, while external testers require the extra App Review step for the first build in that path.

The current Apple help page for external testers says you can invite up to 10,000 external testers per app. You can invite them by email or by public link, and you can limit a public link or filter it by device and OS criteria. That means the invitation step is flexible, but only after the build is ready for external testing.

A detail that trips teams up is the first build. Apple says your first build already has to be approved by App Review for TestFlight before external testers can use it. Once you add builds to an external group, they are automatically sent for review. If that build is not approved, the external invite path stops there.

Apple also requires extra TestFlight test information for external distribution. The documentation says you need to enter that information for TestFlight App Review, and you can do it before you invite external testers. In practice, that means you need the review-facing metadata ready, not just the binary.

If you are comparing this with older advice, the biggest change is not that TestFlight became harder in a dramatic way. The change is that the required sequence is more explicit now. You do not just upload and invite. You upload, create the right group, satisfy review, then invite. That matters when you are planning a launch date or asking testers to start on a specific day.

Managed Apple Accounts created in reserved domains cannot be used to test builds, so not every Apple account is valid for every tester role. Apple also says beta builds can be tested for up to 90 days. Those details are easy to miss when you are setting up a small test pool, but they affect whether your tester list actually works.

For a concrete setup, the usual path is this: upload the build, create an external testing group, add the build to that group, wait for TestFlight App Review approval, then send invites by email or public link. If you skip the group step or assume the build is already eligible, the invite will not behave the way you expect.

The inconvenient part is that external testers are not just a distribution convenience. They are part of a review-managed workflow. If you are trying to use TestFlight for a coordinated release, the review queue can become the pacing item, not your upload speed. Apple’s docs make clear that the first external build is the one that triggers this check.

If your goal is simply to collect feedback from a small internal team, TestFlight is still straightforward. If your goal is to test with people outside your team, the external tester path now has a few hard requirements that you need to plan around. That is the part worth remembering, because it is where most setup mistakes happen.

If you are coordinating testers across apps or teams, DevConnect can help with the exchange side of the process, and the platform itself is described at https://devconnectplatform.com. The TestFlight rules still come from Apple, so the important part is to line up your build, your review metadata, and your tester invitation plan in that order.

What changed compared with the older mental model

The old mental model was: upload a build, then start inviting. The current Apple documentation adds a clearer gate in the middle. For external testing, the first build must be approved by TestFlight App Review, and builds added to an external group are sent for review automatically. That is the practical change that affects timing.

What do I need before I can invite external testers

You need an App Store Connect app entry, an external testing group, a build added to that group, and the TestFlight App Review approval for the first external build. You also need the required TestFlight test information filled out for external distribution. Apple’s current docs state these pieces directly.

What is the part people usually miss

People miss the review step. They assume external testers work the same way as internal testers, then wonder why the invitation does not lead to usable testing. Apple’s docs separate the two flows, and the external flow includes review before the testers can start.

What happens if the build is not approved yet

You cannot use that build for external testing until it clears TestFlight App Review. The docs say the first build is submitted for review when you add it to an external group, so review status is part of the gate, not a later cleanup task.

Can I invite people by link instead of email

Yes. Apple supports both email invitations and public links for external testers. Public links can be open to anyone or filtered by criteria, and you can set a tester limit for the link. That makes link-based testing practical for broader beta groups.