Skip to main content
Installing and testing on a real iPhone Level: Intermediate 10 min read

How to Retract or Expire a Broken TestFlight Build Immediately

Learn how to immediately expire a broken TestFlight build or retract it from beta testing groups to prevent tester crashes and bug reports.

Published: 2026-11-01 • Last Updated: 2026-11-01 • Author: Kip Lawrence
Key MCP Tools: build_remove_from_beta_group

Distributing a pre-release build through TestFlight allows developers to validate applications on physical devices with real testers. However, an urgent operational challenge arises when a build contains a critical regression: a crash on launch, a database corruption issue, or an unintended security exposure.

In that situation, every minute matters. Developers need to halt new installations and disable broken binaries.

Many developers ask: Can I delete an old or broken build from App Store Connect?

The short answer is no: Apple does not allow deleting processed builds from App Store Connect history. However, Apple provides remediation mechanisms with fundamentally different device-level effects: retracting the build from beta groups (which stops new installations and updates for group members while allowing existing installations to keep running) and expiring the build (which halts execution across all devices that have already installed the build).

This guide explains how build lifecycle management works in TestFlight, details what happens on physical devices under each remediation mechanism, and shows how to compare options, retract builds, or expire builds using conversational AI prompts with FlightDeck.


Why Processed Builds Cannot Be Deleted from Apple

Once an .ipa archive is uploaded and completes Apple's backend processing pipeline (reaching the VALID state), it cannot be deleted through either the App Store Connect web portal or the App Store Connect REST API.

Apple retains every ingested build permanently in its database for several reasons:

  1. Auditability and Regulatory Traceability: App Store Connect maintains an immutable audit trail of every executable artifact submitted under your Developer Program membership.
  2. Release History Integrity: If a build was previously linked to an App Store version, submitted for review, or delivered to external testers, deleting it would compromise compliance records.
  3. Symbolication and Diagnostics: Crash reports submitted by historical testers require the uploaded symbol maps (dSYM packages) associated with that specific build UUID.

Once uploaded and processed, a build record remains in Apple's historical database forever. Remediation requires group retraction, build expiration, or distributing a replacement build—never deletion.


The Core Remediation Mechanisms and Device Consequences

When managing a defective build, developers must distinguish among distinct remediation actions and their exact effects:

TEXT
┌──────────────────────────────────────────────────────────────────────────┐
│                   DEFECTIVE BUILD IN TESTFLIGHT                          │
└────────────────────────────────────┬─────────────────────────────────────┘
                                     │
      ┌──────────────────────────────┼──────────────────────────────┐
      ▼                              ▼                              ▼
[1. Retract from Beta Group]   [2. Disable Public Link]       [3. Expire Build]
• Halts new installs for group • Halts new tester signups     • Halts launches everywhere
• Existing installs STILL RUN  • Existing testers keep build  • TestFlight modal blocks app
• Surgical group control       • Link-level control           • Account-wide shutdown

1. Removing a Build from a Beta Group (Retraction)

  • What it does: Decouples the build from a specific beta testing group (e.g., External Public Testers) using FlightDeck's build_remove_from_beta_group.
  • On physical devices: Testers in that group can no longer install or update to the build in the TestFlight iOS app. However, testers who already downloaded the build onto their physical devices can continue launching and using it until the standard 90-day testing window lapses or the build is expired. Removing a build from a group does not stop local execution on devices where it is already installed.
  • FlightDeck Support: Fully supported via natural-language prompts.
  • What it does: Disables the public TestFlight join URL in beta group settings.
  • On physical devices: Prevents prospective testers from joining the beta group via Public Invitation Links. Testers who already joined retain their current access.

3. Expiring a TestFlight Build (Account-Wide Shutdown)

  • What it does: Sets the build's expired attribute to true across your entire App Store Connect account.
  • On physical devices: When any tester attempts to tap and launch the application, TestFlight's on-device runtime intercepts the launch, presents an alert dialog informing the user that the beta has expired, and halts execution.
  • Irreversibility: Once a build is marked expired, Apple does not allow it to be re-activated. To resume testing, you must upload a new build with an incremented build counter.
  • FlightDeck Support: Can be staged via AI using FlightDeck's universal operation dispatcher, or performed manually in the App Store Connect web portal.

4. Normal 90-Day Build Expiration

  • Every TestFlight build automatically expires 90 days after its upload date. Manual expiration simply brings that deadline forward to the present moment.

5. What Happens to the Installed App Icon (No Remote Wipe)

  • Critical platform reality: Apple provides no remote wipe or silent uninstall mechanism. TestFlight does not remove or erase the application icon from the tester's home screen.
  • When an expired app is tapped, TestFlight displays an expiration alert, but the icon remains on the device until the tester manually deletes it or installs a replacement update.

6. Public App Store Releases (Unaffected)

  • Expiring or retracting a TestFlight build has zero impact on active production versions on the public App Store.

Retraction vs. Expiration: Feature Comparison

Action Can New Testers Install? Can Existing Installs Launch? Can Internal QA Keep Testing? Reversible? Supported in FlightDeck?
Remove from Beta Group No (group loses access) Yes (runs until 90-day expiry) Yes (other groups retain access) Yes (can re-add) Yes (Prompt-driven with approval)
Disable Public Link No (no new joiners) Yes (existing testers keep access) Yes (internal groups unaffected) Yes (re-enable link) Manual / Portal
Expire Build No (hidden everywhere) No (TestFlight modal blocks launch) No (expired account-wide) No (requires new build) Yes (AI-staged or Portal)
Delete Build N/A N/A N/A N/A Unsupported by Apple

