Get the FREE Ultimate OpenClaw Setup Guide →

asc-build-lifecycle

Scanned
npx machina-cli add skill rudrankriyam/app-store-connect-cli-skills/asc-build-lifecycle --openclaw
Files (1)
SKILL.md
1.2 KB

asc build lifecycle

Use this skill to manage build state, processing, and retention.

Find the right build

  • Latest build:
    • asc builds latest --app "APP_ID" --version "1.2.3" --platform IOS
  • Recent builds:
    • asc builds list --app "APP_ID" --sort -uploadedDate --limit 10

Inspect processing state

  • asc builds info --build "BUILD_ID"

Distribution flows

  • Prefer end-to-end:
    • asc publish testflight --app "APP_ID" --ipa "./app.ipa" --group "GROUP_ID" --wait
    • asc publish appstore --app "APP_ID" --ipa "./app.ipa" --version "1.2.3" --wait --submit --confirm

Cleanup

  • Preview expiration:
    • asc builds expire-all --app "APP_ID" --older-than 90d --dry-run
  • Apply expiration:
    • asc builds expire-all --app "APP_ID" --older-than 90d --confirm
  • Single build:
    • asc builds expire --build "BUILD_ID"

Notes

  • asc builds upload prepares upload operations only; use asc publish for end-to-end flows.
  • For long processing times, use --wait, --poll-interval, and --timeout where supported.

Source

git clone https://github.com/rudrankriyam/app-store-connect-cli-skills/blob/main/skills/asc-build-lifecycle/SKILL.mdView on GitHub

Overview

asc-build-lifecycle helps you track build processing, locate the latest builds for a given app/version, inspect individual build states, and clean up old builds to maintain retention. It covers find, inspect, end-to-end distribution, and cleanup workflows, aligning with typical ASC workflows.

How This Skill Works

The skill uses ASC CLI commands to query builds (latest, list), inspect processing state (info), perform end-to-end distribution (publish), and manage retention (expire). For long processing times, you can apply --wait, --poll-interval, and --timeout to control blocking and polling. It differentiates between the upload preparation path (asc builds upload) and the full publish path (asc publish ...) for distribution.

When to Use It

  • When you need the latest build for a specific app and version to verify processing
  • When you want a quick view of recent builds to monitor uploads
  • When a build is stuck or you need to inspect its processing state
  • When performing end-to-end distribution and you want to wait for completion
  • When cleaning up storage by expiring older builds (e.g., older-than 90 days) or a single build

Quick Start

  1. Step 1: Identify the target build with asc builds latest or asc builds list for your APP_ID and version
  2. Step 2: Inspect the build state with asc builds info --build "BUILD_ID" to confirm processing
  3. Step 3: If distributing, run asc publish (testflight or appstore) with --wait; for cleanup, use expire-all or expire with a dry-run first

Best Practices

  • Prefer end-to-end distribution flows using publish with --wait to ensure completion before proceeding
  • Use asc builds latest and list with correct app IDs and versions to target the right build
  • Always inspect a build with asc builds info before taking action
  • Dry-run expirations first with expire-all --older-than X --dry-run to avoid accidental data loss
  • If processing takes long, leverage --wait, --poll-interval, and --timeout to control polling

Example Use Cases

  • asc builds latest --app "APP_ID" --version "1.2.3" --platform IOS
  • asc builds list --app "APP_ID" --sort -uploadedDate --limit 10
  • asc builds info --build "BUILD_ID"
  • asc publish testflight --app "APP_ID" --ipa "./app.ipa" --group "GROUP_ID" --wait
  • asc builds expire-all --app "APP_ID" --older-than 90d --dry-run

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers