App Store
Metadata
Open /dashboard/apps/<projectId>/metadata for an app imported from App Store Connect. The editor reads the current metadata from Apple and lets you switch between available localizations.
Edit a localization
The editable fields are title, subtitle, keywords, promotional text, description and what's new. Select a locale, make changes and review the field counters and validation messages.
The keywords field is measured in UTF-8 bytes. Its 100-byte budget is not necessarily 100 visible characters. The editor also flags issues such as empty terms, duplicates and repeated words across metadata fields.
Keyword suggestions are generated from the supplied candidates and current metadata. Applying a suggestion changes the editor's draft. It does not publish anything. See Keywords to collect and evaluate candidates first.
Publish reviewed changes
Publishing sends only fields that differ from what you loaded. AppNorth validates the resulting localization, rereads Apple's values and checks the expected values for fields being changed. Authorized dashboard managers can publish when the app has an editable version and workspace access permits it.
This updates metadata in App Store Connect. It does not submit a build for review or release an app version.
Resolve a conflict
| Result | Meaning | Next step |
|---|---|---|
READ_ONLY | No editable version is available | Prepare an editable version in App Store Connect, then reload |
LOCALE_NOT_FOUND | The selected localization is unavailable | Reload and select an existing localization |
STALE | A changed field no longer matches what you loaded | Reload Apple's latest values and reapply the intended edit |
INVALID_METADATA | The resulting content fails validation | Fix the highlighted fields |
PARTIALLY_PUBLISHED | Some fields were saved but a later write failed | Reload and inspect which values reached Apple before retrying |
A publish operation can span app-info and version-localization writes. Do not treat a partial failure as an automatic rollback. The server records publish outcomes for audit.
Demo metadata is stored in memory and does not reach Apple. For agent workflows, use the preview and expected-value contract in MCP.