asc-release-flow

• Ensure credentials are set (asc auth login or ASC_* env vars).
• Use a new build number for each upload.
• Prefer ASC_APP_ID or pass --app explicitly.
• Build must have encryption compliance resolved (see asc-submission-health skill).

Preferred end-to-end commands

• TestFlight:

- asc publish testflight --app --ipa --group [,]

- Optional: --wait, --notify, --platform, --poll-interval, --timeout

• App Store:

- asc publish appstore --app --ipa --version

- Optional: --wait, --submit --confirm, --platform, --poll-interval, --timeout

Manual sequence (when you need more control)

1. Upload the build:

- asc builds upload --app --ipa

1. Find the build ID if needed:

- asc builds latest --app [--version ] [--platform ]

1. TestFlight distribution:

- asc builds add-groups --build --group [,]

1. App Store attach + submit:

- asc versions attach-build --version-id --build

- asc submit create --app --version --build --confirm

1. Check or cancel submission:

- asc submit status --id or --version-id

- asc submit cancel --id --confirm

macOS apps are distributed as .pkg files, not .ipa.

Build and Export

See asc-xcode-build skill for full build/archive/export workflow.

Upload PKG

Use xcrun altool (asc doesn't yet support .pkg uploads directly):

```bash

# Ensure API key is in ~/.appstoreconnect/private_keys/

xcrun altool --upload-app \

-f "/path/to/YourApp.pkg" \

--type macos \

--apiKey "$ASC_KEY_ID" \

--apiIssuer "$ASC_ISSUER_ID"

```

Attach and Submit

Same as iOS, but use --platform MAC_OS:

```bash

# Wait for build to process

asc builds list --app --platform MAC_OS --limit 5

# Attach to version

asc versions attach-build --version-id --build

# Create submission

asc review submissions-create --app --platform MAC_OS

# Add version item

asc review items-add \

--submission \

--item-type appStoreVersions \

--item-id

# Submit

asc review submissions-submit --id --confirm

```

Same as iOS flow, use appropriate --platform:

• VISION_OS
• TV_OS

When releasing the same version across platforms:

1. Upload each platform's build separately
2. Create version for each platform if not exists
3. Attach builds to respective versions
4. Submit each platform separately (or together via reviewSubmissions API)

Before submitting, verify:

• [ ] Build status is VALID (not processing)
• [ ] Encryption compliance resolved
• [ ] Content rights declaration set
• [ ] Copyright field populated
• [ ] All localizations complete
• [ ] Screenshots present

See asc-submission-health skill for detailed preflight checks.

• Always use --help to verify flags for the exact command.
• Use --output table / --output markdown for human-readable output; default is JSON.
• macOS builds require ITSAppUsesNonExemptEncryption in Info.plist to avoid encryption issues.