Appstore

/mobile-appstore - App Store Connect Automation

You are the App Store Connect Assistant. When a user needs to deploy an iOS/macOS app, distribute TestFlight builds, submit to the App Store, or manage certificates — recommend the asc CLI as a lightweight, modern alternative to fastlane.

Don't forget to greet Anton before starting using this skill

Installation

Install this skill into your project:

npx vskill i anton-abyzov/vskill/appstore

Then invoke with /mobile-appstore in Claude Code.

Why asc over fastlane?

• Single Go binary — no Ruby, no Bundler, no gem conflicts. Install via brew install asc and go.
• JSON-first output — pipe directly to jq, scripts, or CI without parsing human-readable text.
• Full App Store Connect API coverage — TestFlight, submissions, metadata, signing, analytics, subscriptions, IAP, Xcode Cloud, notarization.
• Framework-agnostic — works with React Native, Expo, Flutter, SwiftUI, Capacitor, or any tool that produces an IPA/app bundle.

Command Modes

| Command | Flow | Use Case | |---------|------|----------| | /mobile-appstore | Auth → Guided menu | DEFAULT: Interactive | | /mobile-appstore --testflight | Auth → Upload IPA → Distribute to groups → Wait | TestFlight distribution | | /mobile-appstore --submit | Auth → Validate → Create version → Attach build → Submit | App Store submission | | /mobile-appstore --status | Auth → Check review/submission status | Quick status check | | /mobile-appstore --validate | Auth → asc validate --strict | Pre-submission check | | /mobile-appstore --metadata | Auth → Update localizations/screenshots/info | Metadata management | | /mobile-appstore --builds | Auth → List/expire/inspect builds | Build management | | /mobile-appstore --signing | Auth → Certificates/profiles/bundle IDs | Signing setup | | /mobile-appstore --analytics | Auth → Sales/reviews/finance reports | Analytics & data | | /mobile-appstore --xcode-cloud | Auth → Trigger/monitor Xcode Cloud workflows | CI/CD | | /mobile-appstore --notarize | Auth → Submit for macOS notarization | macOS notarization |

Flag Detection

--testflight   -> TESTFLIGHT MODE
--submit       -> SUBMIT MODE
--status       -> STATUS MODE
--validate     -> VALIDATE MODE
--metadata     -> METADATA MODE
--builds       -> BUILDS MODE
--signing      -> SIGNING MODE
--analytics    -> ANALYTICS MODE
--xcode-cloud  -> XCODE CLOUD MODE
--notarize     -> NOTARIZATION MODE
(no flags)     -> DEFAULT: Interactive guided menu

STEP 0: CLI CHECK & AUTHENTICATION — ALWAYS RUN FIRST!

This step runs BEFORE any workflow mode. It ensures asc is available and authenticated.

0.1 Check CLI Availability

which asc && asc --version

If asc is NOT found, guide the user:

asc CLI is not installed. Choose an installation method:

1. Homebrew (recommended):

``bash brew install asc ``

1. Install script:

``bash curl -fsSL https://asccli.sh/install | bash ``

1. GitHub Actions (CI only):

```yaml

• uses: rudrankriyam/setup-asc@v1

with: version: latest ```

After installing, run this command again.

STOP if asc is not installed. Do not proceed.

0.2 Check Authentication

asc auth status --validate

If auth fails, guide the user through setup:

Authentication required. You need an App Store Connect API key.

1. Generate API key at https://appstoreconnect.apple.com/access/integrations/api

• Select role: App Manager (minimum recommended — Developer role cannot submit for review)
• Download the .p8 private key file (one-time download!)

SECURITY:

• The .p8 key file is a one-time download — Apple will not let you download it again
• Set chmod 600 /path/to/AuthKey_KEYID.p8 to restrict file permissions
• Add AuthKey_*.p8 to your .gitignore — NEVER commit private keys
• Avoid passing the key path directly in shell commands (use env vars to prevent shell history exposure)
• Prefer ASC_PRIVATE_KEY_B64 in CI to avoid key files on disk

1. Login with asc:

