asc-subscription-localization

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

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-subscription-localization-dustinober1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-subscription-localization
Source: https://github.com/dustinober1/sundee-fundee-ios/tree/main/SundeeFundeeApp/.agents/skills/asc-subscription-localization
Command: npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-subscription-localization-dustinober1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting subscription, subscription group, and in-app purchase display names for every App Store locale requires tedious manual clicking in App Store Connect. This Skill automates bulk creation and updating of localizations via the asc CLI, including the API 4.4.1 version-scoped v2 resources. ## Core Features & Use Cases - Version-Scoped Localization: Resolves or creates PREPARE_FOR_SUBMISSION versions for subscriptions, groups, and IAPs before localizing, following the zero/one/many match rule. - Bulk Locale Coverage: Creates or updates display names and descriptions across all 40 supported App Store locales, listing first to avoid duplicate-creation errors. - Safe Update Semantics: Distinguishes omitted values, non-empty strings, and JSON null, and enforces Apple's non-empty description requirement for subscription and IAP localizations. - Use Case: You launch a new subscription in 40 locales. Instead of editing each language in App Store Connect, run the bulk workflow to create every missing localization with a shared display name and description, then verify with a table listing. ## Quick Start Use the asc-subscription-localization skill to set the display name of my subscription to "Premium Plan" 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 App Store Connect subscription display names?▼

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 list again to verify. Each locale requires a separate create call since there is no bulk API.

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

Resolve the IAP's PREPARE_FOR_SUBMISSION version ID, list its localizations, then create missing locales or update existing ones by localization ID. Updates omit the description flag unless a new non-empty value is supplied.

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 different from the product, subscription, or group ID. Resolve the version first with the versions list command filtered by PREPARE_FOR_SUBMISSION state.

What happens if multiple PREPARE_FOR_SUBMISSION versions exist?▼

The workflow stops and requires an explicit version ID when more than one match is returned. Zero matches means create a version, one match means reuse that ID, and versions cannot be deleted once created.