App Store Connect CLI

A fast, lightweight, and scriptable CLI for the App Store Connect API. Automate iOS, macOS, tvOS, and visionOS release workflows from your terminal, IDE, or CI/CD pipeline.

asc skills
Sponsors
Quick Start
Troubleshooting
Support
Wall of Apps
Common Workflows
Commands and Reference
Documentation
Contributing
License

asc skills

Agent Skills for automating asc workflows including builds, TestFlight, metadata sync, submissions, and signing: https://github.com/rorkai/app-store-connect-cli-skills

Quick Start

If you want to confirm the binary works before configuring authentication:

asc version
asc --help

1. Install

# Homebrew (recommended)
brew install asc
Install script (macOS/Linux)
curl -fsSL https://asccli.sh/install | bash

Windows users can download the signed release binaries directly from the GitHub releases page.

For source builds and contributor setup, see CONTRIBUTING.md.

2. Authenticate

asc auth login \
  --name "MyApp" \
  --key-id "ABC123" \
  --issuer-id "DEF456" \
  --private-key /path/to/AuthKey.p8 \
  --network

Generate API keys at: https://appstoreconnect.apple.com/access/integrations/api

If you are running in CI, a headless shell, or a machine where keychain access is not available, use config-backed auth instead:

asc auth login \
  --bypass-keychain \
  --name "MyCIKey" \
  --key-id "ABC123" \
  --issuer-id "DEF456" \
  --private-key /path/to/AuthKey.p8

3. Validate auth

asc auth status --validate
asc auth doctor

4. First command

asc apps list --output table
asc apps list --output json --pretty

Output defaults (TTY-aware)

asc chooses a default --output based on where stdout is connected:

Interactive terminal (TTY): table
Non-interactive output (pipes/files/CI): json

You can still set a global preference:

export ASC_DEFAULT_OUTPUT=markdown

And explicit flags always win:

asc apps list --output json

Stability labels

asc uses visible lifecycle labels so you can judge support expectations before depending on a command in CI or scripts:

No label: stable public CLI contract for normal use
[experimental]: useful, but still evolving; expect sharper edges and faster iteration
DEPRECATED: or deprecation warnings: compatibility path kept during migration, but not the long-term home

Troubleshooting

Homebrew

Refresh Homebrew first: brew update && brew upgrade asc
Check which binary you are running: which asc
Confirm the installed version: asc version
If Homebrew is behind the latest GitHub release, use the install script from https://asccli.sh/install

Authentication

Validate the active profile: asc auth status --validate
Run the auth health check: asc auth doctor
If keychain access is blocked, retry with ASC_BYPASS_KEYCHAIN=1 or re-run asc auth login --bypass-keychain
Use asc auth login --local --bypass-keychain ... when you want repo-local credentials in ./.asc/config.json

Output

asc defaults to table in an interactive terminal and json in pipes, files, and CI
Use an explicit format when scripting or sharing repro steps: --output json, --output table, or --output markdown
Use --pretty with JSON when you want readable output in terminals or bug reports
Set a personal default with ASC_DEFAULT_OUTPUT, but remember --output always wins

Support

Use GitHub Discussions for install help, authentication setup, workflow advice, and "how do I...?" questions
Use GitHub Issues for reproducible bugs and concrete feature requests
See SUPPORT.md for the support policy and bug-report checklist
Before filing an auth or API bug, retry with ASC_BYPASS_KEYCHAIN=1; if it is safe to do so, include redacted output from ASC_DEBUG=api asc ... or asc --api-debug ...

Wall of Apps

See the Wall of Apps →

Want to add yours? asc apps wall submit --app "1234567890" --confirm

The command uses your authenticated gh session to fork the repo and open a pull request that updates docs/wall-of-apps.json. It resolves the public App Store name, URL, and icon from the app ID automatically. For manual entries that are not on the public App Store yet, use --link with --name. Use asc apps wall submit --dry-run to preview the fork, branch, and PR plan before creating anything.

Common Workflows

TestFlight feedback and crashes

asc testflight feedback list --app "123456789" --paginate
asc testflight crashes list --app "123456789" --sort -createdDate --limit 10
asc testflight crashes log --submission-id "SUBMISSION_ID"

Builds and distribution

asc builds upload --app "123456789" --ipa "/path/to/MyApp.ipa"
asc builds list --app "123456789" --output table
asc testflight groups list --app "123456789" --output table

