Localize your App Store listing
Import your App Store Connect listing into a project, translate it, and publish reviewed text into each App Store locale.
The App Store Connect connector is two-way. It reads your app's listing in its source locale, turns each field into a key in your project, and publishes reviewed translations back into each target App Store locale, creating the localization if it does not exist yet. It never writes your source locale.
What it translates
One connection covers one app. You choose which listing fields to translate:
| Field | App Store Connect surface |
|---|---|
name, subtitle | App information |
description, keywords, promotionalText, whatsNew, marketingUrl, supportUrl | The app version |
Only the fields you select become keys, and only those are ever written back.
Requirements
- Plan: Starter or above.
- Role: Admin of the project's workspace, or an Owner of its account.
- In App Store Connect: an API key. In App Store Connect, go to Users and Access, Keys, create a key, and download its
.p8private key file. Note the key's Key ID and the Issuer ID shown on the same page. - Your app's Apple ID: the numeric ID under App Information, General, Apple ID.
- Target languages added to your transglot project.
Connect
Open the CMS page
Open your project's settings, choose CMS, and pick App Store Connect in the CMS list.
Enter the app and key
| Field | What to enter |
|---|---|
| App ID | Your app's numeric Apple ID, for example 1234567890 |
| Key ID | The API key's ID |
| Issuer ID | The issuer ID from the Keys page |
| Source App Store locale | The App Store locale that holds your source listing, for example en-US. transglot only reads it |
| Private key (.p8) | Paste the whole contents of the .p8 file, from -----BEGIN PRIVATE KEY----- to -----END PRIVATE KEY----- |
Map your locales
Under Locale → App Store locale, enter the App Store locale for each target language in the project, for example fr-FR for fr. A language you leave unmapped is skipped when publishing.
Choose the fields
Under Content types, select listing. Under Translatable fields, select the listing fields to translate.
Connect, test and sync
Select Connect, then Test connection, then Sync from CMS to import the listing. The private key is stored encrypted and never shown again.
Publish translations back
Review the imported translations, then publish them with Publish to CMS, or turn on automatic publishing when a translation is reviewed. Only reviewed translations are published. Connect a content platform describes reviewing and publishing in full; it works the same way here.
Apple accepts changes only while there is something editable:
- Version fields (description, keywords, promotional text, release notes, marketing and support URLs) are written to the app version that is being prepared for submission.
nameandsubtitleare written to the app information that is editable with that version.
transglot checks this before writing anything: if the fields you publish have nowhere editable to go, the publish fails without writing any locale. Importing still works on a live app with no version in preparation.
Troubleshooting
The full message is "App Store Connect has no editable version. Create a new app version to publish store metadata (description, keywords, promotional text, release notes)." Create a new version of the app in App Store Connect, then publish again.
The full message is "App Store Connect has no editable app information. Create a new app version to publish the app name or subtitle." The app name and subtitle can only change alongside a new version. Create one, then publish again.
Check that the Key ID and Issuer ID belong to the .p8 key you pasted, that the key has not been revoked, and that it has access to the app.
It has no App Store locale under Locale → App Store locale, or none of its translations are reviewed yet.