gpd-metadata-sync
GPD Metadata Sync
Use this skill to keep local metadata in sync with Google Play.
Store listing fields
gpd publish listing get --package com.example.app
gpd publish listing update --package com.example.app --locale en-US --title "My App"
gpd publish details get --package com.example.app
gpd publish details update --package com.example.app --contact-email support@example.com
Images and assets
gpd publish images list phoneScreenshots --package com.example.app --locale en-US
gpd publish images upload icon icon.png --package com.example.app --locale en-US
gpd publish images delete phoneScreenshots IMAGE_ID --package com.example.app --locale en-US
gpd publish images deleteall featureGraphic --package com.example.app --locale en-US
gpd publish assets upload ./assets --package com.example.app
gpd publish assets spec
Fastlane metadata workflow
Export current state
gpd migrate fastlane export --package com.example.app --output fastlane/metadata/android
Validate local files
gpd migrate fastlane validate --dir fastlane/metadata/android
Import updates
gpd migrate fastlane import --package com.example.app --dir fastlane/metadata/android
Import with options
gpd migrate fastlane import --package com.example.app --dir fastlane/metadata/android --replace-images
gpd migrate fastlane import --package com.example.app --dir fastlane/metadata/android --skip-images --dry-run
Multi-language workflow
- Export localizations:
gpd migrate fastlane export --package com.example.app --output fastlane/metadata/android
-
Translate files in
fastlane/metadata/android. -
Import all at once:
gpd migrate fastlane import --package com.example.app --dir fastlane/metadata/android
Notes
- Use
gpd migrate fastlane validatebefore import to catch missing fields. - Use
--dry-runwhen available before overwriting assets.
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