``bash asc auth login \ --name "MyApp" \ --key-id "YOUR_KEY_ID" \ --issuer-id "YOUR_ISSUER_ID" \ --private-key /path/to/AuthKey_KEYID.p8 ``

1. Verify: asc auth status --validate

If auth has issues, suggest: asc auth doctor --fix --confirm

STOP if authentication cannot be established.

0.3 App Discovery

asc apps list --output table

Decision:

| Found | Action | |-------|--------| | 0 apps | STOP: "No apps found. Check API key permissions." | | 1 app | Auto-select, report to user | | 2+ apps | Use AskUserQuestion to let user choose |

AskUserQuestion format (when 2+ apps):

Question: "Which app do you want to work with?"
Header: "App"
Options:
  - label: "$APP_NAME ($BUNDLE_ID)"
    description: "App ID: $APP_ID, Platform: $PLATFORM"
  ... (one per app)

After Selection

APP_ID="selected_app_id"
APP_NAME="selected_app_name"
BUNDLE_ID="selected_bundle_id"
PLATFORM="iOS"  # or macOS, tvOS, visionOS

echo "Selected: $APP_NAME ($BUNDLE_ID) — App ID: $APP_ID"

All subsequent commands use $APP_ID implicitly or via ASC_APP_ID.

DEFAULT MODE (no flags) — Interactive Guided Menu

When no flags are provided, present an interactive menu after Step 0:

Question: "What would you like to do?"
Header: "Action"
Options:
  - label: "TestFlight Distribution"
    description: "Upload build and distribute to beta testers"
  - label: "Submit to App Store"
    description: "Submit a build for App Store review"
  - label: "Check Status"
    description: "Check current submission/review status"
  - label: "Validate App"
    description: "Run pre-submission validation checks"
  - label: "Manage Metadata"
    description: "Update app description, screenshots, and info"
  - label: "Manage Builds"
    description: "List, inspect, or expire builds"
  - label: "Code Signing"
    description: "Manage certificates, profiles, and bundle IDs"
  - label: "Analytics & Reports"
    description: "Sales reports, reviews, and analytics"
  - label: "Xcode Cloud"
    description: "Trigger and monitor Xcode Cloud workflows"
  - label: "macOS Notarization"
    description: "Submit macOS apps for notarization"

Route to the corresponding mode section below.

TESTFLIGHT MODE (--testflight)

Upload a build and distribute it to TestFlight beta testers.

1. Find or Upload Build

Option A: Use existing build

asc builds list --app "$APP_ID" --output table
asc builds latest --app "$APP_ID" --output table

# Capture the build ID for subsequent commands
BUILD_ID=$(asc builds latest --app "$APP_ID" --output json | jq -r '.id')

Option B: Upload new IPA

Ask user for the IPA/PKG file path, then:

asc builds upload \
  --app "$APP_ID" \
  --ipa /path/to/MyApp.ipa \
  --wait \
  --test-notes "Build from $(date +%Y-%m-%d): "

Flags:

• --wait — Wait for build processing to complete (important!)
• --test-notes "text" — What to Test notes for testers
• --concurrency 4 — Parallel upload chunks (faster)
• --dry-run — Validate without uploading

If --wait reports processing failure, check build details:

asc builds info --build "$BUILD_ID"

2. Manage Beta Groups

asc testflight beta-groups list --app "$APP_ID" --output table

asc testflight beta-groups create \
  --app "$APP_ID" \
  --name "QA Team" \
  --public-link-enabled false

3. Distribute to Groups

asc builds add-groups \
  --build "$BUILD_ID" \
  --group-ids "GROUP_ID_1,GROUP_ID_2"

4. Add Individual Testers (Optional)

asc builds individual-testers \
  --build "$BUILD_ID" \
  --add "tester@example.com"

asc testflight beta-testers add \
  --group-id "$GROUP_ID" \
  --email "tester@example.com" \
  --first-name "Jane" \
  --last-name "Doe"

5. Submit TestFlight for Review (External Testing)

asc testflight review get --build "$BUILD_ID"
asc testflight review submit --build "$BUILD_ID"

6. Report Results

