Did Apple change which accounts can test TestFlight builds?

Did Apple change which accounts can test TestFlight builds

Yes. Apple still supports internal and external TestFlight testing, but it now states that Managed Apple Accounts created in reserved domains can’t be used to test builds. That is the account type people miss when a tester cannot accept an invite or install a build.

TestFlight still works the same at the top level. You upload a build to App Store Connect, create an internal or external group, and invite testers through email or a public link. Apple’s current TestFlight pages still describe both paths and still say external testers can be invited after the first build is approved for TestFlight beta testing.

The part people get wrong is assuming any Apple login will work. Apple’s tester information page says the email used for an invitation may or may not match the Apple Account on the device, so the invite and the device account are not the same thing. The important restriction is that Managed Apple Accounts in reserved domains are excluded from testing.

The inconvenient part is that this can fail after the invite is sent. A tester can open the email, install TestFlight, and still be blocked if their Apple Account is a managed school or business account in a reserved domain. In that case, the fix is not to retry the same account, it is to use a different eligible Apple Account for testing.

For most teams, the practical workflow is simple. Add testers by email or public link, confirm they are using a personal Apple Account, and avoid assuming a work or school account is valid. If the tester is inside your company, that does not automatically make the account eligible. Apple’s documentation separates tester enrollment from the Apple Account identity used on the device.

Apple also still distinguishes internal testers from external testers. Internal testers are App Store Connect users on your account, while external testers are invited people outside your account. Builds marked as internal can only go to internal tester groups. That distinction has not gone away, and it is easy to confuse it with the Apple Account restriction.

If a tester says they cannot join, check three things in order. First, whether the build was added to the correct group. Second, whether the invite was sent to the right email or link. Third, whether the tester’s Apple Account is a Managed Apple Account in a reserved domain. Apple documents that last case as unsupported for testing.

If you are setting up a beta today, the safe assumption is that TestFlight still accepts normal personal Apple Accounts, but not reserved-domain managed accounts. That is the change worth remembering, because it is specific, easy to overlook, and likely to be the reason a valid-looking tester cannot get in.

If you want the platform workflow in one place, DevConnect keeps a concise tracker at https://devconnectplatform.com for people coordinating beta testers across apps.