app-store-connect-cli

Automate App Store Connect workflows including TestFlight, builds, submissions, and metadata via the asc CLI.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/devtools-skills --skill app-store-connect-cli-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: app-store-connect-cli
Source: https://github.com/reason-machines/devtools-skills/tree/main/skills/app-store-connect-cli
Command: npx skills add https://github.com/reason-machines/devtools-skills --skill app-store-connect-cli-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing App Store Connect tasks like uploading builds, publishing to TestFlight, submitting apps for review, and syncing metadata requires repetitive manual work in Apple's web portal, which does not fit CI/CD pipelines or scripted automation. ## Core Features & Use Cases - Build and TestFlight Automation: Upload IPAs, publish builds to TestFlight groups, collect tester feedback, and download crash logs from the command line. - App Store Submission Pipeline: Stage releases, validate readiness, submit versions for review, and monitor status with watch mode. - Metadata and Screenshot Management: Initialize, apply, audit, and sync localized metadata and screenshots across app versions. - Use Case: In a GitHub Actions workflow on macOS, authenticate with an App Store Connect API key, run a defined workflow to archive and export an Xcode project, publish the IPA to TestFlight, then validate and submit version 1.2.3 to the App Store while monitoring review status. ## Quick Start Install the asc CLI with Homebrew, log in with your App Store Connect API key, then ask the agent to upload your IPA and publish it to a TestFlight group.

Frequently Asked Questions about app-store-connect-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upload a build to TestFlight from the command line?▼

Use the asc CLI publish command: asc publish testflight with your app ID, IPA path, tester group, and the --wait flag. It uploads the build and distributes it to the specified TestFlight group in one step.

How to automate App Store submission in CI/CD?▼

Authenticate with asc auth login using --bypass-keychain and your API key stored in CI secrets, then run asc publish appstore with --submit and --confirm. Example pipelines for GitHub Actions, GitLab CI, and CircleCI are provided.

Does asc work in headless CI environments without keychain access?▼

Yes, asc supports headless environments via the --bypass-keychain flag on auth login or the ASC_BYPASS_KEYCHAIN=1 environment variable. Credentials are read from flags or environment variables instead of the macOS keychain.

Can I sync App Store metadata between app versions?▼

Yes, asc metadata sync copies metadata from one version to another per locale, and asc metadata apply pushes metadata from a local directory structure. Use --dry-run first to preview changes before applying them.

Why does asc authentication fail in CI pipelines?▼

Failures usually come from keychain restrictions or incorrect API credentials. Run asc auth doctor for diagnostics, verify the key ID, issuer ID, and .p8 file, and retry with ASC_BYPASS_KEYCHAIN=1 to skip keychain storage.

What output formats does the asc CLI support for scripting?▼

asc outputs table format in interactive terminals and JSON in non-TTY contexts automatically. You can force formats with --output table, json, or markdown, and pipe JSON to jq for programmatic parsing.