Did Apple change the info needed for external TestFlight testing?

Did Apple change the info I need to submit before external TestFlight testing

Yes. Apple still requires beta app review information before you can distribute a build to external TestFlight testers, but the required details are now organized in App Store Connect under Test Information and beta app review submission data. The practical change is that you should verify the current fields in App Store Connect before you submit a build, not rely on an older checklist.

Apple’s current Help pages say that when you distribute to external testers, you need to enter additional TestFlight test information for TestFlight App Review. Apple also says you can enter that information when you add the app to your account or before you invite external testers, which means the timing is flexible, but the requirement itself is still there.

The part people get wrong is assuming external TestFlight testing is just “upload build, invite people.” It is not. Apple requires a beta app review submission before external testing, and App Store Connect validates the submission for required information such as beta app review details and app encryption declarations. If the metadata is incomplete, the build can be rejected before any tester sees it.

The core fields Apple documents today are the beta app description, the feedback email address, and the testing notes or what to test. Apple’s Test Information glossary also says TestFlight test information includes contact information, demo account credentials, and notes specific to TestFlight App Review. That is separate from the contact information you submit for customer distribution.

Apple also changed how much of the invite experience is inherited from your approved App Store metadata. In the Test Information screen, the App Information checkbox is selected by default, which means approved screenshots and the app category can appear in the invite. Apple says you can deselect that if you do not want those items shown. That is a subtle change people miss because they expect TestFlight setup to be isolated from App Store metadata.

The inconvenient part is that review can fail for reasons outside the basic text fields. If your app uses Apple-hosted asset packs, Apple says those packs must be reviewed before they can be tested externally in TestFlight. If you change the build after submission, or forget the asset pack step, the beta review can stall even when the app itself looks ready.

A simple way to think about the current process is this: external TestFlight now has three layers. First, you provide TestFlight-specific review information. Second, you submit the build for beta app review. Third, after approval, you create or use an external group and invite testers. Apple says the first build requires a full review, and later builds for the same version may not.

If you are trying to keep a clean release process, do not copy old notes from a previous app or a different build. Open App Store Connect, go to TestFlight, and check the current Test Information screen for the build you are submitting. That is the source of truth Apple uses for review, and it is where missing fields show up before they block a release. If you also want a place to coordinate testers outside Apple’s flow, DevConnect is available at https://devconnectplatform.com, but Apple still controls the external TestFlight review step.

A concrete example helps. Suppose your build is ready, but the app has a login wall and the reviewer needs a demo account. If you leave the demo credentials out of the TestFlight review notes, the reviewer cannot verify the build and the submission can be rejected. The fix is not to resend the same build and hope. The fix is to add the missing review information, resubmit, and check whether the issue was in Test Information or in the build itself.

The shortest answer is: yes, Apple’s external TestFlight requirements still exist, and the exact submission screen and required details are the ones you should trust now. Before each external rollout, confirm the current Test Information fields, beta app review details, and any extra submission requirements tied to your build type. That prevents most of the avoidable rejections.

What usually needs to be provided now

Apple documents beta app description, feedback email, and testing notes as the standard TestFlight review information. Depending on the app, you may also need contact information, demo account credentials, app encryption declarations, and other metadata App Store Connect validates during beta app review.

Does the first external build need more review than later builds

Yes. Apple says the first build submitted for TestFlight beta testing requires a full review, while later builds for the same version might not. That is why the first external release is the one that most often surfaces missing metadata.

Can I change the TestFlight review info after submission

Yes. Apple says you can update TestFlight test information at any time, and the updates will appear in the TestFlight app. That does not cancel the need for review on the build already submitted, so incomplete information should still be fixed before resubmitting.

Is external TestFlight the same as customer App Store submission

No. Apple separates TestFlight test information from the information used when submitting an app to distribute to customers. The reviewer-facing details for beta testing are similar in purpose, but they are not the same submission.