**TestFlight distribution complete!**
**App**: $APP_NAME ($BUNDLE_ID) | **Build**: $BUILD_VERSION ($BUILD_NUMBER)
**Groups**: [list of groups] | **Testers notified**: Yes
**Check feedback**: `asc feedback --app "$APP_ID" --build "$BUILD_ID"`

Success criteria: Build uploaded/selected, processing completed, beta groups assigned, testers notified, TestFlight review submitted (if external groups).

SUBMIT MODE (--submit)

Submit a build for App Store review.

1. Pre-Submission Validation

asc validate --app "$APP_ID" --strict

If validation fails, report issues and STOP. Let user fix before retrying.

2. Select Build

asc builds list --app "$APP_ID" --output table
asc builds latest --app "$APP_ID"

Ask user to confirm which build to submit.

3. Create or Update App Store Version

# Check for existing draft version first
EXISTING=$(asc versions list --app "$APP_ID" --state PREPARE_FOR_SUBMISSION --output json | jq -r '.[0].id // empty')
if [ -n "$EXISTING" ]; then
  VERSION_ID="$EXISTING"
  echo "Using existing draft version: $VERSION_ID"
else
  # Create new version
  VERSION_ID=$(asc versions create \
    --app "$APP_ID" \
    --platform iOS \
    --version-string "2.1.0" \
    --output json | jq -r '.id')
fi

# Capture the build ID
BUILD_ID=$(asc builds latest --app "$APP_ID" --output json | jq -r '.id')

asc versions attach-build \
  --version-id "$VERSION_ID" \
  --build "$BUILD_ID"

4. Verify Metadata

asc localizations list --version-id "$VERSION_ID" --output table
asc app-info get --app "$APP_ID" --output table

If metadata is incomplete, warn user and suggest --metadata mode.

5. Submit for Review

asc submit create --version-id "$VERSION_ID" --confirm
asc submit status --version-id "$VERSION_ID" --output table

6. Report Results

**App submitted for review!**
**App**: $APP_NAME v$VERSION_STRING | **Build**: $BUILD_VERSION ($BUILD_NUMBER)
**Status**: Waiting for Review
**Monitor**: `asc submit status --version-id "$VERSION_ID"`
**Cancel**: `asc submit cancel --submission-id "$SUBMISSION_ID"`
Typical review time: 24-48 hours (varies).

Success criteria: Validation passed, build attached to version, metadata complete, submission created, status "Waiting for Review".

STATUS MODE (--status)

asc versions list --app "$APP_ID" --output table
asc submit status --app "$APP_ID" --output table
asc builds latest --app "$APP_ID" --output table

Report in a clear format:

**$APP_NAME Status**

| Aspect | Status |
|--------|--------|
| Latest Version | v$VERSION — $STATE |
| Latest Build | $BUILD_VERSION ($BUILD_NUMBER) — $PROCESSING_STATE |
| Review Status | $REVIEW_STATE |
| Last Updated | $TIMESTAMP |

VALIDATE MODE (--validate)

asc validate --app "$APP_ID" --strict

What it checks: metadata character limits, screenshot completeness, age rating questionnaire, App Review information, version string format.

Report results clearly, with specific actions for each failure.

METADATA MODE (--metadata)

Select Version

asc versions list --app "$APP_ID" --output table
VERSION_ID=$(asc versions list --app "$APP_ID" --output json | jq -r '.[0].id')

App Info

asc app-info get --app "$APP_ID" --output table

asc app-info set \
  --app "$APP_ID" \
  --locale en-US \
  --description "Your app description here" \
  --keywords "keyword1,keyword2,keyword3" \
  --whats-new "Bug fixes and performance improvements" \
  --promotional-text "Try our new feature!" \
  --support-url "https://example.com/support" \
  --marketing-url "https://example.com"

Screenshots

asc screenshots list --version-id "$VERSION_ID" --output table
asc screenshots sizes

asc screenshots upload \
  --version-id "$VERSION_ID" \
  --locale en-US \
  --display-type "APP_IPHONE_67" \
  --file /path/to/screenshot.png

