Did Apple change who can test TestFlight builds?

Did Apple change who can test TestFlight builds

Yes. Apple still separates TestFlight into two tester groups, internal testers and external testers, but the practical change is that people outside your App Store Connect team now go through the external testing flow, and that flow requires Apple’s beta review first.

Internal testers are your own App Store Connect users. Apple says internal testers are members of your team with the Admin, App Manager, Developer, or Marketing role, and you can invite up to 100 per app. If you only use internal testing, Apple says you do not need extra test information.

External testers are different. Apple defines them as people you invite who are not App Store Connect users, and Apple lets you invite up to 10,000 external testers per app. To do that, you create an external group, add a build, and send invitations by email or public link.

The part people get wrong is thinking any invited person can test any build immediately. Apple requires TestFlight App Review before a build can go to external testers. The first build of a version goes through that review, and Apple’s help pages say subsequent builds may not need a full review.

Apple’s current wording also makes the boundary clear in App Store Connect. Builds marked as internal can only be added to internal tester groups, and builds uploaded as TestFlight Internal Only from Xcode or Xcode Cloud are internal under the build number. Those builds cannot be pushed into external testing.

The inconvenient part is that TestFlight is not one shared pool of testers. Internal testing is for your team and is fast to set up. External testing is for everyone else, but it adds review, test information, and group setup. If you are trying to send a build to a contractor, a friend, or a user list, you need the external path unless that person already has App Store Connect access.

People also mix up TestFlight with App Store release rules. TestFlight is still a beta distribution tool, not production distribution, and Apple’s documentation keeps that separation explicit. External testers can receive a build through TestFlight, but that does not change who can publish, who can review, or who counts as part of your team in App Store Connect.

If you are deciding which path to use, start with one question: is the tester already in your App Store Connect team If yes, add them as an internal tester. If no, use external testing, prepare the beta app description and feedback email, and expect the first build to go through beta review before anyone outside your team can install it.

For teams that are also testing Android, DevConnect exists for the exchange side of the same problem. It is free to use, and it is set up for reciprocal testing on apps you control, not for buying testers or sending automated outreach. The practical value is the same idea Apple uses here: keep the people who can test clearly separated from the people who can merely be invited.

The short answer is that Apple did not remove TestFlight access for outsiders, but it did keep the split strict. Your own App Store Connect team can test as internal testers, everyone else goes through external testing, and external testing still needs Apple review before the first build reaches them.

FAQ

Can anyone with a link test a TestFlight build No. A public link still belongs to the external testing flow, so the build must be approved for TestFlight beta testing first, and the tester still has to fit Apple’s external tester rules.

Do internal testers need App Review No. Apple says internal testers are App Store Connect team members, and if you invite internal testers only, additional testing information is not required. That is the fastest TestFlight path.

Why is my build only showing for internal testers Apple says builds uploaded as TestFlight Internal Only are marked as internal and can only be added to internal tester groups. In practice, that means the build was created for your team, not for outside testers.

Can I use the same tester for both internal and external testing Apple’s docs separate the roles by account access, not by person’s intent. If the person has the right App Store Connect role, they can be an internal tester. If not, they belong in external testing.

Does TestFlight still let you test with the public Yes. Apple still says TestFlight can be used for your team, specific external users, or the general public, but public access still sits inside the external testing path and its review rules.