asc-ad-hoc-distribution

Distributes iOS archives as private install links to registered devices via S3-compatible storage.

1.0k|57|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-ad-hoc-distribution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-ad-hoc-distribution
Source: https://github.com/rudrankriyam/app-store-connect-cli-skills/tree/main/skills/asc-ad-hoc-distribution
Command: npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-ad-hoc-distribution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distributing iOS builds to testers outside TestFlight requires manual device registration, ad hoc provisioning profile management, re-signing, and secure hosting. This Skill automates that entire pipeline with the asc distribute command, producing a verified private install link.

Core Features & Use Cases

  • Plan-Apply Workflow: Generate a read-only plan with typed blockers and an effects inventory, then apply it only after authorizing the exact plan hash.
  • Resumable Runs: Inspect run status, resume recoverable runs, and verify published artifacts with live fetches or connected-device observation.
  • Private S3 Publication: Publish immutable IPA bundles to caller-owned S3-compatible buckets with presigned, TTL-limited install links stored in owner-only artifacts.
  • Use Case: A pull request build needs testing on a specific device. Plan the distribution from the .xcarchive, confirm the plan hash, and share the resulting private install link with the tester.

Quick Start

Ask the agent to plan and apply an ad hoc distribution of your .xcarchive to registered devices using asc distribute with a private S3 bucket.

Frequently Asked Questions about asc-ad-hoc-distribution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I distribute an iOS build to testers without TestFlight?

Use asc distribute to plan and apply an ad hoc distribution from an existing .xcarchive. It registers devices, creates ad hoc profiles, re-signs the app, and publishes a private install link to your S3-compatible bucket.

How do I resume a failed asc distribute run?

Run asc distribute status with the run ID to check typed state, then use asc distribute resume to revalidate durable evidence and retry. Resume never blindly repeats a remote write; expired inputs require a new plan.

Does asc distribute support AWS S3 or other object storage?

Yes, it publishes to any S3-compatible bucket using ASC_S3_ACCESS_KEY_ID, ASC_S3_SECRET_ACCESS_KEY, and optional session token, or the standard AWS SDK credential chain. It never creates buckets or changes storage policies.

Why does asc distribute plan report ready false?

The plan exits successfully with ready false when blockers exist, such as embedded app targets, expired signing material, or missing devices. Inspect the typed blockers and effects in the JSON output, resolve them, and create a new plan.

When should I use TestFlight instead of ad hoc distribution?

Use TestFlight or App Store release skills when builds should go through Apple-hosted distribution. Ad hoc distribution fits private release-testing on registered devices where you control hosting and want install links outside Apple's pipeline.