In this guide
Your TestFlight public link worked yesterday and today people cannot join. Usually one of three things is going on: the link hit its own tester limit, the group criteria exclude the person, or you reached the external tester limit.
The numbers that matter
| Limit | Value | Where it comes from |
|---|---|---|
| External testers | up to 10,000 | Apple, TestFlight overview |
| Tester limit on one public link | optional, 1 to 10,000 | Apple, Invite external testers |
The link limit is something you set yourself. If you never set one, the link has no limit of its own, and Apple's overall limit of 10,000 external testers still applies.
Why a link stops accepting testers
- You set a tester limit and it is full. App Store Connect shows when a public link is full in the cards at the top of the group details page. Apple's page does not describe the behavior in more detail, so open the group and look.
- Filter criteria exclude the device. A link can be open to anyone or filtered by platform and OS version. If the build in the group needs a newer OS than your criteria allow, or the tester's device is outside the range, they cannot join. Make sure the builds in the group match the criteria.
- The link was disabled or changed. Under Manage next to Public Link you can disable the link, change who can join, or change the limit.
- No build is available. A group without a usable build has nothing to install. Builds are testable for up to 90 days, then they become unavailable.
How to fix it
- Open the external group in App Store Connect and check the public link cards.
- Choose Manage next to Public Link. Raise or remove the tester limit, or fix the criteria.
- Check that a build is attached to the group and has not expired.
- Re-send the link and ask one tester to try it.
You need the Account Holder, Admin or App Manager role to change the link.
Managing a large group
- Expect strangers. Anyone can share the link, so people may join without an invite from you. Testers who join by link show as anonymous in the Testers section, though installs, sessions and crashes are still counted.
- Set a limit on purpose. A limit that matches the number of testers you can actually read feedback from is more useful than "open to everyone".
- Use groups. Separate groups let you give different builds to different audiences.
- Keep the feedback loop small. More testers does not mean more useful feedback. Ten testers who answer specific questions beat a thousand silent installs.
When you need testers who actually respond
A public link brings installs, not necessarily feedback. AppReviewX is a different route: other developers give you private, structured feedback on your app, and one feedback you write earns one credit. Test groups are for Google Play (Android apps); test rounds cover apps that are already published. New accounts start with 0 credits.
More in App testing problems and fixes. Related: TestFlight feedback not arriving and Managed Apple Accounts cannot test.
Apple changes App Store Connect; re-check the linked pages. Not legal advice.