Triage and Comparison: Asking Your AI Coding Assistant

When an issue is discovered, prompt your AI coding assistant to inspect the current state and compare options before taking any mutating action.

Primary Triage Prompt

Copy and paste this prompt into your connected AI coding assistant:

TEXT
Find the latest TestFlight build for [Your App Name]. I discovered a serious issue and want to stop further testing. Show me which groups currently have access, explain the available retraction or expiration options and their consequences, and do not make changes until I approve the safest option.

Your assistant connects to FlightDeck, inspects the active builds and beta group assignments, and reports:

  • The active build number and current processing state.
  • Which beta groups (internal and external) currently have access to the build.
  • A comparison of whether to retract the build from specific groups or expire it account-wide.

Executing Remediation with Human-in-the-Loop Governance

Option A: Retracting a Build from a Specific Beta Group

If you only want to stop external testers while keeping internal QA access:

TEXT
Retract build [e.g., 88] from the [e.g., External Public Testers] group for [Your App Name] using FlightDeck.

Because removing a build from a beta group alters live tester distribution, FlightDeck treats this as a remote mutating operation under its Human-in-the-Loop Governance model and stages it for your review. FlightDeck Desktop displays an Approval Center sheet:

Illustrative representation of the FlightDeck Approval Center sheet:

TEXT
┌──────────────────────────────────────────────────────────────┐
│ FlightDeck Desktop — Operation Approval Request             │
├──────────────────────────────────────────────────────────────┤
│ Operation:   Remove Build from Beta Group                   │
│ Target App:  [Your App Name] (App ID: 6812899314)           │
│ Build:       Version 1.4.2 (Build 88)                        │
│ Beta Group:  External Public Testers (ID: 4a2b3c4d-...)     │
│ Action:      DELETE /v1/betaGroups/{id}/relationships/builds│
│ Impact:      Testers in this group can no longer install    │
│              build 88. Existing on-device installs can run  │
│              until the build is expired.                    │
├──────────────────────────────────────────────────────────────┤
│ [Reject Proposal]                        [Approve & Execute] │
└──────────────────────────────────────────────────────────────┘

Review the parameters in FlightDeck Desktop and click Approve & Execute. FlightDeck dispatches the deletion request to Apple's API and severs the group relationship.

Option B: Expiring a Build Account-Wide via FlightDeck

If the build contains an urgent data-loss bug and must be halted across all devices, prompt your assistant to stage an account-wide expiration:

TEXT
Expire build [e.g., 88] for [Your App Name] account-wide in App Store Connect using FlightDeck. Stage the proposal for my approval and explain what testers will experience.

Behind the scenes, FlightDeck's universal operation dispatcher formats the Apple API update (PATCH /v1/builds/{id} with expired: true) and presents it in FlightDeck Desktop:

Illustrative representation of the FlightDeck Approval Center sheet:

TEXT
┌──────────────────────────────────────────────────────────────┐
│ FlightDeck Desktop — Operation Approval Request             │
├──────────────────────────────────────────────────────────────┤
│ Operation:   Expire TestFlight Build                        │
│ Target App:  [Your App Name] (App ID: 6812899314)           │
│ Build:       Version 1.4.2 (Build 88)                        │
│ Action:      PATCH /v1/builds/{id} (expired: true)          │
│ Impact:      IRREVERSIBLE. Halts app launches on all        │
│              tester devices account-wide.                   │
├──────────────────────────────────────────────────────────────┤
│ [Reject Proposal]                        [Approve & Execute] │
└──────────────────────────────────────────────────────────────┘

Once approved, the build is immediately marked expired on Apple's servers.

Option C: Expiring via the App Store Connect Web Portal

If you prefer to perform account-wide expiration directly in Apple's portal:

  1. Sign in to App Store Connect.
  2. Select Apps and click your application.
  3. Click the TestFlight tab in the top navigation bar.
  4. In the left sidebar, click iOS under the Builds section.
  5. Click the version and build number of the defective build (e.g., 1.4.2 (88)).
  6. In the upper-right corner of the build details screen, click the Expire Build button.
  7. Confirm the expiration warning.

Verification and Read-Back Prompt

To confirm the new state of the build and ensure distribution has been restricted:

TEXT
Verify the status of build [e.g., 88] for [Your App Name] in App Store Connect. Confirm whether it is expired, and check which builds remain available to testers in our beta groups.

Your assistant will query App Store Connect, read back the current build attributes, and confirm that the build is either detached from the target group or marked expired account-wide.


When an urgent defect is detected in a live TestFlight build:

  1. Triage and Halt Installs: Ask your AI assistant to compare retraction vs expiration. For public groups, immediately retract the build using FlightDeck.
  2. Evaluate Severity for Existing Installs: - If the bug is cosmetic or non-destructive, leave the build running for existing testers while preparing a hotfix. - If the bug corrupts user databases or compromises authentication, expire the build immediately.
  3. Increment Build Counter and Rebuild: - Resolve the bug in your source code. - Increment CFBundleVersion (e.g., from 88 to 89). - Package a new .ipa archive.
  4. Deliver and Distribute Hotfix: - Ask your assistant to inspect and stage the upload of build 89. - Once Apple processing completes, assign the new build to your beta groups. Existing testers will receive an update notification in TestFlight.

Connect Your AI Agent to App Store Connect

FlightDeck runs locally on your Mac, keeping private keys secure in your macOS Keychain and executing mutations only after your explicit approval.

Download FlightDeck on Mac App Store