External Testing
External testing distributes builds to non-team real users (up to 10,000), but the first external submission of a version must pass Beta App Review.
When to Use External Testing
- Invite seed users / customers to try a new product early.
- Feature validation with specific audiences (enterprise clients, industry users).
- Real-environment smoke tests before release (covering more devices and OS versions).
- Combined with internal testing to form the “small internal → large external → submit” rhythm.
External vs Internal
| Aspect | External | Internal |
|---|---|---|
| Tester scope | Any Apple ID user | Team members only |
| Limit | 10,000 testers | 100 members |
| Beta App Review | Yes | No |
| Invitation | Email / public link | Team member addition |
| Typical use | Seed users, external validation | Daily in-team validation |
First External Test: Beta App Review
Before external testing, the first external build of a version must go through Beta App Review:
- In TestFlight → External Testing, click +, select a build, and submit for external testing.
- Fill in What to Test: tell reviewers what this build is for and what to watch.
- Confirm Export Compliance: for standard encryption, usually choose “yes, exempt”.
- Submit and wait; testers receive invites once approved.
Beta App Review and full review are separate processes, but their standards are similar. An external rejection usually means the full review would also have issues — surfacing them early is a good thing.
Create an External Group & Invite Testers
-
Go to TestFlight → External Testing → + to create a group.
-
Attach a build that has passed external review.
-
Add testers:
- Email invite: add emails one by one or bulk import via CSV.
- Public Link: enable to generate a link; anyone can join through it (limit 10,000; can be disabled anytime).
-
Testers install the TestFlight app on their phone, tap the email invite link (or public link) to accept, and install the build.
The public link is especially good for seed-user recruitment: share it in a community or mailing list and users join on their own, without you managing emails one by one.
Updating External Builds
- Under the same version, uploading a new build lets you “replace” the build in the group; new builds usually pass Beta App Review automatically (if similar to an approved build).
- Significant changes (metadata, new IAP) may trigger re-review.
- All builds remain subject to the 90-day validity.
Compliance & Risks
- Don’t use public links to distribute guideline-violating content: external testing is also bound by App Store review rules.
- External users see a near-production experience — make sure it’s stable and free of serious defects.
- If the app needs accounts, prepare clear test instructions or a demo account for external users.
Self-Check List
- Build processed and submitted for external testing
- What to Test filled in
- Export Compliance confirmed
- External review passed (or pending)
- Group attached to the correct build
- Tester emails / public link ready
- Installation and feedback instructions communicated
FAQ
- How long does external review take? Usually faster than full review (hours to ~1 day), longer in peaks.
- Tester didn’t receive the email? Check the email is in the tester list and spam; public links avoid email issues.
- Can external testers test IAP? Yes, using sandbox accounts for purchase flows.
- After disabling the public link, can existing testers still test? Yes — disabling only affects new joiners; accepted testers are unaffected.