App-Store-Connect-CLI
Fast, scriptable CLI for the App Store Connect API. Automate TestFlight, builds, submissions, signing, analytics, screenshots, subscriptions, and more
Runs with mockssource: GitHubhomepageGoMITcommit 6d4943bd8830
Go, MIT licensed. The project labels itself: app store connect, apple, automation, cicd, cli, command line tool, developer tools and devops.
App-Store-Connect-CLI runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The asc CLI binary builds and runs from source using Go 1.26.6 downloaded into the container. All 107 test packages pass on an isolated worktree with ASC_BYPASS_KEYCHAIN=1. The binary's --help, --version, and auth doctor commands all produce correct output. No real App Store Connect credentials are configured, so all verification was offline against mock HTTP servers.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- 15 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- go test ./... exited 0 with 107 packages marked ok; ./asc --help printed 132 lines; ./asc version printed 'dev (commit: unknown, date: unknown)'; ./asc auth doctor reported 0 errors
- Model tokens used
- 104,111
- Exact commit tested
- 6d4943bd8830
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
1789554421 exec /bin/sh -lc 'export GOROOT=/tmp/go && export PATH=$GOROOT/bin:$PATH && cd /work/repo && ./asc versi… succeeded in 0ms: dev (commit: unknown, date: unknown) 132 2. Remove orphaned temp key files from your temp directory Found 2 warning(s) and 0 error(s). All done. Here's the final report: tokens used 104,111 All done. Here's the final report:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 15 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.04 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.07 |
Topics (from GitHub)
app-store-connectappleautomationcicdclicommand-line-tooldeveloper-toolsdevopsgogolangiosmacosswifttestflightxcode
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/app-store-connect-cli)Questions
- Does App-Store-Connect-CLI run?
- App-Store-Connect-CLI runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test App-Store-Connect-CLI?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6d4943bd8830. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test App-Store-Connect-CLI?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does App-Store-Connect-CLI take to install?
- 15 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does App-Store-Connect-CLI need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing App-Store-Connect-CLI?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for App-Store-Connect-CLI?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.