Xcode · App Store Connect

Localize your App Store listing with Xcode

Ask Xcode to take your listing into German, Japanese and Brazilian Portuguese. It writes the copy; MetaRun checks the 30-character name and subtitle, the 100-character keyword field, and stages each language as its own before and after.

Start Free Trial See pricing →

Setup checked October 2026 against Apple: extending and customizing agents, giving external agents access to Xcode

01 · Uplink

Connect Xcode once

01 · Add the MetaRun plug-in

In Xcode 27, open Settings, Intelligence, Plug-ins. Choose Add Plug-in, then Add from URL, and paste:

https://github.com/metarun/metarun-skills

02 · Or with one click

Opens Xcode's plug-in sheet with the repository filled in.

xcode://agent-plugin-clone?repo=https%3A%2F%2Fgithub.com%2Fmetarun%2Fmetarun-skills

03 · Sign in

Install MetaRun from the list, then click Sign in next to it. MetaRun opens in your browser; pick read-only or read and change.

04 · Ask the coding assistant

Claude Agent, Codex and Gemini in Xcode all get MetaRun's tools and its six workflow skills.

Attach build 312 to version 2.4 and tell me what blocks submission.

02 · Briefing

What Xcode handles here

An App Store listing is two sets of text per language. Name, subtitle and the privacy URL live on App Information. Description, keywords, What's New, promotional text and the support URL live on the version. Adding a language in App Store Connect means filling both, in the right places, inside limits that are counted differently per field.

Xcode handles the writing. MetaRun reads every language that exists, checks each field's limit before staging, adds languages that don't exist yet, and keeps a coverage map so a half-done job is visible.

03 · Preflight

Before you start

An editable version, so the version's text can change.
App Information open for edits if you're changing name or subtitle; apple_get_listing_editability says whether it is.
A list of target languages, or ask Xcode which ones your storefronts index.

04 · Execution

How it runs

01
Read the listing as it is
Xcode reads both text surfaces for every existing language, plus Apple's list of supported languages.
02
Write within the limits
Name and subtitle get 30 characters each, keywords 100, the description 4,000. The agent writes; MetaRun refuses anything over a limit at preview, with the count.
03
Stage per language
Each language becomes one or two previews (App Information and the version). New languages are created by the apply, no separate add step.
04
Close the gaps
Listing coverage shows which fields are still empty in which languages, so Xcode can finish the job instead of reporting it done early.

05 · Session

An example session in Xcode

The app ships in 12 languages. Make the App Store listing match those 12.

apple_list_supported_localesGerman, Japanese and Portuguese (Brazil) are supported and not on the listing yet.
apple_preview_set_app_info_localizationPreview: add German. Name 22 of 30 characters, subtitle 29 of 30.
apple_preview_set_version_localizationPreview: German description and keywords, 97 of 100 characters.
Xcode asks before running apple_apply_set_app_info_localization. You read the preview above and approve.
apple_apply_set_app_info_localizationGerman added. Apple created its other localization rows.
Xcode asks before running apple_apply_set_version_localization. You read the preview above and approve.
apple_apply_set_version_localizationApplied.
apple_get_listing_coverageGerman complete. Japanese and Portuguese (Brazil) still to do.

Illustrative: your apps, versions and numbers will differ. The tool names and their order are real.

06 · Tools

The MetaRun tools Xcode calls

Tool	What it does
apple_list_supported_localesread	Every listing language Apple supports, with its code.
apple_list_app_metadataread	Name, subtitle and privacy URLs per language.
apple_list_version_localizationsread	Description, keywords, What's New and promotional text per language.
apple_preview_set_app_info_localizationpreview + apply	Stage name and subtitle for a language, adding the language if needed.
apple_preview_set_version_localizationpreview + apply	Stage description, keywords and the rest of the version text.
apple_get_listing_coverageread	What's filled and what's empty, per language and field.
aso_cross_locale_planread	Which extra languages each storefront indexes, and the keyword room they add.
aso_lint_metadataread	Rulebook check on the copy before it's staged.

Each preview has an apply twin (the same name with apply instead of preview) that only runs with the confirm token from a fresh preview, and refuses if App Store Connect changed in between. MetaRun tools save to your MetaRun workspace only (studio projects, tracked keywords), never to Apple.

07 · Apple rules

What Apple enforces, and how MetaRun handles it

Two surfaces, two edit windows

Name and subtitle sit on App Information; the rest sits on the version. Apple locks each at different times, and apple_get_listing_editability says which is open right now.

Storefronts index more than one language

The US storefront indexes nine extra listing languages besides English (U.S.). Each adds a 30-character name, 30-character subtitle and 100-character keyword field Apple searches in that storefront, which aso_cross_locale_plan maps out.

Keywords are 100 characters, commas included

Spaces after commas waste characters, and words already in your name or subtitle are indexed anyway. The lint flags both.

A new language fills its own blanks

Adding a language makes Apple create that language's other localization rows. MetaRun keys the confirm token on the language rather than Apple's row id, so the second half of your change doesn't fail as drift.

08 · Comms

What to ask Xcode

Ask Xcode: The app ships in 12 languages. Make the App Store listing match those 12.
Ask Xcode: Pull the terms from our string catalog and use them in the Japanese listing.
Ask Xcode: Which App Store languages are we missing compared to the app's own localizations?

09 · Safety

How Xcode asks before a change

Xcode asks before an agent uses a tool it hasn't been allowed. Tools you've allowed are listed in Settings, Intelligence, under Permissions, where you can remove them. Leave MetaRun's apply tools off that list so every App Store change asks first; reads and previews are safe to allow.

Apple key stays on MetaRun, encryptedPreview before every writeRecorded, revertible from history

10 · FAQ

Frequently asked questions

How many languages can Xcode add?

Any of the languages Apple supports for listings. apple_list_supported_locales returns the current list with codes, and each language is staged as its own change.

Does MetaRun translate, or does Xcode?

Xcode writes the translations. MetaRun makes them land correctly: the right field, the right surface, inside Apple's limits, with a preview per language.

Can it localize keywords, not just translate them?

Yes, and it should. Direct translations of keywords often miss what people search for. Pair it with aso_suggest_keywords, which reads App Store autocomplete in that storefront.

What if I don't like one language?

Skip it at approval, or ask Xcode to redo it. After applying, every change is in your history and can be reverted from there.

How do I connect Xcode to App Store Connect?

In Xcode 27, add the plug-in from https://github.com/metarun/metarun-skills (Settings, Intelligence, Plug-ins, Add from URL) and click Sign in next to MetaRun. After that, ask for "localize your listing" in plain words and Xcode picks the MetaRun tools.

Does Xcode see my App Store Connect key?

No. Your App Store Connect API key stays envelope-encrypted on MetaRun's servers and is decrypted per request. Xcode holds a MetaRun token that you can revoke in Settings at any time.

More with Xcode

Xcode

Release notes

Write What's New from your changelog and stage it in every language.

Open

Xcode

ASO keywords

Find keywords from App Store autocomplete, track ranks, and lint your metadata.

Open

Xcode

Screenshots

Design, caption, translate and upload App Store screenshots from a prompt.