asc-metadata-sync

Sync and validate App Store metadata and localizations with ASC.

4|Updated Dec 8, 2019
One-click install
npx skills add https://github.com/Detrous/dotfiles --skill asc-metadata-sync-detrous
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-metadata-sync
Source: https://github.com/Detrous/dotfiles/tree/main/claude/skills/asc-metadata-sync
Command: npx skills add https://github.com/Detrous/dotfiles --skill asc-metadata-sync-detrous

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync and validate App Store metadata and localizations with ASC, including migration of legacy metadata formats, to ensure store listings stay accurate and compliant during updates and translations.

Core Features & Use Cases

  • Synchronizes version and app-info localizations with App Store Connect.
  • Migrates legacy metadata formats to the current ASC schema and validates character limits.

Quick Start

Run the ASC migrate workflow to export, validate, and import your app's metadata and localizations for a given app.

Frequently Asked Questions about asc-metadata-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync and validate App Store metadata with App Store Connect?

You can sync and validate App Store metadata with App Store Connect by running the ASC migrate workflow, which handles export, validation, and import steps for app IDs, localization files, and metadata attributes.

How do I migrate legacy App Store metadata formats to the current ASC schema?

Migrating legacy App Store metadata formats to the current ASC schema requires running the ASC migrate workflow to export legacy data, validate character limits, and import updated localizations into App Store Connect.

Can I update version localizations and app-info localizations across multiple locales?

Yes, you can update both version localizations and app-info localizations across multiple locales by using the ASC CLI to manage app IDs, localization files, and metadata attributes during the sync process.

Do I need the ASC CLI to manage App Store metadata and keep store listings accurate?

Yes, the ASC CLI is required to manage app IDs, localization files, and metadata attributes during the export, validate, and import workflow for keeping App Store listings accurate and compliant.

What is the best way to validate character limits for App Store localizations before importing?

The best way to validate character limits for App Store localizations is to run the ASC migrate workflow, which validates metadata attributes and localization files against the current ASC schema before importing.

Why does App Store metadata validation fail when updating localizations for new releases?

App Store metadata validation fails when updating localizations if legacy formats do not match the current ASC schema or if character limits are exceeded, which the ASC migrate workflow detects during the validation step.