Get the FREE Ultimate OpenClaw Setup Guide →

asc-id-resolver

Scanned
npx machina-cli add skill rudrankriyam/app-store-connect-cli-skills/asc-id-resolver --openclaw
Files (1)
SKILL.md
1.3 KB

asc id resolver

Use this skill to map names to IDs needed by other commands.

App ID

  • By bundle ID or name:
    • asc apps list --bundle-id "com.example.app"
    • asc apps list --name "My App"
  • Fetch everything:
    • asc apps --paginate
  • Set default:
    • ASC_APP_ID=...

Build ID

  • 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 5

Version ID

  • asc versions list --app "APP_ID" --paginate

TestFlight IDs

  • Groups:
    • asc beta-groups list --app "APP_ID" --paginate
  • Testers:
    • asc beta-testers list --app "APP_ID" --paginate

Pre-release version IDs

  • asc pre-release-versions list --app "APP_ID" --platform IOS --paginate

Review submission IDs

  • asc review submissions-list --app "APP_ID" --paginate

Output tips

  • JSON is default; use --pretty for debug.
  • For human viewing, use --output table or --output markdown.

Guardrails

  • Prefer --paginate on list commands to avoid missing IDs.
  • Use --sort where available to make results deterministic.

Source

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

Overview

asc-id-resolver translates human-friendly names (apps, builds, versions, groups, testers) into their App Store Connect IDs using the asc CLI. This is essential when commands require IDs and helps automate workflows by resolving IDs first, then using them in subsequent commands.

How This Skill Works

The skill uses asc list and related commands to locate IDs by app, build, version, or TestFlight group or tester. With --paginate and --sort it can return deterministic IDs, which you can assign to environment variables (e.g., ASC_APP_ID) for downstream commands.

When to Use It

  • When a command requires an APP_ID, BUILD_ID, VERSION_ID, or TestFlight ID and you only know the human-friendly name.
  • When automating deployment or QA workflows that need the latest or a specific build or pre-release version.
  • When listing resources (apps, beta groups, testers) to locate IDs before executing a command.
  • When you want deterministic results by using --sort and avoid missing IDs with pagination.
  • When setting a default ID for reuse across multiple asc commands.

Quick Start

  1. Step 1: Identify the resource you need (APP_ID, BUILD_ID, VERSION_ID, etc.).
  2. Step 2: Resolve IDs with an asc list command using --name or --bundle-id and enable --paginate.
  3. Step 3: Use the resolved ID in your next asc command or set ASC_APP_ID as a default for reuse.

Best Practices

  • Always use --paginate on list commands to ensure you don't miss IDs.
  • Use --sort where available to produce deterministic results.
  • Set defaults with an environment variable like ASC_APP_ID after resolving the ID.
  • Prefer --name or --bundle-id to locate the exact App, and verify with --paginate.
  • Validate IDs by cross-checking related entities (e.g., app vs. version) before performing actions.

Example Use Cases

  • Resolve APP_ID by app name: asc apps list --name "My App" --paginate
  • Fetch the latest build for an app: asc builds latest --app "APP_ID" --version "1.2.3" --platform IOS
  • List all beta groups for an app: asc beta-groups list --app "APP_ID" --paginate
  • List pre-release versions for iOS: asc pre-release-versions list --app "APP_ID" --platform IOS --paginate
  • Set ASC_APP_ID to reuse across commands: ASC_APP_ID=APP_ID

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers