LocalizeASO Logo LocalizeASO

App Store Connect setup

App Store Connect access is optional for BYO Agent review workflows. You can create metadata, keyword, screenshot, and pricing review jobs with a known app id, attach ASO keyword context, submit agent proposals, review diffs, and export local asc handoffs without storing Apple API credentials in LocalizeASO.

Connect App Store Connect when you want LocalizeASO to load live store data, list apps automatically, import locales, read current metadata/screenshots/prices, or run hosted submit convenience after human approval.

What works without ASC credentials

These workflows can run with an active LocalizeASO pass and a known app id:

  • BYO Codex/AI-agent review jobs for metadata, keywords, screenshots, and pricing.
  • ASO keyword inventory import, including Astro CSV import.
  • Agent proposal submission, reviewer feedback, approval receipts, and review history.
  • Figma approved-copy apply after a screenshot review is approved.
  • Local asc metadata/pricing handoff exports after approval.

Agents still cannot approve, apply, mark status, schedule pricing, or submit to App Store Connect. Those steps are human-only.

When to connect ASC

Connect App Store Connect when you want:

  • Automatic App Store app selection from your Apple account.
  • Live metadata, screenshot, release-note, and pricing reads.
  • Hosted LocalizeASO metadata, screenshot, or pricing submit workflows.
  • Dashboard submit and schedule jobs with status polling and per-locale/per-territory results.

Agent Pass users can keep credentials local and submit with asc, Transporter, or another human-run workflow instead.

Credentials for hosted ASC workflows

Create an App Store Connect API key in Apple:

  1. Open App Store Connect.
  2. Go to Users and Access -> Integrations.
  3. Create an API key.
  4. Use the App Manager role.
  5. Copy the Issuer ID.
  6. Copy the Key ID.
  7. Download the .p8 private key file.

Connect in LocalizeASO when needed

In the dashboard onboarding flow, enter:

  • Issuer ID.
  • Key ID.
  • The .p8 private key.

After saving, LocalizeASO checks the connection and loads the apps available to that key.

How credentials are handled

The dashboard stores App Store Connect credentials encrypted on the server. The private key is not kept in the browser. It is decrypted in backend memory only when a request needs to call Apple’s API.

App selection

After connection, the dashboard lists your App Store Connect apps. Select an app to access ASC-backed surfaces:

  • Metadata.
  • Screenshots.
  • Prices.
  • Release notes.

The app overview, ASO keyword inventory, and review queues can also be opened with a known app id when ASC is not connected.

Editable app states

Some App Store Connect states are read-only for hosted metadata updates. If a selected version is not editable, LocalizeASO shows a read-only state message and prevents unsafe hosted submits. BYO review and local handoff generation can still prepare proposals, but App Store submission remains a human-run step.

Troubleshooting

If connection fails, check:

  • The key has the App Manager role.
  • The Issuer ID and Key ID are copied exactly.
  • The .p8 file belongs to the same API key.
  • The app is accessible to the App Store Connect account that created the key.