What an app store localization rejection actually is

An app store localization rejection means Metadata Rejected status under Guideline 2.3: some locale's title, screenshots, or description misleads reviewers. Read the App Review message, fix the flagged asset in every locale that carries it, then reply in App Store Connect. No new build is needed for metadata-only rejections, and most clear within one to three days after your reply.

Apple reviews each localization of your listing, not just the primary language. Section 2.3 of the App Review Guidelines, titled Accurate Metadata, opens with a plain rule: everything on the page, from privacy details to screenshots, must reflect the app's core experience. When one locale breaks that rule, the whole version flips to Metadata Rejected, and the fix happens in App Store Connect, not in Xcode.

Here's the passage worth quoting. An app store localization rejection lands as Metadata Rejected status, which Apple clears without a new build once every flagged locale reads clean. Open the App Review message in App Store Connect and note the guideline number plus the assets it names: 2.3.1 for claims the build can't support, 2.3.3 for screenshots that don't show the app in use, 2.3.7 for prices or keyword-stuffed captions, 2.3.10 for Android frames or store badges. Fix the flagged asset in all localizations that carry it, because a fix in English alone won't clear a problem that also sits in your German set. Re-export screenshots at accepted sizes with no transparency, rewrite translated titles inside character caps with no repeated terms, and strip prices, placeholder text, and third-party logos from each affected set. Then reply to App Review with what changed and where, locale by locale, stating the build is unchanged. Most metadata-only rejections clear within one to three days after that reply.

That status is good news disguised as bad news. A binary rejection sends you back to code, tests, and a new build. A metadata rejection keeps the same binary and asks for honest paperwork. Teams that treat it as a locale audit instead of a punishment usually ship within the week.

The 6 localization triggers behind most rejections

Trigger one is English screenshots in localized storefronts. You translated the description into ten languages but shipped the same English screenshots everywhere, or mixed English UI with translated captions in one set. Reviewers flag this as a localization mismatch under Guidelines 2.3.3 and 2.3.7, because the shopper reads one language and sees another. Our screenshot translation guide walks through drafting each locale set so captions and UI match.

Trigger two is a keyword-stuffed translated title. German and Portuguese titles run long, and teams cram three synonyms inside the 30-character cap to keep every term. Apple reads that as misleading metadata under Guideline 2.3, the same rule that catches English title stuffing. Pick one term per title, move the rest to the subtitle or the 100-character keyword field, and never repeat a term the title already holds.

Trigger three is prices or money claims inside localized screenshots. A caption that says "Only $2.99" misleads shoppers in markets where the tier costs something else, so Guideline 2.3.7 bans prices in screenshots outright. Describe what the app does and let the store show the price. Move sale or trial wording into promotional text or in-app events where it belongs.

Trigger four is other-platform imagery reused from a Google Play set. An Android frame, Android status bar, or "Get it on Google Play" badge trips Guideline 2.3.10, which bans names, icons, or imagery of other mobile platforms in App Store metadata. Keep separate screenshot sets per store with a naming rule in your design files, and audit every locale when you port a set across.

Trigger five is claims some locale makes that the build can't support. A translated description can promise a feature that shipped only in one market, or screenshots can show mocked UI from a redesign that never landed. Guideline 2.3.1 calls this out directly: don't promote content the app doesn't offer. Capture screenshots from the exact build under review and check each locale's claims against it.

Trigger six is placeholder or test data left in one locale. "Lorem ipsum" captions, a "John Doe" test account, debug banners, or a blank state that slipped through in locale number nine all read as unfinished under Guideline 2.1 and the fictional-data rule. Our localization QA guide gives you an ordered pass that catches these leftovers before reviewers do.

Why fixing one locale never clears the rejection

Apple's own instructions carry a note most teams skim past: make the metadata changes in all app localizations, selecting each one in turn. Reviewers check per locale, so a fix that lands in English while the German set still shows the old screenshots leaves the rejection in place. Launchshots states the rule bluntly: a fix in English alone won't clear a problem that exists in your German set too.

