asc-subscription-localization

Bulk-localize subscription and in-app purchase display names across App Store Connect locales.

1|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill asc-subscription-localization-omixec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-subscription-localization
Source: https://github.com/OMIXEC/all-in-one-swift-skills/tree/main/skills/asc-subscription-localization
Command: npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill asc-subscription-localization-omixec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting subscription and in-app purchase display names in App Store Connect requires clicking through every locale manually in the web UI, which is slow and error-prone for apps supporting dozens of languages. ## Core Features & Use Cases - Bulk Localization: Create or update display names and descriptions for subscriptions, subscription groups, and IAPs across all 39 App Store locales using the asc CLI. - API 4.4.1 Version-Scoped Resources: Resolves or creates PREPARE_FOR_SUBMISSION versions and uses v2 version-scoped localization endpoints, avoiding deprecated v1 commands. - Idempotent Updates: Lists existing localizations first, creates only missing locales, updates changed values, and skips unchanged entries. - Use Case: You launch a new subscription in 39 locales. Instead of editing each language in App Store Connect, run the bulk workflow to create every localization with one display name, then verify with a table listing. ## Quick Start Use the asc-subscription-localization skill to set the display name "Premium Plan" for my subscription across all App Store locales.

Frequently Asked Questions about asc-subscription-localization

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

FAQPage Schema
How do I bulk-localize subscription display names in App Store Connect?▼

Use the asc CLI version-scoped localization commands: list existing localizations for the subscription version, create missing locales with a name and non-empty description, then update changed entries by localization ID. Verify with a final list command.

How to update in-app purchase names across all App Store locales?▼

Resolve the IAP's PREPARE_FOR_SUBMISSION version ID, then run asc iap versions localizations create for each missing locale with a display name and description. Existing localizations are updated by their resolved localization ID instead.

Why does creating a subscription localization fail with an empty description?▼

Apple's live service rejects empty descriptions and --clear-description for subscription- and IAP-version localizations even though the API 4.4.1 schema permits JSON null. Every create requires a non-empty description of at least one character.

Can I use product IDs with version-scoped localization commands?▼

No. Version-scoped v2 commands require a version ID, which is distinct from the product, subscription, or group ID. List versions filtered by PREPARE_FOR_SUBMISSION state to resolve the correct version ID first.

What happens if a localization already exists for a locale?▼

Creating a duplicate localization fails. Always list existing localizations first, then update the resolved localization ID when values differ and skip locales whose values already match.