You sent your tester a TestFlight public link or an 8-character redemption code. They tap the link in their browser, it opens TestFlight, and they see “This code is invalid” or “This beta is not accepting new testers.” You confirm the link works in your own browser — opens fine, lands on the “Start Testing” screen — so the link itself isn’t broken. Something about the tester’s environment, their Apple ID, or your group state is mismatched.
TestFlight invite redemption has a handful of strict preconditions: the tester’s Apple ID country must match a region your app is available in, the same Apple ID cannot already be in the same build’s group, the group’s tester count cap must not be reached, and the TestFlight app on the device must be up to date. Walking through these usually finds the cause in 5 minutes.
Common causes
Ordered by hit rate.
1. Apple ID country doesn’t match app’s available regions
Your app is available in US and CA only. The tester’s Apple ID is registered in JP. When they tap the redemption link, TestFlight checks region compatibility and rejects.
How to spot it: Ask the tester to check Settings → Apple ID → top of screen → Region. Compare against your App Store Connect → Pricing and Availability list. If their region isn’t in your list, that’s the block.
2. Same Apple ID already joined the group
The tester previously accepted an invite (perhaps for an older build, or to a sibling group) using the same Apple ID. TestFlight thinks they’re already a tester and rejects the new redemption.
How to spot it: App Store Connect → TestFlight → search the tester’s email across all groups. If they appear in any group with the same build, that’s the conflict.
3. External tester slot is full (10,000 cap)
Public link groups have a configurable cap (default 100, max 10,000). When the cap is hit, new redemptions fail with “This beta is not accepting new testers” — even though the link works.
How to spot it: TestFlight → External Testing → your group with public link → look at the tester count vs cap. If at or near cap, raise it or remove inactive testers.
4. TestFlight app version on tester’s device is too old
If the tester hasn’t updated TestFlight in a year, the older version may fail to redeem newer codes/links. Apple has occasionally rolled out backend changes that require recent TestFlight clients.
How to spot it: Ask the tester to open the App Store, search “TestFlight,” and check if it shows “Update.”
5. Apple ID has not yet accepted Sandbox or TestFlight terms
A brand-new Apple ID, or one that’s never used TestFlight, has to accept the TestFlight terms of service before redemption succeeds. The first redemption can fail silently if the terms acceptance hasn’t been completed.
How to spot it: Ask the tester to open the TestFlight app directly first (without the redemption link), sign in, accept any prompts, then try the link again.
6. The public link or code was revoked / expired
You may have disabled the public link without realizing, or the build it pointed to was withdrawn. The code returns invalid until you reactivate the link.
How to spot it: App Store Connect → TestFlight → your group → check Public Link is enabled. If disabled, re-enable. Confirm the group has a Ready-to-Test build attached.
7. Tester is on macOS / iPadOS with restricted TestFlight setup
Some Mac configurations (Apple Silicon, with iOS apps disabled) and some iPad setups can fail to redeem iPhone-only TestFlight builds. The link “works” but the app can’t be installed on their device.
How to spot it: Ask the tester to try on iPhone first; if iPhone works but Mac/iPad doesn’t, you’ve found the limit. Adjust the build’s supported devices or guide them to use iPhone.
Information to collect
- The exact error message the tester sees (screenshot is best).
- The tester’s Apple ID country and the device they’re using.
- Which redemption mechanism: public link, email invite, or 8-character code.
- Group name + current tester count + cap.
- Build status (Ready to Test, Waiting for Review, etc.) and which builds are attached.
Shortest path to fix
Step 1: Verify the link / code works on a second account
Try the link in a private browser window with a different Apple ID (or borrow a colleague’s). If it works, the link is fine and the problem is the original tester’s setup.
If it fails on a second account too, the issue is on your side (group state, build attachment, link disabled).
Step 2: Check the tester’s Apple ID region
Ask: “What country is your Apple ID set to? (Settings → tap your name → Region.)” Compare against App Store Connect → Pricing and Availability.
If region mismatch is the cause:
- Expand your app’s availability to include their region (App Store Connect → Pricing and Availability).
- Or have the tester use a different Apple ID in your supported region (note: switching Apple ID country has restrictions).
Step 3: Check the group’s tester cap
App Store Connect → TestFlight → External Testing → your group → look at “Testers (X / Y).”
If at cap:
- Raise the cap up to 10,000 max.
- Or remove inactive testers (those who never installed): click each → Remove.
Step 4: Have tester leave any prior group first
If the same Apple ID was in a previous group:
- In the tester’s TestFlight app, open the app’s listing → tap ”…” → “Stop Testing.”
- Then click the redemption link again.
Step 5: Update or reinstall TestFlight on tester’s device
Ask the tester to:
- Open App Store → search “TestFlight” → update if available.
- If no update, delete TestFlight and reinstall.
- Sign in with the matching Apple ID.
- Accept any terms-of-service prompts on first launch.
- Click the redemption link again.
Step 6: Switch redemption mechanism
Email invite and public link both work, but sometimes one fails where the other succeeds:
- Public link fails → try email invite: App Store Connect → TestFlight → External Testing → your group → ”+” → add tester by email → tester gets email with separate link.
- Email fails → try public link: enable it for the group, share the URL directly.
How to confirm the fix
- The tester reaches the “Start Testing” screen and successfully taps Install.
- App Store Connect → TestFlight → your group shows the tester in “Available to Test” or “Installed” state.
- The build installs and launches on the tester’s device.
- A second redemption test (e.g., from your own throwaway Apple ID) also succeeds.
If it still fails
- Have the tester send a screenshot of the exact error; the wording (“invalid code” vs “not accepting” vs “not available in your region”) points to different causes.
- Check Apple System Status for TestFlight redemption-side incidents.
- Try a completely fresh email and Apple ID (e.g., from a free Gmail) to confirm whether the link is functional end-to-end.
- Contact App Review via the Contact form if a tester reports inability to redeem and all the above fail — rare but real backend bugs occur.
Prevention
- Ask testers up front which country their Apple ID uses; prefer public TestFlight links over email invites to dodge inbox issues.
- Keep an updated
TESTERS.mdmapping email → Apple ID region → preferred device, so mismatches are caught at invite time. - Set public link cap to 10,000 from day one if you’re doing public-link distribution; you’ll never hit the cap accidentally.
- Whenever you remove a build from a group, also notify any new testers that they’ll need to wait for the next build.
- For corporate / restricted-region testers, set up a parallel beta channel via a public link a tester can self-redeem with any Apple ID you’ve pre-approved.
Related reading
- External tester not receiving invite
- TestFlight build not showing on device
- Expired provisioning profile build
- TestFlight build expired
Tags: #Troubleshooting