Release (high-level App Store publish flow)

# Optional: preview the staging plan before submission asc release stage --app "123456789" --version "1.2.3" --build "BUILD_ID" --copy-metadata-from "1.2.2" --dry-run Canonical upload + attach + submit command asc publish appstore --app "123456789" --ipa "/path/to/MyApp.ipa" --version "1.2.3" --submit --confirm Monitor status after submission

asc status --app "123456789" --watch

Lower-level submission lifecycle commands (for debugging or partial workflows):

# Canonical readiness check
asc validate --app "123456789" --version "1.2.3"
asc submit status --version-id "VERSION_ID"
asc submit cancel --version-id "VERSION_ID" --confirm

Review status and blockers

asc review status --app "123456789"
asc review doctor --app "123456789"

Metadata and localization

asc localizations list --app "123456789"
asc metadata apply --app "123456789" --version "1.2.3" --dir "./metadata" --dry-run
asc metadata keywords audit --app "123456789" --version "1.2.3" --blocked-terms-file "./blocked-terms.txt"
asc apps info view --app "123456789" --output json --pretty

Use asc metadata keywords audit before sync or apply when you want an ASO-focused review of live keyword metadata across locales. It reports duplicate phrases, repeated terms across locales, overlap with localized app name or subtitle, byte-budget usage, and optional blocked terms from repeated --blocked-term flags or a text file.

Screenshots and media

asc screenshots plan --app "123456789" --version "1.2.3" --review-output-dir "./screenshots/review"
asc screenshots apply --app "123456789" --version "1.2.3" --review-output-dir "./screenshots/review" --confirm
asc screenshots list --version-localization "LOC_ID"
asc video-previews list --app "123456789"

Signing and bundle IDs

asc certificates list
asc profiles list
asc bundle-ids list

Workflow automation

asc workflow validate
asc workflow run --dry-run testflight_beta VERSION:1.2.3

Verified local Xcode -> TestFlight workflow

See docs/WORKFLOWS.md for a copyable .asc/workflow.json and ExportOptions.plist that use asc builds next-build-number, asc xcode archive, asc xcode export, and asc publish testflight --group ... --wait.

asc workflow validate
asc workflow run --dry-run testflight_beta VERSION:1.2.3
asc workflow run testflight_beta VERSION:1.2.3

Xcode Cloud workflows and build runs

# Trigger from a pull request asc xcode-cloud run --workflow-id "WORKFLOW_ID" --pull-request-id "PR_ID" Rerun from an existing build run with a clean build asc xcode-cloud run --source-run-id "BUILD_RUN_ID" --clean Fetch a single build run by ID

asc xcode-cloud build-runs get --id "BUILD_RUN_ID"

Commands and Reference

Use built-in help as the source of truth:

asc --help
asc <command> --help
asc <command> <subcommand> --help

Reference hierarchy:

asc --help: authoritative command and flag surface
docs/COMMANDS.md: generated top-level taxonomy map
asc docs show workflows: curated workflow recipes
asc docs show reference: repo-local quick reference template used by asc init

For full command families, flags, and discovery patterns, see:

docs/COMMANDS.md

Documentation

docs/CI_CD.md - CI/CD integration guides (GitHub Actions, GitLab, Bitrise, CircleCI)
docs/COMMANDS.md - Command families and reference navigation
docs/WORKFLOWS.md - Reusable workflow patterns, including local Xcode to TestFlight
docs/API_NOTES.md - API quirks and behaviors
docs/CONTRIBUTING.md - CLI development and testing notes
docs/TESTING.md - Testing patterns and conventions
docs/openapi/README.md - Offline OpenAPI snapshot + update flow
CONTRIBUTING.md - Contribution guide

Acknowledgements

Local screenshot framing uses Koubou (pinned to 0.18.1) for deterministic device-frame rendering. GitHub: https://github.com/bitomule/koubou

Simulator UI automation for screenshot capture and interactions uses AXe CLI. GitHub: https://github.com/cameroncooke/AXe

Contributing

Contributions are welcome. See CONTRIBUTING.md for details.

License

MIT License - see LICENSE for details.

Star History

_{This project is an independent, unofficial tool and is not affiliated with, endorsed by, or sponsored by Apple Inc. App Store Connect, TestFlight, Xcode Cloud, and Apple are trademarks of Apple Inc., registered in the U.S. and other countries.}

NAME

SYNOPSIS

INFO

DESCRIPTION

README