TL;DR: An app can stay on TestFlight only while its build is still valid and the developer keeps it available. Testers also need a valid invite or public link and a device or OS that meets the beta’s requirements, so

Short answer

A TestFlight app stays available only while the build is valid and the developer keeps it available. Apple says testers can access only the builds the developer makes available to them, and testers need a valid email or public link invite plus a device that meets the beta requirements. The public TestFlight page is the clearest source for those rules: TestFlight.

What controls how long a build remains available

Three things usually decide whether a tester can keep using a build:

  1. The build expires.
  2. The developer stops distributing it or uploads a newer one.
  3. The tester still has access through a valid invite or public link.

If any of those changes, the build can disappear from TestFlight quickly. That is normal for beta software.

What Apple says about access and eligibility

Apple says testers must accept an email or public link invitation from the developer and have a device available for testing. They may use only the builds the developer has chosen to share with them. Apple also says developers can set criteria for a beta, such as a preferred device or OS, and testers must meet those requirements to accept the invitation.

Apple’s TestFlight page also lists platform requirements, including iOS or iPadOS 16 or later for iPhone and iPad apps, macOS 13 or later for Mac apps, tvOS 18 or later for Apple TV apps, visionOS 1 or later for Apple Vision Pro apps, and watchOS 9 or later for Apple Watch apps. If the device or OS no longer matches, access can fail even if the invite used to work.

How this affects a pre-review iOS workflow

Use it to verify the app, catch bugs, and check whether the build and the listing tell the same story before App Store review.

A practical flow is simple: test the beta, fix the problems, upload a fresh build when needed, and move toward App Store review once the app is ready.

Worked example: a beta build waiting on review fixes

A developer uploads a build to TestFlight and shares it with testers.

The developer fixes the issues, uploads Build 43, and keeps the same testers on the beta. If Build 42 is still active, testers can move to the newer build without losing the test cycle. If Build 42 expires first, they lose access to it, but they can still test Build 43 as long as their invite is valid and their device still meets the beta requirements.

That is the basic rhythm: collect feedback, patch, replace the build, repeat until the app is ready to submit.

What to check if testers suddenly lose access

If testers can no longer open the beta, check these first:

  • Whether the build expired.
  • Whether a newer build replaced the old one.
  • Whether the invite link or email invitation is still valid.
  • Whether the tester’s device and OS still meet the beta requirements.
  • Whether the tester still has access to that beta from the developer.

Related prep step: keep the App Store listing aligned

This question matters most when TestFlight is part of release prep. The beta should be kept aligned with the App Store listing, screenshots, and actual experience.

It helps you check the app and the listing together, which is the point of using TestFlight before review.

Related: How to Write App Store Screenshot Captions That Read Fast