Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My testers cannot install the beta app from TestFlight

Short answer

A tester can install only a build that has been added to their group, approved if it needs review, and shared with them. Apple lists the limits: the first build for external testers goes to review, internal-only builds cannot reach external groups, and public links can be full, filtered or disabled. Check each one.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • A tester says the app is not in their TestFlight.
  • The invitation email arrived but there is nothing to install.
  • Only some testers can install, others cannot.
  • The build shows as in review or rejected.
  • The public link says it is full or does nothing.

Why does this happen?

  1. The build is waiting for Apple review

    Apple says the first build for a version needs a full review before external testing can begin, and later builds might not.

  2. The build was uploaded as internal only

    Apple says builds uploaded as TestFlight Internal Only can go only to internal groups, so external testers will never see them.

  3. Testers were not notified or the build was rejected

    If automatic notification is off, someone must press Notify Testers after approval. A rejected build shows as Rejected, with details under App Review.

  4. The public link is limited

    Apple lets you filter a public link by device or operating system, set a tester limit, and disable it. A tester who does not match, or arrives after it is full, cannot join.

  5. The build has expired or the account type is unsupported

    Apple says a build can be tested for up to 90 days and then becomes unavailable, and that Managed Apple Accounts in reserved domains cannot be used to test builds.

What can I do about it today?

  1. Open the build in TestFlightIn App Store Connect check its status: Testing, In Review, Rejected or Expired.
  2. Check which group the tester is inThe build has to be added to that group, and the tester has to be a member.
  3. Ask the tester what they seeA screenshot of their TestFlight app tells you more than a description.
  4. Check the public link settingsLook at the device filter, the tester limit and whether the link is still switched on.
  5. Do not send more invitations yetRepeated invitations create confusion. Fix the cause, then invite once.

When should I bring someone in?

  • The build was rejected and the message is unclear.
  • Your own role does not allow you to see the build groups.
  • Testers are on many device types and nobody knows what is supported.

How do I handle it?

  1. Follow the path of one buildI trace the build from upload through group, review and notification.
  2. Find the first step that failsEach stage has its own status, so the failing stage is usually clear.
  3. Fix the setupGroups, link settings and notifications are corrected, with your approval.
  4. Verify with a real testerThe fix is done when a tester installs and opens the build.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Why does my first build take longer?

Apple says the first build for a version requires a full review for external testing; later builds might not.

How many external testers can I invite?

Apple states up to 10,000 external testers per app.

Can anyone share the public link?

Apple says anyone can share it, and you can disable it at any time.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.