asc-iris
Manage App Store Connect private API (iris) with cookie-based authentication using the `asc` CLI tool. Use this skill when: (1) Checking iris session status: "asc iris status", "am I logged in to iris", "check iris cookies" (2) Listing apps via iris private API: "asc iris apps list", "list my apps with iris" (3) Creating a new app: "asc iris apps create --name NAME --bundle-id ID --sku SKU", "create app", "register new app", "add app to App Store Connect" (4) User mentions "iris", "private API", "cookie-based auth", "create app", "register app", "new app on App Store Connect" (5) User wants to do something that the public API cannot do (e.g. app creation) (6) Troubleshooting iris cookie errors or "No App Store Connect cookies found" messages (7) Reading App Review rejection messages: "asc iris resolution-center get --submission-id ID", "why was my app rejected", "resolution center", "rejection reason", "App Review message"
How do I install this agent skill?
npx skills add https://github.com/tddworks/asc-cli-skills --skill asc-irisIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill manages Apple App Store Connect using a command-line tool and session cookies. It features a design where the agent is encouraged to execute commands suggested within the tool's output, which represents a surface for indirect instructions.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
asc iris — App Store Connect Private API
Access App Store Connect private API (iris) endpoints using cookie-based authentication. The iris API powers the ASC web UI and exposes capabilities not available through the public REST API, such as app creation.
Authentication
Iris uses browser cookies, not JWT API keys. Two resolution methods:
- Browser auto-extraction (default) — log in to appstoreconnect.apple.com in Chrome/Safari/Firefox. Cookies are extracted automatically via SweetCookieKit.
- Environment variable — set
ASC_IRIS_COOKIESfor CI/CD:export ASC_IRIS_COOKIES="myacinfo=DAWT...; itctx=eyJ..."
The essential cookie is myacinfo (set on .apple.com). Additional cookies (itctx, dqsid, wosid) are collected from appstoreconnect.apple.com.
How to Navigate (CAEOAS Affordances)
Every JSON response contains an "affordances" field with ready-to-run commands:
{
"source": "browser",
"cookieCount": 5,
"affordances": {
"listApps": "asc iris apps list",
"createApp": "asc iris apps create --name <name> --bundle-id <id> --sku <sku>"
}
}
Commands
status — check iris session
asc iris status --pretty
Output:
{
"data": [{
"affordances": {
"createApp": "asc iris apps create --name <name> --bundle-id <id> --sku <sku>",
"listApps": "asc iris apps list"
},
"cookieCount": 5,
"source": "browser"
}]
}
If cookies are not found, the error message will suggest logging in to appstoreconnect.apple.com or setting ASC_IRIS_COOKIES.
apps list — list all apps
asc iris apps list --pretty
Output:
{
"data": [{
"affordances": {
"listAppInfos": "asc app-infos list --app-id 1234567890",
"listVersions": "asc versions list --app-id 1234567890"
},
"bundleId": "com.example.app",
"id": "1234567890",
"name": "My App",
"platforms": ["IOS"],
"primaryLocale": "en-US",
"sku": "MYSKU"
}]
}
apps create — create a new app
asc iris apps create \
--name "My App" \
--bundle-id com.example.app \
--sku com.example.app \
[--primary-locale en-US] \
[--platforms IOS] \
[--version 1.0] \
--pretty
| Flag | Required | Default | Description |
|---|---|---|---|
--name | ✅ | — | App name (shown on App Store) |
--bundle-id | ✅ | — | Bundle identifier (must match a registered bundle ID) |
--sku | ✅ | — | SKU identifier (unique within your account) |
--primary-locale | ❌ | en-US | Primary locale |
--platforms | ❌ | IOS | One or more: IOS, MAC_OS |
--version | ❌ | 1.0 | Initial version string |
Multi-platform example:
asc iris apps create \
--name "My Universal App" \
--bundle-id com.example.universal \
--sku com.example.universal \
--platforms IOS MAC_OS \
--version 2.0 \
--pretty
Important: The --bundle-id must reference an already-registered bundle identifier. Register one first with asc bundle-ids register if needed.
resolution-center get — read App Review's rejection message
The official API only reports that a submission has UNRESOLVED_ISSUES; the
reviewer's message text and guideline citations are iris-only. When a
submission or rejected item shows the getResolutionDetails affordance, run:
asc iris resolution-center get --submission-id <SUBMISSION_ID> --plain-text --pretty
asc iris resolution-center get --submission-id <SUBMISSION_ID> --out ./rc-attachments # also download attachments
Returns the Resolution Center thread: messages[] (reviewer text, fromActor
APPLE/USER), rejectionReasons[] (guideline section/code/description),
and attachments[] when App Review attached files (--out <dir> downloads them).
Full docs: docs/features/resolution-center.md
Typical Workflow
# 1. Check if you're logged in
asc iris status --pretty
# 2. Create a new app
asc iris apps create \
--name "My New App" \
--bundle-id com.example.newapp \
--sku com.example.newapp \
--pretty
# 3. Continue with public API commands (use the app ID from step 2)
asc versions list --app-id <id>
asc app-infos list --app-id <id>
Troubleshooting
"No App Store Connect cookies found"
- Make sure you're logged in to appstoreconnect.apple.com in your browser
- If using Chrome, the CLI needs Keychain access to decrypt cookies — grant access when prompted
- For CI/CD, set
ASC_IRIS_COOKIESwith the cookie string
409 ENTITY_ERROR.INCLUDED.INVALID_ID
- Placeholder IDs in the create request must use the
${local-id}format — this is handled automatically by the CLI
Empty results from iris apps list
- This is normal if no apps have been created yet — create one with
asc iris apps create
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/tddworks/asc-cli-skills/asc-iris">View asc-iris on skillZs</a>