Apple's TestFlight page says: "You can test a build for up to 90 days", and "Your build becomes unavailable for testers after 90 days" (retrieved 2026-10-24). After that, testers cannot use that build through TestFlight.
What testers see
The build is unavailable. A tester who has not installed it cannot get it. For a tester who has it installed, expect that it will stop working as a test build; ask them to confirm instead of guessing.
How to renew
You cannot extend an old build. You replace it:
- Make a new build with a higher build number (the version can stay the same).
- Upload it to App Store Connect and wait for processing.
- Add it to your internal and external groups.
- Tell the testers to open TestFlight and update. Include what changed and what to look at.
- If it is a later build for the same app, a full review may not be needed ("Subsequent builds may not require a full review"). A new version number could differ; read the status in App Store Connect.
Avoid the surprise
- Write the upload date of each build in a note. Add 90 days and put the date in your calendar a week earlier.
- For long tests, plan a fresh build every few weeks even without code changes. It keeps testers on the current version.
- Use release notes in TestFlight so testers know what to test.
- If testers are scattered, a public link lets new people join the current build, but mind its limits.
Who fixes what
| Situation | Owner |
|---|---|
| Build older than 90 days | You: upload a new one |
| Tester has not updated | Tester: open TestFlight |
| New build waiting for review | Apple |
Need fresh testers when the new build is out? Start here.
Related: App testing problems: causes and fixes, Beta App Review waiting, TestFlight public link limits.