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 one of these (as of June 2026 the exact wording is):
This code is invalid.Couldn't redeem TestFlight invitation code. This invitation has been revoked or is invalid. Request a new invitation from the developer.This beta isn't accepting any new testers right now.
You confirm the link works in your own browser — it opens fine and 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.
Fastest fix (covers most cases): make sure the group has a non-expired build (uploaded within the last 90 days) attached and in a Ready to Submit / approved state, then have the tester open the TestFlight app directly, sign in with the same Apple ID the invite was sent to, and tap the link again from inside that signed-in session. The two most common real causes are (1) the tester is signed into a different Apple ID than the one you invited, and (2) the build attached to the group expired at day 90.
TestFlight redemption has a handful of strict preconditions: the build must be non-expired and approved, the tester’s Apple ID country must match a region your app is available in, the email-invite code is locked to whichever Apple ID is signed in when it’s redeemed, the group’s tester cap must not be reached, and the TestFlight app must be reasonably current. Walking through the list below usually finds the cause in about 5 minutes.
Match the error string to the cause first
The exact wording the tester sees is the single best diagnostic. Ask for a screenshot, then start with the matching row.
| What the tester sees | Most likely cause | Jump to |
|---|---|---|
This code is invalid. | Wrong Apple ID signed in, code already redeemed, or link revoked | Causes 2, 6, 8 |
Couldn't redeem... This invitation has been revoked or is invalid. | Email-invite code locked to a different Apple ID, or you revoked the link | Causes 2, 6 |
This beta isn't accepting any new testers right now. | Tester cap reached, or the attached build expired (day 90) | Causes 3, 5 |
App not available in your region / nothing installs | Apple ID country not in your availability list | Cause 1 |
| Link opens, install fails on Mac/iPad only | Device not supported by the build | Cause 7 |
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. Tester is signed into a different Apple ID than you invited
This is the most common cause of This code is invalid and the ...revoked or is invalid wording, per Apple’s developer forums (as of June 2026). An email invite redeems against whatever Apple ID is currently signed into the device, not the address you typed. If you invite tester@work.com but they tap the link on a phone signed into tester@personal.com, the code redeems (and locks) to the personal ID, and a later attempt with the work ID fails.
A related case: the tester previously accepted an invite (an older build, or a sibling group) with the same ID, so TestFlight already counts them as a tester and rejects the new redemption.
How to spot it: Have the tester open Settings → tap their name (top of screen) and read the Apple ID email shown there. It must exactly match the address you invited. Also search the tester’s email in App Store Connect → TestFlight → your group; if they already appear in any group on the same build, that’s the conflict.
3. External tester slot is full (10,000 cap)
An app can have at most 10,000 external testers (hard Apple limit, unchanged as of June 2026). A public link can also carry its own optional limit you set between 1 and 10,000. When either cap is hit, new redemptions fail with This beta isn't accepting any new testers right now — even though the link still opens for you.
How to spot it: App Store Connect → TestFlight → External Testing → your group. The insight cards at the top of the group page flag when the public link is full; you can also compare the tester count against the limit shown next to the public link.
4. The attached build expired at day 90
TestFlight builds are installable for only 90 days after upload, and Apple does not extend or reactivate them (confirmed June 2026). Once the build a group points to is past day 90, new testers hitting the link see This beta isn't accepting any new testers right now and existing testers see “expired.” This is one of the two causes of the “not accepting” string (the other is a full cap).
How to spot it: App Store Connect → TestFlight → your group → look at the attached build’s upload date and status. If it’s older than 90 days, upload a fresh build. Note the first build of a new version still needs Beta App Review before external testers can install it, so do this well before day 90.
5. TestFlight app version on tester’s device is too old, or terms not accepted
If the tester hasn’t updated TestFlight in a long time, the older client can fail to redeem newer codes/links — Apple occasionally ships backend changes that require a recent TestFlight version. Separately, a brand-new Apple ID, or one that’s never used TestFlight, must accept the TestFlight terms of service on first launch before redemption succeeds; skip that and the first redemption can fail silently.
How to spot it: Ask the tester to open the App Store, search “TestFlight,” and check for an “Update” button. Then have them open the TestFlight app directly (without the link), sign in, accept any prompts, and only then tap the redemption link.
6. The public link was revoked, or the build was withdrawn
You may have disabled or deleted the public link without realizing, or the build it pointed to was removed from the group. The code returns revoked or is invalid until you re-create or re-enable the link.
How to spot it: App Store Connect → TestFlight → External Testing → your group → Testers tab. If there’s no active public link, click “Create Public Link” (or “Manage” to re-enable an existing one). Confirm the group has an approved, non-expired build attached.
7. Managed Apple Account from a reserved domain
Since an October 2025 TestFlight change, most Managed Apple Accounts from Apple Business Manager or Apple School Manager can test builds — but two kinds still cannot: an account whose address is on a reserved domain, and any account assigned the Student role. Those redemptions simply won’t go through, which trips up some corporate or school accounts.
How to spot it: Ask whether the account was issued by their company or school. If the Apple ID is on a reserved (org-owned) domain or carries a Student role, have them redeem with a personal Apple ID in a supported region instead. The managed account must also be able to receive email for the invite to work.
8. 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: Confirm the attached build is current and approved
App Store Connect → TestFlight → your group → check the build’s upload date and status.
- If the build is older than 90 days, upload a new one (the first build of a new version needs Beta App Review before external testers can install).
- Confirm the build is approved/Ready to Submit and actually attached to this group, not just sitting in the build list.
Step 4: Check the group’s tester cap
App Store Connect → TestFlight → External Testing → your group → look at the tester count vs the public-link limit (insight cards at the top flag a full link).
If at cap:
- Raise the public-link limit (up to 10,000 max) via “Manage” next to the public link.
- Or remove inactive testers (those who never installed): click each → Remove.
Step 5: Fix the Apple ID, then leave any prior group
- Have the tester confirm
Settings → tap their nameshows the exact Apple ID you invited, and that its country is in your availability list. - If the same Apple ID was already in a previous group: in the tester’s TestFlight app, open the app’s listing → tap ”…” → “Stop Testing,” then tap the redemption link again from inside the signed-in TestFlight app.
Step 6: 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.
- Tap the redemption link again.
Step 7: 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 → Testers tab → ”+” → “Email” → add tester by email → tester gets their own link. Remind them to redeem it on a device signed into that exact Apple ID.
- Email fails → try public link: Testers tab → “Create Public Link” → “Open to Anyone” (optionally set a Tester Limit) → 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 (
This code is invalidvs...revoked or is invalidvsisn't accepting any new testers) points to different causes. - Check Apple’s Developer System Status page for a TestFlight incident before assuming it’s your config.
- Try a completely fresh email and Apple ID (e.g., a new free iCloud or Gmail address) to confirm whether the link is functional end-to-end.
- If a known Apple ID is permanently locked to the wrong account (the forum-documented email-invite trap), delete that tester from the group, wait for the change to propagate, then re-invite as a public link rather than re-sending the same email code.
- Contact App Review via the Contact Us form if testers still can’t redeem and everything above checks out — rare but real backend bugs occur.
FAQ
Why does my TestFlight link work for me but not my tester?
The link being live only proves the group and build are fine on your side. Redemption is rejected by the tester’s environment: their Apple ID country, the Apple ID they’re actually signed into, an expired build, a full cap, or a managed (work/school) account. Match their exact error string to the table above.
Does the tester’s Apple ID country really have to match my app’s regions?
Yes. TestFlight checks the Apple ID’s registered country against your App Store Connect → Pricing and Availability list at redemption time. If their country isn’t on the list, expand availability or have them use an Apple ID registered in a supported region. Switching an Apple ID’s country has its own restrictions (no unspent store credit, etc.), so expanding availability is usually easier.
Why did the email invite redeem to the wrong Apple ID?
An email invite redeems against whatever Apple ID is signed into the device when the link is tapped, not the address you typed. If the tester is signed into a personal ID while you invited their work ID, the code locks to the personal one. Apple re-sends the same code on re-invite rather than minting a new one, so the clean fix is to delete the tester and switch to a public link, which any signed-in supported account can redeem.
How long is a TestFlight build good for?
90 days from upload, with no extensions (as of June 2026). Upload a fresh build well before day 90 so the group always has a live build; otherwise new testers hit This beta isn't accepting any new testers right now and existing testers see “expired.”
Can a corporate or school Apple account test my beta?
Mostly yes, since an October 2025 TestFlight change: most Managed Apple Accounts from Apple Business Manager or Apple School Manager can now be invited. The exceptions still blocked are accounts on a reserved (org-owned) domain and accounts with the Student role — those can’t redeem at all, so have them use a personal Apple ID in a supported region instead.
Prevention
- Ask testers up front which country their Apple ID uses, and which Apple ID address is actually signed into their device.
- Prefer public TestFlight links over email invites: they sidestep both inbox delivery problems and the “redeemed on the wrong Apple ID” trap.
- Keep an updated
TESTERS.mdmapping email → Apple ID region → preferred device, so mismatches are caught at invite time. - Set a generous public-link limit (up to 10,000) from day one if you’re doing public-link distribution; you’ll never hit the cap accidentally.
- Upload a new build before any attached build reaches day 90, and notify testers when you swap builds so nobody lands on an expired one.
Related reading
- External tester not receiving invite
- TestFlight build not showing on device
- Expired provisioning profile build
- TestFlight build expired
Tags: #Troubleshooting