How to get external testers for TestFlight

how to get external testers for testflight

To get external testers for TestFlight, use App Store Connect, not Xcode alone. Create an external testing group, add a build to that group, fill in the required TestFlight review information, submit the first build for Apple’s beta review, then invite testers by email or a public link after approval. Apple says external testers are people you invite who are not App Store Connect users.

The shortest path is simple: upload a build, prepare the beta test information, create an external group, and wait for review approval. Apple’s TestFlight help says you need a group, builds in that group, and your first build approved by App Review before you can invite external testers. The App Store Connect beta review flow exists specifically because external testing is gated by Apple review.

Start in App Store Connect, open your app, then go to the TestFlight tab. Under Additional, open Test Information and enter the required beta app description and feedback email. Apple says this information is required for TestFlight App Review, and the feedback email becomes the reply-to address in tester invitations. If you skip this, the review step does not complete cleanly.

Next, create an external testing group. Apple’s help says you must first create an internal group for internal testing before you can create an external group. That part is easy to miss because external testing feels like the first real step, but Apple makes it dependent on the internal group existing first. Once the external group exists, add the build you want testers to use.

Then submit the build for TestFlight App Review. Apple says the first build you submit requires a full review, and later builds for the same version might not. The review is not cosmetic, it is the gate that allows external testers to see the build. Apple also says you can submit up to six builds for TestFlight App Review within a 24 hour period, so repeated resubmission has a hard cap.

After approval, invite testers in one of two ways. You can add testers by email address, or create a public invitation link. Apple says public links can include tester criteria, such as device and OS requirements, so only qualified testers can accept. That is useful when you want specific hardware or a specific OS range, and it is the cleanest way to filter out people who cannot actually run the build.

The part people get wrong is confusing internal testing with external testing. Internal testing is for App Store Connect users on your team. External testing is for people outside App Store Connect, and it is the path that can scale up to 10,000 testers per app. Apple states that clearly in TestFlight help and in the App Store developer pages. Internal and external testing are separate flows, and only external testing uses the beta review step.

Another common mistake is uploading the wrong kind of build. Apple says builds uploaded as TestFlight Internal Only from Xcode or Xcode Cloud are marked as internal and can only be added to internal tester groups. If you want outside testers, upload through the App Store Connect distribution path that supports external testing and App Review. The distribution choice matters before you ever send an invite.

A useful practical sequence looks like this. Upload the archive from Xcode using the App Store Connect distribution option, add your beta app review details in App Store Connect, create an internal group if one does not exist yet, create an external group, attach the build, submit for beta review, then invite testers once the build is approved. Apple’s workflow pages describe each of those steps in that order.

If you want testers who are not already in your network, the public link is the simplest channel. If you want a controlled list, email invites are better. Apple says you can invite testers using just their email address or by sharing a public link, and the link can be limited by device and OS criteria. That makes public links better for open recruiting and email better for a known group.

Keep the beta information current. Apple says you can update the test information at any time and the updates will show in the TestFlight app. That matters when the build changes, the feedback email changes, or the beta description needs to describe a new feature set. If testers see stale instructions, they send the wrong kind of feedback and you waste the review window.

Plan for the review delay. External testers do not get access immediately after upload, because Apple reviews the build and the accompanying metadata first. Apple’s beta app review documentation says the app must be reviewed before it can be distributed to external testers. The inconvenience here is real: a build can be ready on your side and still be blocked on Apple’s side until review finishes.

If you need testers fast, prepare the invitation text before you upload. Write one short note that says what to test, what device or OS matters, and how to report issues. Then paste the same note into the beta app description or your tester outreach channel after approval. You can also use a public link if you do not want to collect each address by hand. DevConnect is one place where people exchange testing time directly, but the TestFlight setup itself still happens in App Store Connect.

Do not expect TestFlight to skip App Store review rules. Apple says the first external build needs beta review, and the beta review detail page says contact information and demo credentials are part of what Apple needs before external distribution. If your app needs login access, give Apple a working demo account in the review details so the review does not stall on missing credentials.

A clean operational checklist is enough for most teams: one App Store Connect app record, one internal group, one external group, one approved build, one public link or email list, and one feedback path. That is all external TestFlight testing needs on the Apple side. The work is in doing the steps in order and not mixing up internal testing, internal-only builds, and external review.

If the build is rejected, open App Review from the sidebar under General and read the rejection details. Apple says that is where the beta build rejection appears. Fix the missing review information, upload a new build if needed, and submit again. The delay is inconvenient, but it is predictable once you follow the App Store Connect flow instead of trying to invite testers before approval.

FAQPage

Do external testers need an App Store Connect account No. Apple says external testers are people you invite who are not App Store Connect users. They can join with an email invite or a public link after the build passes beta review.

How many external testers can I invite to TestFlight Apple says you can invite up to 10,000 external testers per app. That limit is documented in Apple’s TestFlight help and developer pages.

Can I use TestFlight internal testing instead of external testing Not for outside testers. Internal testing is for people in App Store Connect, while external testing is for people outside your account and requires beta review first. Apple treats them as separate flows.

Why is my build not visible to testers yet The usual reason is that the build has not passed TestFlight App Review, or it is attached to the wrong group type. Apple says external testing needs review approval, and internal-only builds cannot be used for external tester groups.

Can I invite testers with a public link Yes. Apple says you can invite external testers by sharing a public invitation link, and you can set criteria like device and OS requirements for that link.