Asc Testflight Orchestration

by rorkai9c7e769f09a1No license1K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 3 days ago

Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.

Instructions onlyDevOps & Cloud
AI-generated overview

Orchestrates TestFlight beta distribution, tester groups, and What to Test notes through the asc CLI.

What it does
Provides command sequences for exporting TestFlight configuration, creating and listing tester groups, adding or inviting testers, and distributing builds to groups. It also covers inspecting a build's groups, uploading an IPA without distribution, and creating or updating What to Test notes per locale. The output is executed CLI operations and exported configuration files rather than generated documents.
When to use it
Use it when rolling out or managing TestFlight betas: organizing testers and groups, attaching builds to groups, uploading a build for processing only, or writing localized What to Test notes.
Requirements
The asc CLI must be installed and authenticated with access to the target App Store Connect app. Requires app, build, group, and localization identifiers, an IPA or local Xcode build for uploads, and network access. Ships no scripts; instructions only.

asc TestFlight orchestration

Use this skill when managing TestFlight testers, groups, and build distribution.

Export current config

  • asc testflight config export --app "APP_ID" --output "./testflight.yaml"
  • Include builds/testers:
    • asc testflight config export --app "APP_ID" --output "./testflight.yaml" --include-builds --include-testers

Manage groups and testers

  • Groups:
    • asc testflight groups list --app "APP_ID" --paginate
    • asc testflight groups create --app "APP_ID" --name "Beta Testers"
  • Testers:
    • asc testflight testers list --app "APP_ID" --paginate
    • asc testflight testers add --app "APP_ID" --email "[email protected]" --group "Beta Testers"
    • asc testflight testers invite --app "APP_ID" --email "[email protected]"

Distribute builds

  • asc builds add-groups --build-id "BUILD_ID" --group "GROUP_ID"
  • Remove from group:
    • asc builds remove-groups --build-id "BUILD_ID" --group "GROUP_ID" --confirm

Inspect a build's groups

  • asc testflight groups list --build-id "BUILD_ID" --output table
  • The build lookup is experimental. It resolves the app, paginates the app's groups, and includes groups with all-build access.

Upload without distribution

  • asc publish testflight --app "APP_ID" --ipa "./app.ipa" --upload-only --output json
  • Add --wait when the next step needs a processed build.
  • Upload-only requires a new IPA or local Xcode build. Do not combine it with an existing --build-id, groups, tester notifications, test notes, or beta-review submission. --build-number is allowed as upload metadata, but it cannot be the only build input.

What to Test notes

  • asc builds test-notes create --build-id "BUILD_ID" --locale "en-US" --whats-new "Test instructions"
  • asc builds test-notes update --localization-id "LOCALIZATION_ID" --whats-new "Updated notes"

Notes

  • Use --paginate on large groups/tester lists.
  • Prefer IDs for deterministic operations; use the ID resolver skill when needed.

Source and attribution

Source:rorkai/app-store-connect-cli-skillsinskills/asc-testflight-orchestrationat commit9c7e769

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal