asc-metadata-sync

To sync App Store metadata and localizations, you can export, download, and upload version-level and app-info data using the asc tools workflow. This synchronizes fields like descriptions, keywords, and promotional text across multiple locales.

Yes, you can migrate legacy Fastlane metadata by running the export, validate, and import commands. This migration process enforces canonical metadata fields to keep your app information up-to-date and compatible.

You can manage version localizations like description, keywords, what's new, supportUrl, marketingUrl, and promotionalText. It also handles app-info localizations including name, subtitle, privacyPolicyUrl, and privacyPolicyText.

The best way to validate metadata before uploading is to use the built-in validation step within the migration workflow. This enforces canonical metadata fields and guides you through correcting any structural inconsistencies before import.

No specific dependencies or components are required to run the metadata sync workflow. It operates independently to synchronize local files with App Store Connect using the integrated asc tools commands.

You should use the asc migrate workflow to automate the enforcement of canonical metadata fields across multiple locales. It prevents manual synchronization errors by standardizing the export, validation, and import processes for version and app-info localizations.