TestFlight Public Link Not Working? Here's How to Fix It

When your TestFlight public link stops working or never appears, testers cannot join your beta and you lose time debugging Apple's UI. This guide covers the main reasons links break, how to fix each one, and how to avoid the problem entirely with an automated invite flow for private apps.

Why Your TestFlight Public Link Is Not Working

Apple only provides a public link for builds that have passed Beta App Review. If your link is missing, broken, or testers see errors, one of these causes usually applies.

• Beta App Review not completed or not passed. The public link is only enabled after your build is submitted to and approved in Beta App Review. If you have not submitted, or submission is pending or rejected, no public link exists. Check App Store Connect under TestFlight for the build's review status.
• Public link disabled. You can turn the link off in App Store Connect. If it was working and then stopped, someone may have disabled it, or it was disabled when a new build was added. Re-enable it in the external testing group for the correct build.
• Wrong or expired build. Each build has its own link. If you promoted a new build and did not enable the link for that build, or the previous build expired (90-day limit), the old link can stop working. Ensure the link is enabled for the build you want testers to install.
• External testing group full. External testers are capped at 10,000 per app. If the group is full, new testers cannot join and may see an error. Remove inactive testers or create a new group and enable the link for that group.
• App or build no longer available. If the app was removed from sale or the build was removed from TestFlight, the link will fail. Restore the build or app state in App Store Connect if possible.
• Regional or account restrictions. TestFlight links can be affected by the tester's region or Apple ID. Less common, but if only some testers fail, have them check their region and that they are signed in with a valid Apple ID.

How to Fix Each Issue (Step-by-Step Troubleshooting)

No public link option at all

1. In App Store Connect, open your app and go to TestFlight.
2. Select the build you want to distribute.
3. Under External Testing, confirm the build is in a group that has been submitted for Beta App Review.
4. If not submitted: add the group, fill in test info and contact, and submit for review.
5. After approval, open that external group and enable "Public Link" (or equivalent).
6. Copy the link and test it in a private/incognito window.

Link was working, now it does not

1. Check that the public link is still enabled for the intended external group.
2. Confirm the build has not expired (TestFlight builds expire after 90 days).
3. If you added a new build, enable the link for the new build or the group that contains it.
4. If the group is full (10,000 testers), create a new group, add the build, submit for review if required, and enable the link for the new group.

Testers see "beta full" or cannot join

1. In App Store Connect, open the external testing group and check tester count.
2. If at or near 10,000, remove testers who no longer need access or create a new group.
3. Ensure the link points to a group that has room and that the build is still available.

Common TestFlight Error Messages Explained

• "This beta is full." The external group has reached the 10,000-tester limit. Remove inactive testers or use a new group and a new link.
• "Unable to install" / "This app is no longer available." The build may have expired (90 days) or been removed. Upload a new build, add it to the group, and share the link for that build.
• Link opens but nothing loads or "Page not found." The link may be for a disabled or removed build, or the public link was turned off. Re-enable it in App Store Connect for the correct build and group.
• "You're not invited to test this app." Usually means the link is wrong or the tester is using a different Apple ID. Have them open the exact link in Safari and ensure they are signed in with the Apple ID that received (or will receive) the invite, if applicable. For a true public link, this can also mean the link was regenerated or disabled.
• Spinner or blank screen. Often a temporary Apple or network issue. Retry; if it persists, check App Store Connect status and that the build and link are still valid.

Why Public Links Break Frequently

Public links are tied to a specific build and group. When you upload a new build, you must add it to an external group and, after Beta App Review, enable the link for that build. If you forget, or the previous build expires, the old link stops working. Apple also rotates or regenerates links when you disable and re-enable them, so bookmarked or shared URLs can go stale. There is no "permanent" public link that survives all build and group changes; you have to maintain it. For teams that ship often or manage multiple apps, this maintenance is a common source of broken links.

How to Avoid Public Link Issues Completely

If you need a single, shareable way to get testers into TestFlight but want to avoid Beta App Review and link churn, use an automated invite flow instead of Apple's public link. With a tool like TF Invites, you connect your app once via the App Store Connect API and get a stable invite page URL. You share that link; testers enter their email; the system sends the App Store Connect invitation and adds them to your chosen TestFlight group when they accept. No public link to enable or disable, no 90-day build link expiry in the same way—you just keep sharing the same invite URL and add new builds to your TestFlight group as usual. This approach is built for private apps that cannot or do not use Apple's public link. You get one link, full control over who signs up, and no dependency on Beta App Review. See pricing and the main site to set it up.

FAQ

Why is my TestFlight public link not working?

The most common reasons are: Beta App Review not completed or failed, the public link disabled in App Store Connect, the build expired or removed, or the external group is full. Check the build and group in App Store Connect and re-enable the link for the correct build.

How do I get my TestFlight public link back?

In App Store Connect, go to TestFlight, select the external group and build, and turn the public link back on. If the build expired, add a new build to the group, get it through Beta App Review if required, then enable the link for that build.

What does "This beta is full" mean?

Your external testing group has reached Apple's limit of 10,000 testers. Remove testers who no longer need access or create a new group and enable a new public link for that group.

Do TestFlight public links expire?

The link itself can become invalid when you disable it or when the build it points to expires (builds expire 90 days after upload). Enabling the link for a new build gives you a valid link again; the URL may change if Apple regenerates it.

Can I have a stable TestFlight link that does not break?

Apple's public link is tied to the build and group, so it can change when builds or settings change. For a stable, single URL that does not depend on Beta App Review, use an automated invite solution like TF Invites: one invite page link, testers sign up, and the system adds them to TestFlight via the API. See iOS TestFlight public link for private apps.

My TestFlight link works for me but not for testers. Why?

You may be an internal tester (team member) while the link is for external testers, or the link might be disabled for external use. Ensure the public link is enabled for the external group and that testers use the exact URL. If they see "beta full," the group is at capacity; remove testers or use a new group and link.