App Store Release

Read-only inventory: versions, builds, localizations, screenshot sets, pricing and subscriptions. Use it to answer questions about current state; use asc_readiness_report to decide what to do.

Write the listing to App Store Connect: build attach, metadata, pricing, content rights, age rating, category, review info, screenshots and subscription. Idempotent — re-running when everything already matches sends nothing. Does not submit for review.

Create any missing subscription plans and one-time purchases from the config, then write their localizations, prices, introductory offers and App Review screenshots, so they leave MISSING_METADATA. Once READY_TO_SUBMIT, asc_submit_for_review sends them with the app version — the app's first subscription and first in-app purchase included, with the website's clicks as the fallback.

Read the app's customer reviews, newest first: rating, title, text, territory, and any published reply. Filter to what needs attention — low ratings, unanswered ones — and optionally include Apple's own summary of recent reviews. Read-only. To answer one, draft a reply, show it to the human, and only after they approve it call asc_reply_to_review.

Issue a new distribution certificate and provisioning profile and write them to disk. Apple caps an account at three distribution certificates and this consumes one. Disabled unless the operator sets APPSTORE_RELEASE_ALLOW_LOCAL_WRITES=1.

List the apps this API key can see, with their numeric ids and bundle ids. Every other tool needs the numeric id, and it is the one thing people never have to hand.

Create the next App Store version, so its listing can be prepared. Needed whenever every existing version is already live — asc_readiness_report reports that as version.none. A no-op when a version is already editable, so it is safe to call first.

Dry-run the whole listing pipeline and return the exact changes it would send to App Store Connect. Writes nothing. Call this before asc_apply_release so the human can see the diff first.

The main tool. Answers 'can this version be submitted, and if not, what exactly is in the way, in what order'. Read-only. Returns findings with a verdict and an ordered list of next actions, each marked as something this tool can fix or something only a human in App Store Connect can. Start here.

Publish a reply to one customer review on the App Store — publicly, under the developer's name. Replying again replaces the previous reply; the same text twice changes nothing. Draft the reply in the review's language, show the exact text to the human, and call this only once they approve that text. Never reply in bulk without approval of each reply.

Submit the app version to App Review, with the configured subscriptions and in-app purchases. This is the irreversible one. It computes the readiness report first and refuses if anything is blocking, unless force is set. An app's first product is sent by API with the version; if App Store Connect refuses it, nothing is submitted and the result is MANUAL with the clicks — or call again with skipProducts: true to send the app alone. After a submission, follow it with asc_readiness_report or check --wait.

Upload the PNGs in the configured directory to the version's screenshot set. Deletes remote screenshots that have no local counterpart only when prune is true, which it is not by default.

Check a config against the schema and against the rules Apple enforces but does not document — emoji in the description, keywords over 100 bytes, whatsNew on a first version. With preflight: true, also read the app itself (Info.plist, privacy manifest, code) for what App Review rejects: missing or generic permission texts, invalid required-reason codes, login without an equivalent private option, no account deletion, no restore purchases. Touches no network and needs no credentials, so it is safe to call while drafting.