Overview: Distributing Pre-Release Builds via Public Links
A TestFlight Public Link allows developers to distribute pre-release iOS, iPadOS, and macOS builds to a broad audience without collecting individual email addresses in advance. When enabled, Apple generates a unique URL (https://testflight.apple.com/join/...) that anyone can open on an Apple device to join your beta program.
Public links are ideal for community playtests, open betas, social media recruitment, and developer communities. However, public links introduce strict operational considerations: they are restricted to external beta groups, require mandatory Apple Beta App Review for the distributed build, and must be capped to prevent unmonitored quota exhaustion. Furthermore, public links do not bypass device hardware requirements, minimum OS versions, or regional storefront availability configured for your application.
Using FlightDeck's Model Context Protocol (MCP) server, your AI coding assistant can inspect your beta groups, verify build eligibility, configure public links with explicit tester quotas, and retrieve the live enrollment URL.
This guide explains how TestFlight public links operate, the prerequisite review gates, capacity mechanics, and how to manage links safely through natural-language prompts.
1. Public Link Fundamentals: Eligibility and Requirements
Before enabling a public link, your app and testing group must satisfy Apple's architectural requirements:
+-----------------------------------------------------------------------------------+
| PUBLIC LINK DISTRIBUTION GATES |
+-----------------------------------------------------------------------------------+
| |
| 1. Target Group Must Be EXTERNAL (isInternalGroup: false) |
| - Internal groups (team members only) cannot have public links. |
| - Apple rejects public links on internal groups with HTTP 400 Bad Request. |
| |
| 2. Target Build Must Pass BETA APP REVIEW |
| - Uploading a build and reaching VALID processing state is NOT enough. |
| - The first build of any marketing version (e.g. 1.0.0, 1.1.0) must be |
| submitted to Apple and approved for external testing. |
| |
| 3. Export Compliance Must Be CLEARED |
| - ITSAppUsesNonExemptEncryption declared or questionnaire attested. |
| |
| 4. Configurable Quota Limit (1 to 10,000 Testers) |
| - Protects your 10,000-tester account cap from sudden depletion. |
| |
| 5. Device & Regional Availability Apply |
| - Testers must meet minimum OS requirements and reside in supported regions.|
+-----------------------------------------------------------------------------------+
Configured vs. Installable: When you enable a public link on an external group, Apple generates the public join URL immediately. However, testers who visit the link cannot install the app until Apple approves the assigned build for external testing. If users open an active link before Beta App Review approval completes, TestFlight displays a notice stating that the beta is not currently accepting testers or that no builds are available.
2. Quota Mechanics and Link Lifecycle
Apple provides granular control over how public links behave once shared with the public:
| Event / State | Apple Behavior | Impact on Existing Testers | Impact on New Testers |
|---|---|---|---|
| Active Link (Under Limit) | URL opens the TestFlight app and displays your app icon, version, and "What to Test" notes. | Normal access; receive automatic updates for newly assigned builds. | Can tap Accept and Install to join the beta immediately. |
Capacity Reached (publicLinkLimit) | Apple detects enrolled tester count equals the configured limit. | No impact. Already-enrolled testers retain installed builds and receive updates. | New visitors see a message: "This beta is full." Tapping Accept is blocked until the limit is raised or existing testers leave. |
| Public Link Disabled | URL is deactivated immediately on Apple's edge servers. | Existing testers remain enrolled! They retain their current build and can continue testing until manually removed or the build expires. | New visitors see: "This beta is no longer accepting new testers." |
| Public Link Re-Enabled | Apple re-activates the public link (generating a URL or restoring access). | Existing testers continue testing without interruption. | New participants can join up to the configured tester limit. |
| Beta Group Deleted | The group container is purged. The public link URL is permanently invalidated. | Access to builds assigned strictly through this group is revoked. Testers remain in your app/organization directory. | Link returns HTTP 404 / inactive. |
Safety Invariant — Disabling a Link Does Not Kick Testers: Disabling a public link merely stops new participants from joining. It does not revoke access from users who already accepted the invitation. To remove existing testers who joined via the public link, you must remove them from the group or delete the group container.
3. FlightDeck MCP Implementation Realities
FlightDeck provides both high-level semantic tools and low-level staged operations for public links:
- Creating a New Group with Public Link: The semantic tool
beta_group_createnatively acceptspublicLinkEnabled: trueandpublicLinkLimit: <number>. This allows creating a new external beta cohort and enabling the public link in a single staged proposal. - Updating an Existing Group's Public Link: For groups that already exist, updating public link status or adjusting tester limits without deleting the group is performed via
flightdeck_operation_stageusing canonical operationbetaGroups_updateInstance, or toggled directly in the App Store Connect web portal. - Retrieving the Live Link: FlightDeck's
beta_groups_listtool parses Apple's response attributes and returns the livepublicLinkURL (https://testflight.apple.com/join/...) for all groups where the link is active.
4. Step-by-Step Prompt Workflows
4.1 Inspecting Public Link Status
Instruct your assistant to check whether your existing groups have public links enabled and how close they are to their configured limits.
Using FlightDeck, check whether [App Name] has an external TestFlight group eligible for a public invitation link. Explain any prerequisites, report which builds are assigned, and show current tester counts and link status. Do not stage or execute any changes. What the Assistant Does:
- Calls
apps_listto resolve yourappId. - Calls
beta_groups_list(appId: "<appId>"). - Filters for groups where
isInternalGroup: false. - Inspects
publicLinkEnabled,publicLink, andpublicLinkLimit. - Calls
build_beta_details_geton assigned builds to confirm whether they are approved for external distribution.
4.2 Creating an External Group with a Public Link via AI
To launch an open community beta, instruct your assistant to create a dedicated external group with an explicit tester ceiling.
Help me create an external TestFlight group called "Public Community" for [App Name]. Enable a public invitation link with a maximum capacity limit of 250 testers. Do not enable access to all builds automatically. Show me the proposed configuration before staging it for approval in FlightDeck. Execution Flow:
- Verification: The assistant confirms "Public Community" does not already exist.
- Staging: The assistant calls
beta_group_createwith the specified parameters. - Desktop Approval Gate: FlightDeck intercepts the mutation and returns
status: "HUMAN_APPROVAL_REQUIRED". Your assistant prompts: > "I have staged the creation of 'Public Community' with a 250-tester public link limit. Please authorize this proposal in the FlightDeck Desktop Approval Center." - Execution & Readback: You click Approve in the FlightDeck Desktop UI. The assistant completes the mutation and calls
beta_groups_listto fetch the real Apple-generated join link.
4.3 Attaching an Approved Build to the Public Link Cohort
Remember that a public link requires an assigned build to be installable:
Check recent builds for [App Name] using FlightDeck. Verify that the latest build has completed processing and is eligible for external testing. Once confirmed, stage an association connecting that build to our "Public Community" group. The assistant verifies that processingState == "VALID" and that externalBetaState indicates approval. It then stages build_add_to_beta_group for your approval in Desktop.
4.4 Disabling a Public Link When Recruitment Ends
When your tester quota is filled or you want to freeze recruitment, disable the public link to stop new signups while preserving your existing cohort.
Option A: Via AI Assistant (Staged Mutation)
Disable the public invitation link for the "Public Community" group of [App Name]. Confirm that existing testers will not be removed, and stage the update for my approval in FlightDeck. The assistant stages betaGroups_updateInstance targeting the group's Apple ID with publicLinkEnabled: false. You approve the mutation in the FlightDeck Desktop Approval Center.
Option B: Via App Store Connect Web Portal (Manual Steps)
- Sign in to App Store Connect and navigate to Apps $\rightarrow$ [Your App] $\rightarrow$ TestFlight.
- Under External Groups, select your group (e.g. "Public Community").
- Select the Public Link tab.
- Click Disable Public Link.
- Confirm the deactivation dialog. The URL is deactivated immediately.
5. Summary of Best Practices
- Always Set a Limit: Never enable a public link without specifying
publicLinkLimit. Without a limit, viral exposure on social media or forums can consume your entire 10,000 external tester quota in hours. - Verify Beta App Review First: Ensure your target build has been reviewed and approved by Apple before sharing the public link; otherwise, testers will experience an alert saying the beta is not available.
- Never Fabricate URLs: Real public link tokens are generated by Apple upon creation. FlightDeck reads the genuine URL via
beta_groups_list. Never guess or construct synthetic join links. - Prune Inactive Testers: If you reach your 10,000 account limit, use FlightDeck or the web portal to remove testers who haven't launched the app in over 30 days to free up quota.