asc-subscription-localization

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

70|4|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/AlexW00/Zettel --skill asc-subscription-localization-alexw00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-subscription-localization
Source: https://github.com/AlexW00/Zettel/tree/main/.agents/skills/asc-subscription-localization
Command: npx skills add https://github.com/AlexW00/Zettel --skill asc-subscription-localization-alexw00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting subscription, subscription group, and in-app purchase display names for every App Store locale requires clicking through each language manually in App Store Connect, which is slow and error-prone for apps with many products. ## Core Features & Use Cases - Version-scoped v2 localization: Creates and updates localizations on API 4.4.1 version resources for subscriptions, subscription groups, and IAPs, avoiding deprecated v1 endpoints. - Bulk locale coverage: Lists existing localizations first, creates only missing locales, and updates resolved IDs across all 39 supported App Store locales. - Safe version resolution: Applies a zero/one/many rule when resolving PREPARE_FOR_SUBMISSION versions, creating versions only when none exist and stopping when multiple matches require an explicit ID. - Use Case: You launch a new subscription tier and need its display name set in all 39 App Store locales; the skill resolves the subscription version, lists existing localizations, creates the missing ones, and verifies the result. ## Quick Start Localize my subscription display name "Premium Plan" across all App Store Connect locales using the asc CLI.

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 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, list its localizations, then create missing locales or update existing ones by localization ID. Apple's service rejects empty descriptions, so every create needs a non-empty description value.

What is the difference between version IDs and subscription IDs in App Store Connect API 4.4.1?▼

API 4.4.1 gives IAPs, subscriptions, and subscription groups discrete version resources with their own IDs, separate from the parent product or group IDs. Version-scoped localization commands only accept version IDs, never product, subscription, or group IDs.

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 4.4.1 schema permits JSON null. Every create must include a description of at least one character.

Can I delete a subscription version created for localization testing?▼

No version delete command exists for IAP, subscription, or subscription group versions. Reuse the single PREPARE_FOR_SUBMISSION version instead of creating new ones, and do not assume deleting the parent cleans up versions.