gpd-id-resolver
GPD ID Resolver
Use this skill to map names to IDs needed by other gpd commands.
Package name (app ID)
- Package name is the primary identifier:
com.example.app. - Always pass
--packageexplicitly for deterministic results.
Track names
- Common tracks:
internal,alpha,beta,production. - List tracks:
gpd publish tracks --package com.example.app
Version codes and release status
- Use release status to find version codes on a track:
gpd publish status --package com.example.app --track production
Tester groups
- List testers by track:
gpd publish testers list --package com.example.app --track internal
Monetization IDs
- Products:
gpd monetization products list --package com.example.appgpd monetization products get sku123 --package com.example.app
- One-time products:
gpd monetization onetimeproducts list --package com.example.app
- Subscriptions:
gpd monetization subscriptions list --package com.example.appgpd monetization subscriptions get sub123 --package com.example.app
- Base plans and offers:
gpd monetization baseplans migrate-prices --package com.example.app sub123 plan456 --region-code US --price-micros 9990000gpd monetization offers list --package com.example.app sub123 plan456
Permissions IDs
- Developer users:
gpd permissions users list --developer-id DEV_ID
- App grants:
gpd permissions grants create --package com.example.app --email user@example.com --app-permissions CAN_REPLY_TO_REVIEWS
Output tips
- JSON is default; use
--prettyfor debugging. - Use
--allon list commands to avoid missing items.
More from rudrankriyam/app-store-connect-cli-skills
asc-cli-usage
Guidance for using asc cli in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.
2.2Kasc-xcode-build
Build, archive, export, upload, and manage Xcode version/build numbers with the current asc xcode helpers before App Store Connect upload or submission. Use when creating an IPA or PKG for upload.
2.2Kasc-release-flow
Determine whether an app is ready to submit, then drive the current App Store release flow with asc, including validation, staging, review submission, first-time availability, subscriptions, IAP, Game Center, and App Privacy checks.
2.1Kasc-submission-health
Validate App Store submission readiness, submit prepared versions, and monitor review status with current asc commands. Use when shipping or troubleshooting review submissions.
2.1Kasc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
2.1Kasc-testflight-orchestration
Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.
2.0K