🎯

asc-metadata-sync

🎯Skill

from rudrankriyam/app-store-connect-cli-skills

What it does

Synchronizes and validates App Store Connect metadata and localizations across different locales and version releases.

📦

Part of

rudrankriyam/app-store-connect-cli-skills(10 items)

asc-metadata-sync

Installation

Quick InstallInstall with npx

npx add-skill rudrankriyam/app-store-connect-cli-skills

📖 Extracted from docs: rudrankriyam/app-store-connect-cli-skills

Need more details? View full documentation on GitHub →

15Installs

AddedFeb 4, 2026

View on GitHub Back to Skills

Skill Details

SKILL.md

Sync and validate App Store metadata and localizations with asc, including Fastlane format migration. Use when updating metadata or translations.

Overview

# ASC Metadata Sync

Use this skill to keep local metadata in sync with App Store Connect.

Two Types of Localizations

1. Version Localizations (per-release)

Fields: description, keywords, whatsNew, supportUrl, marketingUrl, promotionalText

```bash

# List version localizations

asc localizations list --version "VERSION_ID"

# Download

asc localizations download --version "VERSION_ID" --path "./localizations"

# Upload from .strings files

asc localizations upload --version "VERSION_ID" --path "./localizations"

```

2. App Info Localizations (app-level)

Fields: name, subtitle, privacyPolicyUrl, privacyChoicesUrl, privacyPolicyText

```bash

# First, find the app info ID

asc app-infos list --app "APP_ID"

# List app info localizations

asc localizations list --app "APP_ID" --type app-info --app-info "APP_INFO_ID"

# Upload app info localizations

asc localizations upload --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --path "./app-info-localizations"

```

Note: If you get "multiple app infos found", you must specify --app-info with the correct ID.

Fastlane Format Workflow

Export current state

```bash

asc migrate export --app "APP_ID" --output "./metadata"

```

Validate local files

```bash

asc migrate validate --fastlane-dir "./metadata"

```

This checks character limits and required fields.

Import updates

```bash

asc migrate import --app "APP_ID" --fastlane-dir "./metadata"

```

Quick Field Updates

Version-specific fields

```bash

# What's New

asc app-info set --app "APP_ID" --locale "en-US" --whats-new "Bug fixes and improvements"

# Description

asc app-info set --app "APP_ID" --locale "en-US" --description "Your app description here"

# Keywords

asc app-info set --app "APP_ID" --locale "en-US" --keywords "keyword1,keyword2,keyword3"

# Support URL

asc app-info set --app "APP_ID" --locale "en-US" --support-url "https://support.example.com"

```

Version metadata

```bash

# Copyright

asc versions update --version-id "VERSION_ID" --copyright "2026 Your Company"

# Release type

asc versions update --version-id "VERSION_ID" --release-type AFTER_APPROVAL

```

TestFlight notes

```bash

asc build-localizations create --build "BUILD_ID" --locale "en-US" --whats-new "TestFlight notes here"

```

.strings File Format

For bulk updates, use .strings files:

```

// en-US.strings

"description" = "Your app description";

"keywords" = "keyword1,keyword2,keyword3";

"whatsNew" = "What's new in this version";

"supportUrl" = "https://support.example.com";

```

For app-info type:

```

// en-US.strings (app-info type)

"privacyPolicyUrl" = "https://example.com/privacy";

"name" = "Your App Name";

"subtitle" = "Your subtitle";

```

Multi-Language Workflow

Export all localizations:

```bash

asc localizations download --version "VERSION_ID" --path "./localizations"

```

Translate the .strings files (or use translation service)

Upload all at once:

```bash

asc localizations upload --version "VERSION_ID" --path "./localizations"

```

Verify:

```bash

asc localizations list --version "VERSION_ID" --output table

```

Character Limits

| Field | Limit |

|-------|-------|

| Name | 30 |

| Subtitle | 30 |

| Keywords | 100 (comma-separated) |

| Description | 4000 |

| What's New | 4000 |

| Promotional Text | 170 |

Use asc migrate validate to check limits before upload.

Notes

Version localizations and app info localizations are different; use the right command and --type flag.
asc migrate validate enforces character limits before upload.
Use asc localizations list to confirm available locales and IDs.
Privacy Policy URL is in app info localizations, not version localizations.

More from this repository9

🎯

asc-release-flow🎯Skill

Streamlines iOS and macOS app releases by automating build uploads, TestFlight distribution, and App Store submission processes.

🎯

asc-id-resolver🎯Skill

Resolves App Store Connect IDs by translating human-friendly names to precise identifiers for apps, builds, versions, groups, and testers.

🎯

asc-cli-usage🎯Skill

Provides expert guidance for executing and designing App Store Connect CLI commands with best practices for flags, output, authentication, and command discovery.

🎯

asc-submission-health🎯Skill

Preflight and monitor App Store submission health, ensuring builds meet Apple's requirements and reducing review submission failures.

🎯

asc-testflight-orchestration🎯Skill

Orchestrates TestFlight distribution by managing beta groups, testers, builds, and release notes using Apple's App Store Connect CLI.

🎯

asc-build-lifecycle🎯Skill

Manages Apple Store Connect build lifecycle by tracking, finding, processing, and cleaning up builds across different platforms and versions.

🎯

asc-signing-setup🎯Skill

Configures iOS/macOS app signing assets like bundle IDs, certificates, and provisioning profiles using Apple's ASC CLI.

🎯

asc-ppp-pricing🎯Skill

Configures territory-specific subscription and in-app purchase prices using purchasing power parity (PPP) across different countries.

🎯

asc-xcode-build🎯Skill

Builds and exports iOS/macOS apps using xcodebuild, generating IPA or PKG files ready for App Store Connect upload.