agentleFS
The-Artificer-of-Ciphers-LLCThe-Artificer-of-Ciphers-LLC/skills-from-the-artificer/asc-release-flow/SKILL.md

asc-release-flow

Skill6 starsChanged 33 days agoMITView on GitHub

End-to-end release workflows for TestFlight and App Store using asc publish, builds, versions, and submit commands. Use when asked to upload a build, distribute to TestFlight, or submit to App Store.

9 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when you need to get a new build into TestFlight or submit to the App Store.

    line 8
  2. Very specific:

    Ensure credentials are set (asc auth login or ASC_* env vars).

    line 11
  3. Distinctive:

    Use a new build number for each upload.

    line 12
  4. Very specific:

    Prefer ASC_APP_ID or pass --app explicitly.

    line 13
  5. Distinctive:

    Check or cancel submission:

    line 36
  6. Distinctive:

    When releasing the same version across platforms:

    line 92
  7. Distinctive:

    Create version for each platform if not exists

    line 94
  8. Very specific:

    Always use --help to verify flags for the exact command.

    line 110
  9. Very specific:

    Use --output table / --output markdown for human-readable output.

    line 111

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Release flow (TestFlight and App Store)

Use this skill when you need to get a new build into TestFlight or submit to the App Store.

Preconditions

  • Ensure credentials are set (asc auth login or ASC_* env vars).
  • Use a new build number for each upload.
  • Prefer ASC_APP_ID or pass --app explicitly.
  • Build must have encryption compliance resolved (see asc-submission-health skill).

iOS Release

Preferred end-to-end commands

  • TestFlight:
    • asc publish testflight --app <APP_ID> --ipa <PATH> --group <GROUP_ID>[,<GROUP_ID>]
    • Optional: --wait, --notify, --platform, --poll-interval, --timeout
  • App Store:
    • asc publish appstore --app <APP_ID> --ipa <PATH> --version <VERSION>
    • Optional: --wait, --submit --confirm, --platform, --poll-interval, --timeout

Manual sequence (when you need more control)

  1. Upload the build:
    • asc builds upload --app <APP_ID> --ipa <PATH>
  2. Find the build ID if needed:
    • asc builds latest --app <APP_ID> [--version <VERSION>] [--platform <PLATFORM>]
  3. TestFlight distribution:
    • asc builds add-groups --build <BUILD_ID> --group <GROUP_ID>[,<GROUP_ID>]
  4. App Store attach + submit:
    • asc versions attach-build --version-id <VERSION_ID> --build <BUILD_ID>
    • asc submit create --app <APP_ID> --version <VERSION> --build <BUILD_ID> --confirm
  5. Check or cancel submission:
    • asc submit status --id <SUBMISSION_ID> or --version-id <VERSION_ID>
    • asc submit cancel --id <SUBMISSION_ID> --confirm

macOS Release

macOS apps are distributed as .pkg files, not .ipa.

Build and Export

See asc-xcode-build skill for full build/archive/export workflow.

Upload PKG

Upload the exported .pkg using asc:

asc builds upload \
  --app <APP_ID> \
  --pkg <PATH_TO_PKG> \
  --version <VERSION> \
  --build-number <BUILD_NUMBER> \
  --wait

Notes:

  • --pkg automatically sets platform to MAC_OS.
  • asc publish appstore currently supports --ipa workflows; for macOS .pkg, use asc builds upload --pkg + attach/submit steps below.

Attach and Submit

Same as iOS, but use --platform MAC_OS:

# Wait for build to process
asc builds list --app <APP_ID> --platform MAC_OS --limit 5

# Attach to version
asc versions attach-build --version-id <VERSION_ID> --build <BUILD_ID>

# Create submission
asc review submissions-create --app <APP_ID> --platform MAC_OS

# Add version item
asc review items-add \
  --submission <SUBMISSION_ID> \
  --item-type appStoreVersions \
  --item-id <VERSION_ID>

# Submit
asc review submissions-submit --id <SUBMISSION_ID> --confirm

visionOS / tvOS Release

Same as iOS flow, use appropriate --platform:

  • VISION_OS
  • TV_OS

Multi-Platform Release

When releasing the same version across platforms:

  1. Upload each platform's build separately
  2. Create version for each platform if not exists
  3. Attach builds to respective versions
  4. Submit each platform separately (or together via reviewSubmissions API)

Pre-submission Checklist

Before submitting, verify:

  • Build status is VALID (not processing)
  • Encryption compliance resolved
  • Content rights declaration set
  • Copyright field populated
  • All localizations complete
  • Screenshots present

See asc-submission-health skill for detailed preflight checks.

Notes

  • Always use --help to verify flags for the exact command.
  • Use --output table / --output markdown for human-readable output; default is JSON.
  • macOS builds require ITSAppUsesNonExemptEncryption in Info.plist to avoid encryption issues.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.