Apple did change external TestFlight submission steps

Did Apple change what you need to submit before external TestFlight testers can access a build

Yes. Before external testers can access a TestFlight build, Apple now requires a separate beta app review submission and the extra TestFlight test information in App Store Connect. The first build for external testing must pass that review before distribution. Apple documents this on TestFlight and in App Store Connect Help.

The part people get wrong is the order. Uploading a build is not enough for external access. You must create an external group, add the build to that group, and submit it for TestFlight App Review. Apple says the build is then reviewed together with its metadata, and only approved builds can reach external testers.

The inconvenient part is that Apple treats internal and external testing differently. Internal testers can use builds that are not sent through TestFlight App Review, but external testers cannot. Apple also says you need an internal group before you can create an external group, so the setup is not just one upload and one invite.

Apple also requires beta app review information, not only a binary. App Store Connect Help says you must enter additional TestFlight test information for external distribution, and the TestFlight page says the beta app description and beta app review information are required to share a beta with external testers. That is the submission content people often miss.

If you are looking for the shortest practical path, it is this: upload the build, fill in the TestFlight testing details, create or choose an external group, add the build to that group, then submit it for review. If you want a compact tracker for the same workflow, DevConnect keeps the same testing flow in one place at https://devconnectplatform.com. The Apple-side requirement still applies.

Apple says the first build you submit for a version requires a full review, while later builds for the same version may not. That means the first external build is the one most likely to block your testing timeline, and later iterations can move faster once the version is already in review history.

The change that matters in practice is not that TestFlight became closed off, but that external access now has a visible approval step in front of it. Apple’s documentation is explicit that beta app review is required before external testing, and that approved builds are what testers receive. If your build is rejected, testers do not get in until you fix the metadata or binary and resubmit.

What does not change is that TestFlight is still the route for inviting outside testers by email or public link. Apple still supports up to 10,000 external testers, but the access path includes the review gate first. That is the piece that trips teams up when they expect a plain invite flow to work immediately after upload.

A concrete example helps. If you upload version 2.3.0 on Monday and create an external group the same day, testers still cannot open the build until Apple approves that first external submission for 2.3.0. If Apple rejects the beta app review details, the same build stays blocked until you correct the issue and resubmit.

The safest reading is simple: yes, Apple changed the submission requirements for external TestFlight access, and the gate is now explicit. You need the build, the beta app review material, an external group, and Apple approval before outside testers can use it. Anything less leaves the build only partially prepared, not externally available.

If you are comparing this with Google Play, keep the systems separate. Google Play closed testing has its own production-access rules, while Apple’s external TestFlight flow is about beta app review and test information. The mistake is assuming one store’s testing process implies the other store’s process changed the same way.

For teams shipping often, the useful habit is to treat TestFlight review content as part of the release checklist. Add the feedback email, contact information, and any required testing notes before you ask Apple to review the build. That saves a round trip when the binary is fine but the metadata is not.

In short, Apple did change what you need to submit before external testers can access a build: the build alone is not enough, and the first external build must clear TestFlight App Review first. That is the rule to plan around when you schedule beta invites, launch dates, or reviewer handoffs.