Skip to main content

​
publish

High-level publish workflows for TestFlight and App Store
The publish command is the high-level publishing surface for TestFlight and the canonical App Store upload + submit flow.

​
Usage

​
Canonical paths

Use these top-level workflows deliberately:
  • asc publish testflight - canonical high-level TestFlight publish path
  • asc publish appstore - canonical high-level App Store publish path
  • asc release stage - prepare an App Store version without submitting it
In 1.0, the deprecated asc release run path was removed. Use Migrate to 1.0 if you still have older automation that expects a single deprecated release command.

​
Workflows

​
TestFlight workflow

Upload and distribute to TestFlight:
This workflow:
  1. Uploads the build
  2. Waits for processing
  3. Distributes to specified beta groups

​
App Store workflow

Ship to the App Store with the canonical publish command:
This workflow:
  1. Uploads the IPA
  2. Finds or creates the matching App Store version
  3. Attaches the processed build
  4. Optionally submits for review with --submit
  5. Prints the resulting build/version/submission identifiers

​
TestFlight flags

​
string
required
App ID for the build
​
string
required
Path to IPA file
​
string
Comma-separated beta group names or IDsExample: "External Testers,Internal Team"
​
boolean
Wait for build processing to completeDefault: true

​
1.0 migration note

If older automation still invokes the deprecated asc release run, replace it with asc publish appstore --submit --confirm for end-to-end shipping or asc release stage for pre-submit preparation work.

​
Example workflows

​
Publish to TestFlight

​
Publish to App Store

​
CI/CD integration

​
Output

​
Error handling

If any step fails, the workflow stops and reports the error:
You can retry individual steps using the lower-level commands:

Builds command

Manage builds and uploads

Release command

Pre-submit release staging

Automation guide

Workflow automation patterns