Do I need to export before importing?

Yes — export gives you a local snapshot to validate and modify safely.

Can I run a dry-run before applying changes?

Yes — use --dry-run with the import command or dry-run options to preview changes without overwriting assets.

How do I handle translations across locales?

Export localizations, translate files in fastlane/metadata/android, then import all at once to apply all translations.

gpd-metadata-sync

Scanned

npx machina-cli add skill rudrankriyam/app-store-connect-cli-skills/gpd-metadata-sync --openclaw

Files (1)

SKILL.md

2.1 KB

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 validate before import to catch missing fields.
Use --dry-run when available before overwriting assets.

Source

git clone https://github.com/rudrankriyam/app-store-connect-cli-skills/blob/main/skills/gpd-metadata-sync/SKILL.mdView on GitHub

Overview

This skill keeps your local Google Play metadata in sync with the live store. It covers store listing fields, images/assets, and multi-language content, and includes Fastlane-style workflows to export, validate, and import updates for listings and translations.

How This Skill Works

Typically you export the current state, edit locally (listings, details, images, and assets), then validate and import updates. The workflow uses commands like gpd publish listing get/update, images list/upload/delete, assets upload, and the fastlane migrate commands to manage metadata in fastlane/metadata/android.

When to Use It

Updating a store listing or localized description for a global rollout.
Preparing translations in multi-language workflows.
Exporting current metadata to a versioned local folder for review.
Validating local files before importing to catch missing or malformed fields.
Performing a dry-run to preview asset changes before overwriting assets.

Quick Start

Step 1: Export current state to fastlane/metadata/android: gpd migrate fastlane export --package com.example.app --output fastlane/metadata/android
Step 2: Edit translations and metadata locally, then validate: gpd migrate fastlane validate --dir fastlane/metadata/android
Step 3: Import updates and review results: gpd migrate fastlane import --package com.example.app --dir fastlane/metadata/android

Best Practices

Always run gpd migrate fastlane validate before import.
Use --dry-run when available before overwriting assets.
Keep package name consistent and track changes by locale.
Store metadata under fastlane/metadata/android and version it in source control.
Review image related commands (upload/delete) to avoid accidental deletions.

Example Use Cases

Export current Google Play metadata: gpd migrate fastlane export --package com.example.app --output fastlane/metadata/android
Validate local metadata before importing: gpd migrate fastlane validate --dir fastlane/metadata/android
Import updates after translation: gpd migrate fastlane import --package com.example.app --dir fastlane/metadata/android
Update a localized title: gpd publish listing update --package com.example.app --locale en-US --title "My App"
Sync images for a locale: gpd publish images upload icon.png --package com.example.app --locale en-US

Frequently Asked Questions

Add this skill to your agents