Do I need to submit my app to Apple before TestFlight outside testers?

Do I need to submit my app to Apple before using TestFlight with outside testers

Yes. If you want outside testers, Apple requires the build to go through TestFlight App Review first. Internal testers in your App Store Connect team can test before that, but external testers cannot join until Apple approves the first build for that version.

Apple’s own TestFlight help says external testers are people who are not App Store Connect users, and that after you submit your build to TestFlight App Review, Apple reviews the build and its accompanying metadata. The first build of a version is the one that needs this approval step before outside testing begins.

The part people get wrong is the difference between uploading a build and submitting it for external testing. Uploading a beta build to App Store Connect is not the same as opening it to outside testers. A build can sit in App Store Connect and still be unavailable to anyone outside your team until you send it through the TestFlight review flow.

The inconvenient part is that your review package is not just the binary. Apple says you need TestFlight test information, and the build is reviewed together with its metadata. That means your description, test notes, contact details, and any required compliance information need to be ready before you expect outside testers to see the invite.

Once the first build of a version is approved, you can invite external testers by email or public link. Apple also says subsequent builds may not need a full review, but the initial approval is the gate that matters for outside access. If the first build is rejected, you need to fix the issue and submit a new build before inviting external testers.

For a practical flow, many teams do this in three steps: upload the build, add it to an external tester group, then wait for TestFlight App Review to complete. Only after approval do they send invites. If you try to skip the review step, the testers do not get a usable invite because the build is not approved for external distribution yet.

Internal testing is a separate path. Apple allows internal testers from your App Store Connect team to test without the same external beta review gate, so teams often use internal testers to catch obvious crashes and setup problems before asking Apple to review the build for outside testers. That saves a rejected external review from wasting your tester pool.

If your goal is to get feedback from people outside your team, the minimum path is clear: upload the build, complete the TestFlight beta review request, and wait for approval before you invite outside testers. If you need a place to organize human testers around that workflow, DevConnect is a separate tool for finding people who will test on their own devices and on their own time, and it is free to use.

Apple also limits how long a TestFlight build stays available, so waiting on review is not just a formality. Your planning should assume there is a review step, approval step, and testing window. If you launch invites before the build is approved, you are not speeding anything up, you are just creating a dead end for testers.

If you want the short version: yes, submit the build to Apple first for outside testers, no for your internal team, and do not confuse upload with approval. That distinction is the whole process.

FAQ

Can internal testers use TestFlight before Apple approves external testing

Yes. Internal testers from your App Store Connect team can test earlier. Apple’s external review requirement applies to outside testers, not to your own internal group.

Do all TestFlight builds need a full review

No. Apple says the review is required for the first build of a version, and later builds may not need a full review. The first approval is the part that unlocks external testing.

What happens if Apple rejects the TestFlight build

You cannot invite outside testers with that rejected build. You need to fix the issue, upload a new build, and send it back through TestFlight App Review before external testing can begin.

Can I use a public link before the build is approved

No. Public links still depend on the build being approved for external testing first. The link is a distribution method, not a way around review.

Is TestFlight the same as submitting to the App Store

No. TestFlight review is a beta review step for testing, while App Store submission is the production review path for release. They are related, but they are not the same process.