TestFlight previous builds: install an older build, and what expiry means

How testers install an older TestFlight build, how the 90-day expiry works, how to expire a build yourself, and why a build doesn't show up for testers.

Storewatch blog cover: TestFlight previous builds: install an older build, and what expiry means

On iPhone and iPad, a tester installs an older TestFlight build by opening your app in the TestFlight app and tapping Previous Builds (or Versions and Build Groups if you use Xcode Cloud), then picking the build. It replaces what is installed. A build only appears there while it is still available: Apple says each build can be tested for up to 90 days from upload.

This page covers the tester steps, expiry, how to expire a build yourself, build numbers versus version numbers, and the usual reasons a build doesn't show up. Facts are from Apple's tester instructions and App Store Connect Help, as of November 2026.

How testers install a previous build

  1. Open the TestFlight app and tap your app.
  2. Tap Previous Builds. With Xcode Cloud, the label is Versions and Build Groups.
  3. Pick the build and install it.

Apple says the selected build replaces what's currently installed. A tester can only pick builds you have made available to them, and only while those builds haven't expired. Apple's TestFlight page says testers can access all available beta builds shared with them, and that you can share up to 100 builds.

Heads up: I could only verify the iPhone and iPad steps in Apple's tester instructions. Menus on Mac, Apple TV and Apple Vision Pro differ, so check Apple's page for those.

Does the data survive a downgrade?

Apple doesn't document what happens to local app data when a tester goes back to an older build. If your newer build migrated a database, the older one may not read it. Test downgrading yourself before you tell anyone to do it, or ask the tester to delete and reinstall.

Build expiry: the 90 days

Apple's TestFlight overview says you can test a build for up to 90 days, and the build becomes unavailable to testers after that. The tester instructions say the 90 days start on the day the build was uploaded, not the day a tester got it.

In App Store Connect, an expired build shows the status Expired, which Apple describes as "passed its 90-day availability window" (app build statuses). That's the answer to "testflight build expired": the fix is to upload a new build with a new build number and add it to the group.

If you don't expire a build and you submit it to the App Store, Apple says invited testers can still test it after it goes live.

Expiring a build yourself

To stop people testing a build early (it's buggy, or it points at a retired server), expire it. Apple's Stop testing a build steps, for Account Holders, Admins and App Managers:

  1. In App Store Connect, open the app and click the TestFlight tab.
  2. Under Builds in the sidebar, click the platform.
  3. Click the build in the table.
  4. Click Expire Build.

Apple says the build no longer allows internal and external testers to install it. It doesn't say whether copies already installed stop launching, so don't count on expiring to disable a build in the field. If you just want one group to stop getting a build, remove it from that group instead. Apple notes testers already using a removed build keep access until they switch builds or stop testing.

Build numbers and version numbers

TestFlight lists builds by version and build number. The version is what you'd call 2.4 and what customers eventually see. The build number is how TestFlight tells uploads of the same version apart, so each upload needs one you haven't used for that version. Apple's CFBundleVersion reference is the source for the key itself.

One thing Apple does say in its build upload statuses: if an upload fails, you can reuse the same build number for your next upload. After a successful upload, bump it.

A practical habit: let your build system set the build number (for example from a CI run counter), so you never upload "2.4 (1)" twice by hand.

Why a build doesn't appear for testers

What you seeWhat it means
Still processingThe upload hasn't finished. Apple emails you when it does, and says more than 24 hours means something may be wrong.
Missing ComplianceExport compliance answers are missing. Provide them in the build's page.
Waiting for Review / In Beta ReviewExternal testers can't test until TestFlight App Review approves.
Ready to SubmitInternal testers can use it. Send it to review for external testing.
Not added to a groupA processed build still needs to be added to a tester group.
Expired or RejectedUpload a new build.

Processing

Apple's upload statuses page says that you get an email and the Build Uploads table updates when processing finishes. A Failed upload shows errors when you select it.

Export compliance

Without export compliance information the build is marked Missing Compliance (Apple's steps). Open the build, click Manage, answer the questions, then save or upload your documentation. You can also state your encryption settings in the app's Info.plist so you aren't asked each time.

Beta App Review for external testers

Internal testers can use a build once it's ready. External testers need approval first. Apple's external testers article says the first build for a version gets a full review, and later builds for that version might not. Only one build of each version can be in review at a time, and you can submit up to six builds for TestFlight App Review in 24 hours. See inviting TestFlight testers for the full picture.

One more cause: a build uploaded as TestFlight Internal Only from Xcode or Xcode Cloud can only be added to internal groups, never to external ones.

Keeping track of builds

Storewatch shows where your next version stands (Build uploaded, TestFlight, In review, Approved, Live) and what it's waiting for, so a build stuck before review is easy to spot. Once a version is live, it also compares its crash rate with the previous version's.

Frequently asked questions

How do I install an older build in TestFlight?

Open your app in the TestFlight app, tap Previous Builds (or Versions and Build Groups with Xcode Cloud), and choose the build. It replaces the installed one. The build must still be available to you.

How long do TestFlight builds last?

Up to 90 days from the day the build was uploaded, according to Apple. After that its status is Expired and testers can't use it.

Can I extend a TestFlight build past 90 days?

Apple doesn't document a way to. Upload a new build with a new build number and add it to your groups.

What does Expire Build do?

It stops internal and external testers from installing that build. Apple's page doesn't say what happens to copies already installed.

Why can't my testers see my new build?

Check whether it's still processing, missing export compliance, waiting for or rejected by Beta App Review (external testers), or not yet added to their group.

Is the build number the same as the version number?

No. The version is the release number customers see. The build number separates uploads of the same version in TestFlight.