You added external testers in App Store Connect → TestFlight, the UI confirmed “Tester added,” and a day later they all say the same thing: “I never got the invitation email.” Your tester list shows them sitting at status Invited. You ask them to check spam — nothing. The public TestFlight link you also generated shows them “This beta isn’t accepting any new testers right now” even though your group is nowhere near the 10,000 cap. You start to wonder whether external testing actually works.
It works, but external invites have more wiring than you’d expect. The single most common cause, by a wide margin: your first build for that version has not yet passed Beta App Review, so there is literally nothing for testers to redeem and no invite goes out. After that, it’s the tester’s mail provider, group → build attachment, the public-link limit, or a region mismatch. Walking these in order finds the cause without re-uploading anything.
Fastest fix: Confirm the build status reads Ready to Test (App Store Connect → TestFlight → External Testing → your group → Builds). If it says Waiting for Review or In Review, no invite will ever send — you wait for Apple. If it’s already Ready to Test, jump to the mail-delivery fix and switch the stuck testers to a public link.
Which bucket are you in?
| Symptom | Most likely cause | Section |
|---|---|---|
| ALL external testers, brand-new app/version, never got anything | First build hasn’t passed Beta App Review | Cause 1 |
| Group shows testers but the Builds tab is empty | No build attached to the group | Cause 2 |
| One or a few testers miss it; others got it fine | Mailbox filtered Apple’s sender | Cause 3 |
| Public link shows “not accepting new testers” | Tester-limit cap reached (or limit set to a low number) | Cause 4 |
| Non-team emails show under Internal Testing | Added to wrong group | Cause 5 |
| Invite arrives but redeeming fails | Apple ID region not in your availability list | Cause 6 |
| Tester swears the address is right, still nothing | Typo / stale alias | Cause 7 |
Common causes
Ordered by hit rate.
1. Build hasn’t passed Beta App Review for external use
Internal testers can use any build the moment it finishes processing. External testers cannot — your first build for each new version is sent to Beta App Review and must be approved before external invites go out. Until then, your testers are added but nothing is sent, because there’s nothing for them to test. As of June 2026, that first-build review typically turns around in 1–2 days; subsequent builds of the same version usually skip full review and go live quickly.
How to spot it: App Store Connect → TestFlight → External Testing → your group → Builds. The build must read Ready to Test. If it reads Waiting for Review, In Review, or Rejected, no invite will send. (Rejected? Open App Review in the sidebar under “General” to see why.)
2. Group has testers but no build attached
You created an external group and added testers, but never clicked Add Builds to attach one. The group has no build, so the invite system has nothing to send — even if a build is Ready to Test elsewhere in the app.
How to spot it: TestFlight → External Testing → your group → Builds tab. If it’s empty, attach a build.
3. Tester mailbox filtered or rejected noreply@email.apple.com
This is the most common reason a subset of testers misses the invite. Apple sends from noreply@email.apple.com, and that message often lands in Gmail’s Promotions tab (not the inbox) or gets dropped by corporate filters. Mailboxes on .com.cn, .gov, and university .edu domains are the worst offenders. Personal Gmail and iCloud are the most reliable.
How to spot it: Ask the tester to search their entire account (not just the Inbox folder) for noreply@email.apple.com or TestFlight, and to check the Promotions and Spam tabs specifically. If it’s nowhere, the mailbox blocked or buried it.
4. Public-link tester limit reached (or set low)
A public link has an optional limit you set between 1 and 10,000. If you checked “Set Limit” and entered a small number — or you hit the cap — new testers see “This beta isn’t accepting any new testers right now.” The same message appears if the link was disabled.
How to spot it: TestFlight → External Testing → the group with the public link → next to Public Link click Manage. Check the current tester count against the limit, and confirm the link is enabled.
5. External testers added to internal-only group
You meant to add external testers but added them to the Internal Testing group, which only accepts people who are members of your Apple Developer team (and have an App Store Connect role). The invite fails because non-team members can’t be internal testers.
How to spot it: TestFlight → Internal Testing. If you see emails there that aren’t members of your developer team, that’s the wrong group — remove them and add them under External Testing instead.
6. Tester’s Apple ID region doesn’t match the app’s available regions
Your app is available in US/CA only; the tester’s Apple Account is registered in JP. The invite (or public link) may arrive, but redemption fails because the app isn’t distributable to their region.
How to spot it: App Store Connect → your app → Pricing and Availability → check the country/region list. Ask the tester to confirm their Apple Account country at Settings → [their name] → Media & Purchases → View Account → Country/Region.
7. Email address has a typo or stale alias
You typed tester@gmail.con instead of .com, or used a tester’s old address that’s been deactivated. App Store Connect’s UI doesn’t validate deliverability — it accepts whatever you type.
How to spot it: TestFlight → External Testing → your group → Testers. Re-read each email character by character, ideally by copy-pasting it back to the tester to confirm.
Information to collect
- The build’s status (Waiting for Review / In Review / Ready to Test / Rejected).
- The builds attached to the group.
- The exact email addresses you added (copy them straight out of App Store Connect).
- Each affected tester’s mailbox domain (gmail.com, icloud.com, corporate, .edu, .gov).
- The Apple Account region of testers who report not receiving.
- Whether you’re using the email invite flow or the public TestFlight link.
Shortest path to fix
Step 1: Verify Beta App Review status
App Store Connect → TestFlight → External Testing → your group → Builds. The build’s status must be Ready to Test. If it’s Waiting for Review or In Review, you wait for Apple to approve before any invite sends — there’s no way to force it. See Beta App Review taking too long if it’s been more than a couple of days.
Step 2: Attach the build explicitly to the group
TestFlight → External Testing → your group → Builds tab → click the add (+) button next to “Builds” → select the latest processed build → Add. Fill in the “What to Test” notes, then click Start Testing (or Submit Review if it’s the first build for this version).
Without an attached build, the group has nothing to invite testers to.
Step 3: Re-send invitations once the build is Ready to Test
Once the build is Ready to Test and attached:
- TestFlight → External Testing → your group → Testers. Testers stuck at status Invited show a Resend Invite action — use it for each one.
- If a tester is in a stuck state, remove them and re-add them; Apple sends a fresh invite.
- If you added the build without checking “Automatically notify testers,” go to Builds → your platform → the version → under Status click Notify Testers. The build status moves to Testing and TestFlight notifies everyone.
Step 4: Ask testers to whitelist Apple’s sender
Have the tester:
- Check Spam, Promotions, and any corporate quarantine folder — search the whole account for
noreply@email.apple.com. - Add
noreply@email.apple.comto their contacts. - On corporate email, ask IT to allowlist Apple’s sender / IP range.
- If all else fails, re-invite them at a personal Gmail or iCloud address.
Step 5: Switch to a public TestFlight link
For email-resistant testers, a public link sidesteps delivery entirely:
App Store Connect → TestFlight → External Testing → your group → Testers tab → Create Public Link → choose Open to Anyone (or Filter by Criteria for device/OS gating) → optionally check Set Limit (1–10,000) → Confirm → copy the URL.
Share that URL over WhatsApp, Slack, your own email, or any non-Apple channel. The tester taps it → Start Testing → the TestFlight app opens → they join. No invite email required. Note: public-link testers appear in your list as Anonymous with no email, so you can’t track them per-person.
Step 6: Verify region availability
App Store Connect → your app → Pricing and Availability → confirm the tester’s Apple Account country/region is in the list. If it isn’t, either add that region to availability or have the tester use an Apple Account in a supported region. (Changing an Apple Account’s country has its own restrictions — usually not realistic, so expanding availability is the better fix.)
How to confirm it’s fixed
- The tester’s row in TestFlight → External Testing → your group moves from Invited to Accepted, then Installed.
- A re-sent invite lands within minutes (Apple’s email is near-instant when it isn’t filtered).
- Opening the public link on an Apple Account whose region matches your availability lands on the Start Testing screen rather than the “not accepting testers” message.
- Add a throwaway address of your own as a test and walk the whole path end to end — that proves the build + group wiring, leaving only per-mailbox issues.
If it still fails
- Invite your own personal Gmail or iCloud address. If that works instantly, the problem is the original tester’s mailbox, not your setup.
- Make the public link your primary distribution method; reserve per-email invites for the rare cases where you genuinely need per-tester tracking.
- Check Apple’s System Status for TestFlight delivery incidents before assuming it’s your account.
- One quirk worth ruling out: a tester who already has the App Store production version installed, or who previously declined/accepted on a different Apple Account, can get stuck. Have them delete any existing copy, then remove and re-add them and redeem on a single, clean Apple Account.
Prevention
- Submit each version’s first build for Beta App Review the moment it finishes processing — don’t wait until the day you need testers. You can submit up to 6 builds for review per 24 hours.
- Keep at least one public-link group with a generous limit as your default distribution path; email invites are higher-friction and more failure-prone.
- Record tester emails and Apple Account regions in a
TESTERS.mdso mismatches surface before you invite, not after. - For corporate testers, ask up front whether their IT filters outside senders, and hand them the public link as the alternative.
- After every new build, re-send (or Notify Testers) to anyone still at Invited — they may have lost the original.
FAQ
Do external testers need a separate Beta App Review for every build? No. Only the first build of each version gets a full Beta App Review (typically 1–2 days as of June 2026). Subsequent builds of the same version usually skip full review and become available shortly after processing.
My tester is stuck at “Invited” — what does that mean? It means Apple sent (or queued) the invite but they haven’t opened it in TestFlight yet. Either the email never reached them (Cause 3) or they haven’t acted on it. Use Resend Invite, or switch them to a public link.
Why does the public link say “not accepting new testers” when I’m under 10,000? You set a low Set Limit value, the link was disabled, or that specific link hit its own cap. Open Manage next to the public link and check the limit and enabled state — the 10,000 figure is the maximum, not your current setting.
How long should an invitation email take to arrive? When it isn’t filtered, it’s effectively instant — seconds to a couple of minutes. If a re-sent invite still hasn’t arrived after ~30 minutes at a clean Gmail/iCloud address, treat it as a delivery (mailbox) problem and move to the public link.
Can I see who joined via the public link? Not by name or email — they appear as Anonymous with no address. If you need per-tester identity (for crash/feedback attribution), use email invites instead.
Related reading
- TestFlight Beta review is slow
- TestFlight build not showing on device
- TestFlight tester can’t redeem code
- TestFlight build stuck in Processing
Tags: #Troubleshooting #App Store #App review #TestFlight #External tester