Manage App Store Connect authentication using the `asc` CLI tool.
Use this skill when:
(1) Logging in with an API key: "asc auth login", "save my credentials", "set up authentication"
(2) Managing multiple accounts: "asc auth list", "switch account", "use work account", "add another account"
(3) Switching the active account: "asc auth use NAME", "switch to personal account"
(4) Logging out: "asc auth logout", "remove credentials", "remove account"
(5) Verifying current credentials: "asc auth check", "which account am I using?"
(6) Updating account settings: "asc auth update --vendor-number", "save my vendor number"
(7) Explaining the credentials file format (~/.asc/credentials.json)
(8) Troubleshooting 401 auth errors or "missing credentials" errors
Instrucciones de origen · Vista previa de solo lectura
name
asc-auth
description
Manage App Store Connect authentication using the `asc` CLI tool.
Use this skill when:
(1) Logging in with an API key: "asc auth login", "save my credentials", "set up authentication"
(2) Managing multiple accounts: "asc auth list", "switch account", "use work account", "add another account"
(3) Switching the active account: "asc auth use NAME", "switch to personal account"
(4) Logging out: "asc auth logout", "remove credentials", "remove account"
(5) Verifying current credentials: "asc auth check", "which account am I using?"
(6) Updating account settings: "asc auth update --vendor-number", "save my vendor number"
(7) Explaining the credentials file format (~/.asc/credentials.json)
(8) Troubleshooting 401 auth errors or "missing credentials" errors
asc auth — Multi-Account Authentication
Manages App Store Connect API key credentials in ~/.asc/credentials.json. Supports multiple named accounts with an active account that all asc commands use automatically.
The vendorNumber field is optional — omitted from JSON when nil. It is used by sales-reports and finance-reports commands for auto-resolution when --vendor-number is not provided.
Legacy migration: Old single-credential files ({ "keyID": ..., "issuerID": ..., "privateKeyPEM": ... }) are automatically migrated to a "default" named account on first use.
Typical Workflows
First-time setup (single account)
asc auth login \
--key-id KEYID123 \
--issuer-id abc-def-456 \
--private-key-path ~/.asc/AuthKey_KEYID123.p8
asc auth check --pretty # verify source: "file"
asc apps list # works without env vars
Multiple accounts (personal + work)
# Add accounts
asc auth login --key-id K1 --issuer-id I1 --private-key-path ~/.asc/personal.p8 --name personal
asc auth login --key-id K2 --issuer-id I2 --private-key-path ~/.asc/work.p8 --name work
# List all
asc auth list --pretty
# Switch
asc auth use personal
asc apps list # now uses personal account
asc auth use work
asc apps list # now uses work account
Save vendor number for reports
# During login
asc auth login --key-id K1 --issuer-id I1 --private-key-path key.p8 --vendor-number 88012345
# Or add to existing account
asc auth update --vendor-number 88012345
# Now reports auto-resolve vendor number
asc sales-reports download --report-type SALES --sub-type SUMMARY --frequency DAILY
Remove an account
asc auth list # find the name
asc auth logout --name personal
asc auth list # confirm removal