Run the fix as a sweep. List every locale your version ships in, open each one in App Store Connect, and apply the same correction: same new screenshots, same rewritten title, same stripped caption. Check the scaled sizes in Media Manager too, since iPad slots often carry their own copies of the offending set. Then diff each locale against the flagged message before you reply, so no straggler keeps the version red.

This sweep habit pays beyond the current rejection. The same pass catches keyword-field repeats across sibling locales, an untranslated "What's New" entry, and a promo-text line that still names last season's sale. Our mistakes roundup catalogs the full set of these listing-layer errors so the sweep covers them all.

How to reply to App Review after a localization rejection

Replies live in the App Review section of your app's page in App Store Connect, the area many developers still call the Resolution Center. Apple's status reference describes the loop in one line: read the message, edit the metadata, reply to the message. Keep your reply short and specific so the reviewer can verify it in one pass.

A reply that works reads like this: thanks for the review, we replaced the iPad screenshots in all six localizations with captures of the app running on iPad, the previous images were scaled iPhone screenshots, and the build is unchanged. Name what changed, name where, state the build is unchanged. Vague replies ("we fixed the metadata") invite a second round of questions.

If a reviewer could not find a feature your screenshots show, reply with the steps to reach it and add demo account details in App Review Information. If the reply round stalls, Apple offers 30-minute App Review appointments to talk through the guidelines before you resubmit, plus a formal appeal to the App Review Board with specific reasons the app complies. Fix and reply first in nearly every case. Appeals take longer than corrections, and screenshot or text issues rarely need one.

How App Store Localizer fits a rejection recovery

App Store Localizer (https://asolocalization.com) rebuilds the clean locale pack a rejection reply assumes. Paste a public App Store URL and it imports your title, description, icon, and screenshots through Apple's public lookup API. It translates the title, subtitle, description, and the 100-character keyword field per target locale, generates localized keywords from free heuristics over your listing, and re-renders screenshots with translated captions in iPhone 14 Plus 1284x2778 and iPad Pro 12.9-inch 2048x2732 sizes. Coverage runs to 20-plus target locales, from Japanese, Korean, and both Chinese scripts through German, French, Spanish, and Brazilian Portuguese down to Hindi, Thai, and Vietnamese. You download the finished assets or publish toward App Store Connect.

Prices are one-time per listing, which keeps a recovery cheap to run. Starter at 19.99 dollars covers 3 languages with each available screenshot. Global at 99.99 dollars covers all supported languages. No subscription, no per-seat fees. Two honest limits shape where the tool stops and your workflow starts. Output is machine-generated, so run a native speaker over each corrected market before you reply to review, starting with the title, screenshots, and any claim the reviewer quoted. Keyword ideas come from listing heuristics rather than paid search-volume data, so keep one term per title and let the keyword field carry the rest. The tool serves the store listing only, never the app itself.

Frequently asked questions

  • Do I need a new build if only my metadata was rejected? No. Metadata Rejected status clears through App Store Connect alone: read the App Review message, edit the flagged text or screenshots, and reply. Apple asks for a new build only when the rejection also covers the binary, so keep the build number untouched and say so in your reply. - How long does a Metadata Rejected status take to clear? Most metadata-only rejections clear within one to three days after your reply, since no code review is involved. Complex cases with several flagged locales can take longer if a straggler locale still carries the problem. Sweep every locale before you reply to avoid a second round. - Can Apple reject English screenshots in non-English storefronts? Yes. Translated descriptions paired with English-only screenshots trigger localization-mismatch flags under Guidelines 2.3.3 and 2.3.7. Each locale needs screenshots that match its language: translated captions over UI a local shopper recognizes. Mixed-language sets get flagged the same way. - Can I appeal an app store localization rejection? Yes, but fix and reply first. Appeals to the App Review Board suit cases where you believe the reviewer misread the listing, and they take longer than corrections. For screenshot or text issues, corrected assets plus a specific reply almost always clear faster than an appeal.

Paste your App Store URL at https://asolocalization.com today and rebuild every flagged locale in one pass. Draft corrected titles inside their caps, re-render matching screenshots per market, run the QA pass over each set, then reply to App Review with exactly what changed and where. Reviewers clear clean paperwork fast, and a listing that reads native in every locale rarely sees this email twice.