Overview

Asc TestFlight orchestration helps you manage testers, groups, build distributions, and What to Test notes for beta releases. It streamlines pulling current config, organizing testers, and applying notes across locales, making beta rollouts repeatable and auditable.

How This Skill Works

The skill uses asc commands to export the current TestFlight config, manage beta groups and testers, distribute builds to groups, and create or update What to Test notes. It relies on IDs for deterministic operations and supports pagination for large lists, enabling controlled, traceable beta deployments.

When to Use It

• Export and version-control the current TestFlight configuration with a pull (including builds and testers).
• Create or update beta groups and add or invite testers to prepare a new beta cycle.
• Distribute a specific build to one or more groups and adjust group memberships as testers join/leave.
• Create or update What to Test notes for a build in a given locale to guide testers.
• Handle large groups or tester lists with pagination and prefer IDs for deterministic operations.

Quick Start

1. Step 1: Export current TestFlight config: asc testflight sync pull --app "APP_ID" --output "./testflight.yaml"
2. Step 2: Create a group and add testers: asc testflight beta-groups create --app "APP_ID" --name "Beta Testers"; asc testflight beta-testers add --app "APP_ID" --email "tester@example.com" --group "Beta Testers"
3. Step 3: Distribute a build and set notes: asc builds add-groups --build "BUILD_ID" --group "GROUP_ID"; asc builds test-notes create --build "BUILD_ID" --locale "en-US" --whats-new "Test instructions"

Best Practices

• Keep a version-controlled testflight.yaml by regularly exporting with --include-builds and --include-testers.
• Prefer using IDs for all operations to ensure deterministic results; use the ID resolver when needed.
• Use --paginate when dealing with large groups or tester lists to avoid missing data.
• Organize testers into separate beta groups for different features or cohorts for clearer feedback.
• Document locale-specific What to Test notes and maintain localization consistency across builds.

Example Use Cases

• Export current config with asc testflight sync pull --app "APP_ID" --output "./testflight.yaml", then create a 'Beta Testers' group and add tester@example.com.
• Invite a tester via asc testflight beta-testers invite --app "APP_ID" --email "tester@example.com" and assign to the 'Beta Testers' group.
• Distribute a build to the 'Beta Testers' group using asc builds add-groups --build "BUILD_ID" --group "GROUP_ID".
• Update What to Test notes for a build in en-US with asc builds test-notes create --build "BUILD_ID" --locale "en-US" --whats-new "New features and fixes...".
• For a large tester list, paginate beta-testers list --app "APP_ID" --paginate and use IDs to assign testers to groups.

Frequently Asked Questions