asc-testflight-orchestration

Automate TestFlight beta distribution by using the ASC CLI to export project configuration, create tester groups, add testers, and distribute builds to selected groups. This workflow manages the entire beta rollout deterministically using group and tester IDs.

To manage TestFlight testers and groups, you need the ASC CLI, an APP_ID, and appropriate App Store Connect permissions. These inputs enable deterministic operations for adding, inviting, and organizing testers by group.

Add localized What to Test notes for a TestFlight beta rollout through the ASC CLI to capture and maintain clear beta testing instructions across locales. This ensures testers receive context-specific instructions for the distributed build.

Yes, you can remove testers from a TestFlight group after distributing a build. The workflow supports managing tester groups and individual testers, including adding, inviting, organizing, and removing testers as needed during the beta lifecycle.

The best way to keep TestFlight builds and testers aligned is exporting current project configuration and using deterministic group and tester IDs. This ensures builds are distributed to the correct selected groups without mismatch.