Why this happens
TestFlight public links (https://testflight.apple.com/join/...) never generate or require a redeem code. Redeem codes only exist for individual email invitations sent directly from App Store Connect. When a tester tells you that TestFlight is asking for an invitation code, nothing is broken in your build—the tester got stuck halfway through Apple’s two-step onboarding web page.
When someone without TestFlight installed taps your public link on an iPhone or iPad, Apple opens a landing page divided into Step 1: Get TestFlight and Step 2: Join the Beta. Most first-time testers tap the App Store button under Step 1, download TestFlight, and immediately tap Open inside the App Store. Because TestFlight was launched directly rather than from your beta URL, it knows nothing about your app. It displays No Apps Available to Test, tells the user to contact the developer for an invitation code, and shows a prominent Redeem button in the top corner.
The exact same dead end happens when testers open your public link inside an in-app browser (such as Slack, Gmail, Discord, Instagram, or WhatsApp) that blocks iOS Universal Links from automatically handing off to the TestFlight app, or when they click the link on a Windows PC or Mac where iOS TestFlight isn’t installed.
How to fix it
1. Have the tester tap the public link again after installing TestFlight
Once the TestFlight app is already on the device, tapping the public URL again triggers an iOS Universal Link—or lets the user complete Step 2 on the web page—passing the beta token directly into TestFlight without a code.
Send these exact steps to your tester:
- Install the TestFlight app from the App Store first and complete its initial welcome prompt.
- Close TestFlight and go back to the message, email, or web page containing the
https://testflight.apple.com/join/...link. - Tap the public link a second time.
- If TestFlight opens automatically, tap Accept and then Install.
- If a web page opens instead, scroll past Step 1 to Step 2: Join the Beta and tap Start Testing (or tap OPEN in the TestFlight banner at the very top of Safari).
On smaller iPhone screens or devices with larger Dynamic Type text sizes, Step 2 is often pushed below the fold. Testers frequently assume the page only contains the App Store download link unless you tell them to scroll down.
2. Break out of in-app browsers into Safari
Many chat, email, and social apps open web links inside an embedded web view instead of mobile Safari. Embedded web views often suppress Universal Link redirection, leaving the user stuck on the web instructions page even when TestFlight is already installed.
If tapping Start Testing under Step 2 does nothing or reloads the same page:
- Tap the browser menu icon or compass icon in the corner of the in-app browser and select Open in Safari (or Open in Default Browser).
- Alternatively, long-press the
https://testflight.apple.com/join/...URL, tap Copy, open the Notes or Messages app, paste it, and tap the link from there so iOS routes it directly to TestFlight. - If pasting directly into Safari’s address bar, scroll down on the loaded page and tap Start Testing under Step 2, as typing or pasting into the URL bar bypasses automatic Universal Link routing on initial load.
If you link to your TestFlight beta from inside an existing iOS production app, never load the public link inside WKWebView or SFSafariViewController. Always hand the URL to the system so iOS opens the TestFlight app directly:
import SwiftUI
struct JoinBetaButton: View {
private let betaURL = URL(string: "https://testflight.apple.com/join/YOUR_CODE")!
var body: some View {
// Link uses OpenURLAction, which triggers Universal Links cleanly
Link("Join the iOS Beta", destination: betaURL)
}
}
In UIKit, pass the URL to UIApplication.shared.open(betaURL) rather than presenting an internal browser controller.
3. Send an email invitation if the tester needs a real redeem code
Sometimes sending an actual redeem code is faster than troubleshooting a non-technical tester’s browser, or it is strictly required—for example, when a tester opens their email on a desktop computer while holding a test iPhone, or when testing a tvOS app on Apple TV (which has no web browser to open public links).
To generate an email invitation with a redeem code:
- Sign in to App Store Connect and go to Apps.
- Select your app and click the TestFlight tab at the top.
- In the left sidebar, select an External Testing group (or Internal Testing if the person is part of your App Store Connect team).
- Ensure at least one valid build is added under the Builds section.
- Click the + button next to Testers and choose Add New Testers.
- Enter the tester’s email address and click Add.
Apple immediately emails an invitation to that address. When the tester opens that email on a desktop computer and clicks View in TestFlight, Apple displays a step-by-step page containing a unique alphanumeric redeem code at the bottom. They can then tap Redeem inside the TestFlight app on their iPhone, iPad, or Apple TV and enter that code.
4. Check your public link and build status in App Store Connect
If returning to Safari and tapping Start Testing shows an alert in TestFlight stating that the beta isn’t accepting new testers or no build is available, check the developer configuration:
- Open App Store Connect > Apps > Your App > TestFlight and select your external testing group.
- Under Public Link, verify that the link is enabled and that you haven’t reached your custom tester limit (if you set a cap below TestFlight’s 10,000 external tester maximum).
- Under Builds, confirm that at least one build has a Testing status. The first build of a new version in External Testing must pass Beta App Review before the public link works for external users.
- Check the expiration column. TestFlight builds expire 90 days after upload; if every build in the group has expired, new public-link visitors cannot install the app.
How to prevent it
- Include two-line instructions whenever you share a public link: Tell testers up front: “1. Install TestFlight from the App Store first. 2. Come back and tap this beta link again on your iPhone in Safari.” That single note eliminates almost every redeem-code support ticket.
- Warn testers not to click the link on a desktop computer: Unless your beta includes a macOS build, opening a TestFlight public link on a computer shows installation steps without a way to push the app to an iPhone.
- Use
LinkorUIApplication.shared.openin native apps: Avoid openingtestflight.apple.comURLs insideSFSafariViewControllerorWKWebView, which break automatic Universal Link handoff. - Keep an active, approved build in your External Testing group: Upload a fresh build before the 90-day TestFlight expiration window runs out so your public link stays active.
FAQ
Where do I find the redeem code for a TestFlight public link in App Store Connect?
You cannot find one because TestFlight public links do not have redeem codes. The short alphanumeric string at the end of https://testflight.apple.com/join/XXXXXXXX is a URL token, and typing it into TestFlight’s Redeem box will always fail as invalid.
How do testers join a TestFlight beta on Apple TV?
Apple TV does not have Safari, so tvOS testers cannot open public links directly on the device unless they first accept the public link on an iPhone or iPad signed in to the same Apple Account. Otherwise, invite them via email in App Store Connect so they receive an actual redeem code to type into TestFlight on Apple TV.
Does the tester need to use a specific Apple Account for a public link?
No. Anyone with a valid Apple Account signed in to the App Store on their device can join via a TestFlight public link, and even when invited by email, they can redeem the invitation while signed in to a different Apple Account on their device.
Parts of this guide are adapted from content licensed under CC BY-SA 4.0; this article is shared under the same license.
