Overview: The 90-Day Lifespan Invariant
Every application binary uploaded to TestFlight carries an immutable expiration clock enforced by Apple's cloud infrastructure:
Authoritative Expiration Timestamps from Apple: Under Apple's platform architecture, each TestFlight build is available for beta testing for up to 90 calendar days. Apple's App Store Connect API returns an authoritative expirationDate ISO 8601 timestamp for every build. Apple does not provide any mechanism—via API, web portal, or developer support request—to extend, pause, or renew the 90-day lifespan of an existing build. Once a build reaches Apple's specified expiration date, it transitions to EXPIRED status and can never be reactivated.
When a TestFlight build expires:
- On Physical Devices: Testers who attempt to launch an expired build receive an operating system alert: > "Beta Has Expired — The developer of this app will need to upload a new build before you can continue using it." The app terminates immediately and will not open.
- In the TestFlight App: The build row displays an orange or gray Expired badge, and the "Open" or "Install" button is disabled.
- In App Store Connect: The build status changes to
Expired. It cannot be assigned to beta groups or submitted to App Review.
Crucially, the 90-day expiration clock applies strictly to TestFlight beta distribution. Live production releases published on the public Apple App Store never expire.
This guide explains the mechanics of Apple's expiration rules, demonstrates how to monitor build expiration using FlightDeck MCP's authoritative expirationDate field, provides copyable prompts for your AI assistant, and outlines an optional continuous delivery cadence so your beta testers are never locked out.
1. What Happens When a Build Expires (And What You Can and Cannot Do)
Understanding Apple's platform boundaries prevents wasted effort:
+-----------------------------------------------------------------------------------+
| TESTFLIGHT 90-DAY EXPIRATION TIMELINE |
+-----------------------------------------------------------------------------------+
| |
| [DAY 0: BUILD UPLOADED & VALIDATED] |
| Binary uploaded to App Store Connect. 90-day countdown begins immediately. |
| │ |
| ▼ |
| [DAYS 1 - 75: NORMAL ACTIVE TESTING] |
| Internal and external testers install and update builds freely. |
| │ |
| ▼ |
| [DAYS 76 - 89: REPLACEMENT WINDOW (<15 DAYS REMAINING)] |
| TestFlight app begins displaying yellow warning badges to testers. |
| Recommended: Upload new build to maintain uninterrupted access. |
| │ |
| ▼ |
| [DAY 90: HARD EXPIRATION] |
| Status transitions to EXPIRED. Build terminates on launch for all testers. |
| - Cannot be extended or un-expired. |
| - Cannot re-upload identical binary hash. Must increment CFBundleVersion. |
| - Local app container data persists on device (not deleted). |
| |
+-----------------------------------------------------------------------------------+
Key Invariants to Remember:
- No Extensions: You cannot click an "Extend 30 Days" button. The only way to continue beta testing is to upload a new binary.
- Increment Required: You cannot re-upload the exact same binary or reuse the same
CFBundleVersionbuild number. You must increment the build number (e.g., from14to15), recompile, and upload. - Tester Data Persists: When a build expires, the tester's local data (Core Data, SQLite, local files, User Defaults) remains safely stored on their physical iPhone. When you upload a new build and the tester updates via TestFlight, the app updates in place without wiping user data.
2. Inspecting Build Expiration via FlightDeck MCP
Rather than manually inspecting each build's date math in the web portal, FlightDeck's builds_list tool exposes the exact expirationDate (an ISO 8601 timestamp) and expired boolean for every build.
Your AI coding assistant can query these attributes, calculate remaining days, and alert you before testers experience lockout.
Copyable AI Assistant Prompt: Expiration Audit
Using FlightDeck, inspect all active TestFlight builds for [App Name].
Please perform an expiration audit:
1. List each active build by version and build number (e.g., 1.0.0 build 12).
2. Show the exact upload date and expiration date.
3. Calculate the number of days and hours remaining before each build expires.
4. Flag any builds that have less than 14 days remaining or have already expired.
5. Identify which beta groups are currently attached to these builds.
Recommend which build needs a replacement upload and provide the next recommended build number. Do not modify App Store Connect data.
3. The Continuous Beta Delivery Strategy: Preventing Tester Lockout
While Apple imposes no requirement on how frequently you upload builds, adopting an optional continuous delivery cadence ensures your active testers never encounter an unexpected expiration cliff:
+-----------------------------------------------------------------------------------+
| RECOMMENDED 3-WEEK RELEASE CADENCE |
+-----------------------------------------------------------------------------------+
| |
| Week 1: Build 10 Uploaded (90 Days Left) ──────> Active Testing Begins |
| Week 3: Build 11 Uploaded (90 Days Left) ──────> Tester Updates via TestFlight |
| Week 6: Build 12 Uploaded (90 Days Left) ──────> Clock Resets for Active Testers |
| |
| Outcome: Beta testers never approach the 90-day hard expiration cliff. |
+-----------------------------------------------------------------------------------+
The "Rolling Cadence" Best Practices:
- Ship Every 2 to 3 Weeks: By releasing an incremental build every 14 to 21 days, active testers always have an active build with 70+ days of remaining lifespan.
- Incremental Maintenance Builds: Even if major features are not finished, shipping an incremental maintenance build (bug fixes, localized string updates, or dependency bumps) keeps the beta pipeline alive.
- Re-associating Groups: When your new build is
VALIDand has attested export compliance, use FlightDeck'sbuild_add_to_beta_grouptool to attach the new build to your existing internal and external beta groups. Testers receive an immediate TestFlight notification to update.
4. Manual Web Portal Verification Steps
To check build expiration dates manually in App Store Connect:
- Log in to appstoreconnect.apple.com.
- Select your app from My Apps.
- Click the TestFlight tab.
- In the left navigation, select iOS Builds.
- Examine the build list: - Active builds display "Expires in X days" in the status column. - Builds nearing expiration show a yellow alert indicator. - Expired builds show an Expired badge.
+-------------------------------------------------------------------+
| APP STORE CONNECT PORTAL PATH |
+-------------------------------------------------------------------+
| App Store Connect |
| └── My Apps |
| └── [Your App] |
| └── TestFlight (Tab) |
| └── iOS Builds (Sidebar) |
| └── [Build Number] -> "Expires in X days"
+-------------------------------------------------------------------+
5. Deliberately Expiring a Broken Build Early vs. Group Retraction
While you cannot extend a build's expiration date, you can terminate a build early if you discover a critical regression, data loss issue, or security defect.
It is vital to distinguish among five operations that developers often confuse:
┌─────────────────────────────────────────────────────────────────────────────────────────────┐
│ FIVE DISTINCT BUILD LIFECYCLE OPERATIONS │
├─────────────────────────────────────────────────────────────────────────────────────────────┤
│ 1. Associating a Build with a Group (build_add_to_beta_group) │
│ POST /v1/builds/{id}/relationships/betaGroups │
│ Grants a beta group access to install the build. Does NOT affect expiration. │
│ │
│ 2. Removing a Build from a Group (build_remove_from_beta_group) │
│ DELETE /v1/builds/{id}/relationships/betaGroups │
│ Stops new installs for that group. Existing on-device installs continue to run. │
│ │
│ 3. Disabling Distribution to Testers │
│ Disabling public links or revoking tester invitations. Existing installs remain active. │
│ │
│ 4. Early Account-Wide Build Expiration (Expire Build) │
│ PATCH /v1/builds/{id} with attributes: { "expired": true } │
│ Irreversible account-wide shutdown. Halts execution immediately on ALL tester devices. │
│ │
│ 5. Natural 90-Day Build Expiration │
│ Automated server-side expiration enforced by Apple's immutable expirationDate clock. │
└─────────────────────────────────────────────────────────────────────────────────────────────┘
Apple API & FlightDeck Capabilities for Early Expiration
When a build must be terminated early:
- Apple REST API Endpoint: Apple exposes
PATCH /v1/builds/{id}with request bodyBuildUpdateRequest, settingdata.attributes.expired = true. - FlightDeck Semantic Tools: FlightDeck provides dedicated semantic tools for group associations (
build_add_to_beta_groupandbuild_remove_from_beta_group), but does not expose a standalone semantic build expiration tool (there is no build_expire tool). Associating or removing a build from a beta group never changes Apple's build expiration attribute. - Raw Operation Staging: While FlightDeck's low-level dispatcher (
flightdeck_execute_operationtargeting operationbuilds_updateInstance) supports the underlying Apple schema, mutating build states requires enabling thebuildscapability in read-write mode and completing strict Approval Center verification. - Authoritative Manual Execution: Because early expiration is an irreversible, account-wide operation that invalidates the build for every internal and external tester simultaneously, Apple and FlightDeck recommend executing early expiration directly in the App Store Connect web portal: 1. In App Store Connect, go to TestFlight > iOS Builds > [Build Number]. 2. Click the More (...) menu in the top right. 3. Select Expire Build and confirm the prompt.
- Readback Verification: After expiring a build in the portal, prompt your AI assistant via FlightDeck to call
builds_listorbuild_get. FlightDeck reads back live Apple state and confirms thatexpired == true.
For detailed instructions on early build revocation and blast radius comparison, see our companion guide: How to Expire or Delete a Broken TestFlight Build Immediately.