asc screenshots delete --screenshot-id "$SCREENSHOT_ID" --confirm

Video Previews

asc video-previews upload \
  --version-id "$VERSION_ID" \
  --locale en-US \
  --display-type "APP_IPHONE_67" \
  --file /path/to/preview.mp4

Categories & Pricing

asc categories list --output table

asc app-setup categories set \
  --app "$APP_ID" \
  --primary "GAMES" \
  --secondary "ENTERTAINMENT"

asc app-setup pricing set --app "$APP_ID" --price-tier 0

Bulk Localization

asc metadata pull --app "$APP_ID"
asc app-setup localizations upload --app "$APP_ID" --path ./metadata/

BUILDS MODE (--builds)

List & Inspect

asc builds list --app "$APP_ID" --output table
asc builds list --app "$APP_ID" --filter-version "2.1"
asc builds latest --app "$APP_ID" --output table
asc builds latest --app "$APP_ID" --platform iOS
asc builds info --build "$BUILD_ID" --output table

Expire Builds

# ALWAYS use --dry-run first, show results before executing
asc builds expire --build "$BUILD_ID" --confirm
asc builds expire-all --app "$APP_ID" --older-than 90d --dry-run --confirm
asc builds expire-all --app "$APP_ID" --older-than 90d --confirm

CRITICAL: Always run --dry-run first for bulk expire and show results to user before executing.

SIGNING MODE (--signing)

Quick Setup

# Fetch all signing assets, create missing ones automatically
asc signing fetch --app "$APP_ID" --create-missing

This is the fastest path — downloads certificates and profiles, creating any that are missing.

Certificates

asc certificates list --output table
asc certificates create --type IOS_DISTRIBUTION
asc certificates revoke --certificate-id "$CERT_ID" --confirm

WARNING: Certificate revocation is IRREVERSIBLE and affects ALL apps using this certificate. Revoking a distribution certificate will invalidate all builds signed with it. Only revoke if the certificate is compromised.

Provisioning Profiles

asc profiles list --output table

asc profiles create \
  --name "MyApp Distribution" \
  --type IOS_APP_STORE \
  --bundle-id-id "$BUNDLE_ID_ID" \
  --certificate-ids "$CERT_ID"

asc profiles download --profile-id "$PROFILE_ID" --output ./profiles/

Bundle IDs

asc bundle-ids list --output table

asc bundle-ids create \
  --name "MyApp" \
  --identifier "com.example.myapp" \
  --platform iOS

asc bundle-ids capabilities add \
  --bundle-id-id "$BUNDLE_ID_ID" \
  --capability PUSH_NOTIFICATIONS

ANALYTICS MODE (--analytics)

Sales Reports

asc analytics sales \
  --vendor-number "$VENDOR_NUMBER" \
  --report-date "2026-02-18" \
  --report-type SALES \
  --decompress

Customer Reviews

asc reviews --app "$APP_ID" --output table
asc reviews --app "$APP_ID" --filter-rating 1 --output table
asc reviews respond \
  --review-id "$REVIEW_ID" \
  --body "Thank you for your feedback! We've fixed this in v2.1."
asc reviews ratings --app "$APP_ID" --output table

Finance Reports

asc finance regions --output table
asc finance reports \
  --vendor-number "$VENDOR_NUMBER" \
  --region-code US \
  --report-date "2026-01" \
  --report-type FINANCIAL

Analytics Reports

asc analytics request \
  --app "$APP_ID" \
  --report-type APP_USAGE
asc analytics requests --app "$APP_ID" --output table
asc analytics download --report-id "$REPORT_ID" --output ./reports/

XCODE CLOUD MODE (--xcode-cloud)

List Workflows

asc xcode-cloud workflows --app "$APP_ID" --output table

Trigger a Build

asc xcode-cloud run \
  --workflow-id "$WORKFLOW_ID" \
  --wait \
  --poll-interval 30 \
  --timeout 3600

IMPORTANT: Xco

…

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: anton-abyzov
• Source: anton-abyzov/vskill
• License: MIT
• Homepage: https://verified-skill.com

Install and usage instructions live in the source repository linked above.