App-Store-Connect-CLI
App Store Connect CLI is a Go-based command-line tool that automates iOS/macOS app distribution workflows including TestFlight uploads, build management, and App Store submissions via the App Store Connect API. It is designed for CI/CD integration with JSON output and no interactive prompts.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | rorkai/App-Store-Connect-CLI |
| Owner | rorkai |
| Primary language | Go |
| License | MIT — OSI-approved |
| Stars | 5k |
| Forks | 440 |
| Open issues | 0 |
| Latest release | 2.6.0 (2026-07-06) |
| Last updated | 2026-07-08 |
| Source | https://github.com/rorkai/App-Store-Connect-CLI |
What App-Store-Connect-CLI is
Written in Go, this tool wraps the App Store Connect REST API with a scriptable CLI interface supporting multiple output formats (JSON, table, markdown). It handles authentication via API keys stored in system keychain or config files, includes telemetry (opt-out), and provides lifecycle-labeled commands indicating stability.
Get the App-Store-Connect-CLI source
Clone the repository and explore it locally.
git clone https://github.com/rorkai/App-Store-Connect-CLI.gitcd App-Store-Connect-CLI# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Authentication requires App Store Connect API key (p8 file) and issuer ID; store securely in CI secrets or keychain, never commit to repositories.
- Default telemetry collection includes pseudonymous usage data and installation ID; review `asc telemetry status` immediately and disable if required by policy.
- Output format defaults to table in TTY and JSON in pipes/CI; explicitly set `--output` in scripts to avoid ambiguity across environments.
- Go version 1.26+ required; verify compatibility in build environments before adopting.
- Validation commands (`asc auth status --validate`, `asc auth doctor`) should be integrated into CI setup and pre-deployment checks.
When to avoid it — and what to weigh
- Windows Primary Development Environment — While WinGet binaries are available, the tool is optimized for macOS/Linux and full support for Windows is pending WinGet package acceptance. Current Windows users must download signed binaries manually.
- Graphical UI Preference Required — This is CLI-only with no GUI. Teams requiring visual dashboards or point-and-click workflows should remain on the App Store Connect web portal.
- Non-Apple Ecosystem Distribution — This tool is Apple-specific (iOS, macOS, tvOS, visionOS). It provides no value for Android, web, or cross-platform distribution workflows.
- Offline or Air-Gapped Deployments — The tool requires internet access to App Store Connect API and sends telemetry by default (though opt-out is available). It is unsuitable for fully isolated environments.
License & commercial use
MIT License permits commercial use, modification, and distribution with no royalties. Requires retention of license notice in redistributed code or binaries.
MIT is a permissive OSI-approved license. Commercial use of the tool itself (e.g., bundling in a commercial CD tool) is permitted provided the MIT license and attribution are retained. Use of the tool by commercial entities for internal automation does not require any license action. No warranty is provided.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Strong |
| Assessment confidence | High |
API keys (p8 files) are sensitive credentials; the tool offers keychain storage (default) or config file bypass for CI. Telemetry is enabled by default but does not collect credentials, API responses, or file paths. Validate authentication with `asc auth doctor` before production use. No public advisories or CVEs mentioned in provided data; security posture requires independent review.
Alternatives to consider
Apple Xcode Cloud & App Store Connect Web Portal
Official, graphical, no CLI setup required. Lacks scriptability and batch automation; suitable for teams preferring UI workflows.
Fastlane (Ruby-based iOS automation)
Mature ecosystem with plugins for TestFlight, screenshots, signing. Heavier dependency footprint (Ruby); asc is faster and lighter in Go.
Custom REST API client (curl, SDK wrappers)
Maximum control and minimal dependencies. Requires manual API contract management and error handling; asc abstracts these concerns.
Build on App-Store-Connect-CLI with DEV.co software developers
Replace manual App Store Connect workflows with a single scriptable CLI. Integrate with GitHub Actions, GitLab CI, or local automation in minutes. Install via Homebrew or download today.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
App-Store-Connect-CLI FAQ
Is my API key safe with this tool?
Can I use this in GitHub Actions or GitLab CI?
What does the telemetry collect?
Why is my authentication failing?
Software developers & web developers for hire
From first prototype to production, DEV.co delivers software development services around tools like App-Store-Connect-CLI. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source devops and beyond.
Streamline Your iOS Release Pipeline
Replace manual App Store Connect workflows with a single scriptable CLI. Integrate with GitHub Actions, GitLab CI, or local automation in minutes. Install via Homebrew or download today.