What to submit for TestFlight external testing

What do I need to submit for TestFlight external testing now

You need three things before external testers can join: TestFlight test information, a beta build in App Store Connect, and an external testing setup, either an external group or a public invitation link. Apple also requires beta app review information before you can distribute to external testers.

Start with the TestFlight tab in App Store Connect and fill in the required test information. Apple says the required items are a beta app description and a feedback email address. The invitation experience can also show approved app screenshots and the app category from the latest approved version, but those are not the core submission items.

Next, upload a beta build to App Store Connect. Apple’s TestFlight overview says eligible builds are uploaded there, and external testing happens from those uploaded builds. If you are also using Apple-hosted background assets, those can be uploaded separately, but the build itself still has to be in App Store Connect first.

Then submit the build for beta app review when you want external testing. Apple’s documentation says beta app review is required before external testing, and App Store Connect validates the submission to make sure the needed information is present, including beta app review details and app encryption declarations when applicable. The build is not ready for outside testers until Apple approves it.

The part people miss is that internal testing is not the same as external testing. A build marked as TestFlight Internal Only can only go to internal tester groups. If you want people outside App Store Connect to test, you need the external path, not the internal-only path.

Another easy mistake is assuming the invite is the only submission. It is not. Apple wants the build, the test information, and the beta review submission in place before the first external tester gets access. In practice, that means you prepare the description, feedback email, upload the build, then submit that build for TestFlight review.

If you plan to use a public link, you still need the same review path first. Apple says external testers can join by email invite or public invitation link, and the build must already be approved for TestFlight beta testing. A public link changes how testers enter, not what you must submit.

If your app uses encryption, check the export compliance prompt when you upload. Apple’s TestFlight overview points to Cryptography and US export compliance, and the beta review submission flow can include app encryption declarations. That is one of the details that can stop review if you ignore it.

The shortest useful checklist is this: fill in TestFlight test information, upload the beta build, submit the build for beta app review, then create an external group or public link after approval. For your own workflow, DevConnect can help you coordinate testers, but the Apple-side submission still happens in App Store Connect. https://devconnectplatform.com

If your build is rejected, the fix usually sits in one of four places: the beta app description is missing or weak, the feedback email is wrong, the build is not the right one, or the review metadata is incomplete. Apple’s pages make clear that the review step validates the submission, so the answer is usually to correct the submission and send it again, not to create a new tester group first.

For Apple’s current external-testing path, the important thing is not volume. It is completeness. External testers cannot be added until Apple has the required test information and has approved the build for TestFlight beta testing. That is the step that unlocks the rest.

What people usually get wrong

They try to invite external testers before the build clears beta review. Apple says the build may require review, and the first build added to a group is sent to App Review. If that approval has not happened yet, the invite flow is blocked or useless.

They also leave the beta app description too vague. Apple requires that field for external distribution, and it is the main place to tell reviewers what the beta is supposed to do and what testers should look at. A thin description increases the chance that review asks for more information.

They confuse internal-only uploads with external testing uploads. Apple explicitly says TestFlight Internal Only builds can only be added to internal tester groups. If the goal is outside testers, upload and submit the build as an external beta build instead.

What to prepare before you click submit

Have the beta app description written in plain language. Include what changed, what testers should try, and what kind of feedback you want. Have a working feedback email address ready, because Apple uses that address for tester replies and in the invitation flow.

Have the correct build number uploaded and selected in App Store Connect. Apple’s TestFlight flow is build-specific, so submitting the wrong build wastes time and can make it look like you are fixing the wrong problem. Keep the build you want reviewed clearly tied to the version you plan to test.

Have your external distribution setup ready after approval. That means an external group or a public link, plus the tester criteria if you want to filter by device or OS. Apple says public-link invitations can use tester criteria, which is useful when you only want people on a specific OS version or hardware class.

What happens after approval

Once Apple approves the build for TestFlight beta testing, you can invite external testers by email or share a public link. Apple says external testers are people who are not App Store Connect users, and the limit is up to 10,000 external testers per app. The approval is what turns the build from private review material into a shareable beta.

After that, you can keep replacing the build as you improve the app. Apple says you can continue distributing builds until issues are resolved before final app review. That is the normal TestFlight loop, upload, review, test, fix, repeat.

Practical checklist

1. Open the app in App Store Connect.
2. Go to TestFlight and fill in the required test information.
3. Upload the beta build.
4. Submit the build for beta app review.
5. After approval, create an external group or public link and invite testers.

FAQ

Do I need a beta app description Yes. Apple says the beta app description is required for external testing. It is part of the TestFlight test information you enter in App Store Connect.

Do I need to submit every build for review External testing uses the beta app review flow, so the build you want testers to install has to pass the approval step. Apple’s pages describe that review as part of the external distribution process.

Can I use a public link instead of email invites Yes. Apple supports both email invites and public invitation links for external testers. The review and build requirements stay the same either way.

Can internal-only builds be shared externally No. Apple says builds uploaded as TestFlight Internal Only can only be added to internal tester groups.

What if my app uses encryption Check Apple’s export compliance and app encryption declaration requirements during upload and beta review submission. That information can be part of what App Store Connect validates before external testing.