← Shop Fortune Insight, LLC · 2026-08-25

App Store Rejection for Incomplete zh-Hans Localization — Review 2.3.8 & 4.2.3

You submitted an iOS app or a metadata update with the China storefront enabled — and App Review sent it back. The note mentions incomplete localization, metadata accuracy, or copy that does not match what buyers see on the China App Store. That usually traces to an empty, machine-translated, or contradictory Simplified Chinese (zh-Hans) row — not a bug in Xcode. This page maps common rejection language to Connect fixes so you can resubmit with aligned fields. Operator guidance only — no approval guarantee, no ranking promise, not legal advice, and not investment advice. Seller: Fortune Insight, LLC.

Who this is for

Western indie iOS developers — US, EU, UK, Canada, Australia — who:

If you are still drafting your first zh-Hans row from scratch, start with the China App Store localization checklist instead — this page assumes Review already flagged a gap.

Which guidelines Review cites

Apple does not always quote guideline numbers in rejection email text, but localization-related holds often map to:

These are orientation labels, not legal interpretations. Read Apple's current App Store Review Guidelines and your exact Resolution Center note before you resubmit.

Common rejection patterns we see from indie teams

Decode your Review note — what to fix first

Open Resolution Center and copy the exact sentence. Match it to the fix column — order matters when you are racing a resubmit window.

"Localization appears incomplete" or "not sufficiently localized"

Treat the entire zh-Hans row as incomplete until every buyer-visible field has saved Chinese text: name, subtitle, description, promotional text, and What's New for the version under review. Add zh-Hans screenshot sets for each required device size — not only the iPhone 6.7" slot.

"Metadata does not match the app" or "misleading metadata"

Line up three sources: your en-US listing, your zh-Hans listing, and what Review sees on device. Remove claims present in only one language. If the app UI is English-only inside, say so honestly in zh-Hans description — do not imply full in-app Chinese if strings were not localized.

"Screenshots do not reflect the localized version"

Upload zh-Hans screenshot galleries or overlays that match the Chinese copy. English UI captures are acceptable only when copy accurately describes that limitation. Mixed galleries (Chinese title + English screenshot captions) often trigger a second hold.

"Promotional text / description not in the language of the storefront"

Scan every text field in the zh-Hans dropdown — promo text and What's New are easy to miss because they sit below the fold in Connect. A filled description with empty promo text still looks English-only on the live page header area.

Resubmit checklist before you click Submit again

  1. Resolution Center — reply with what you changed (field names, not vague "fixed localization")
  2. zh-Hans core fields — name, subtitle, keywords, description saved and within character limits
  3. Version-scoped fields — promotional text and What's New for the build under review
  4. Screenshots per localization — each device size under zh-Hans, not only en-US
  5. IAP display names — if your app monetizes, open Features → In-App Purchases → zh-Hans names
  6. Spot-check on device — China storefront account, compare product page to Connect; mismatch means Review will too
  7. Meaning parity — en-US and zh-Hans describe the same product; no extra promises in one language

Field order reference: China App Store localization checklist. Live page still English after approval? See China App Store still shows English.

What AppLocale delivers

When Review already rejected once, you need aligned copy fast — not another translation experiment:

Human rewrite from your live listing and Review note — not a machine translation dump. We improve clarity and search intent from your existing copy.

What AppLocale does not do

How it works

  1. Capture the note — copy your Resolution Center rejection text and list which Connect fields are empty or mismatched
  2. Checkout — pay $79 one-time on Stripe (link below). Seller: Fortune Insight, LLC.
  3. Send intake — reply from the email on your Stripe receipt with your App Store URL, current en-US copy, any existing zh-Hans paste, and the Review note verbatim
  4. Receive files — within 24 hours after we receive the items above, paste-ready zh-Hans fields arrive at your Stripe receipt email
  5. Paste, verify, resubmit — update Connect, upload zh-Hans screenshots if needed, reply in Resolution Center, and submit the version

FAQ

Why did App Review reject my app for incomplete Chinese localization?

If you enabled the China storefront or added a zh-Hans localization row, Apple expects that row to be complete and accurate — not empty, not obvious machine translation, and not contradicting your en-US listing or in-app experience. Review often cites Guideline 2.3.8 (metadata accuracy) or 4.2.3 (minimum functionality and sufficient localization) when title, subtitle, description, screenshots, or What's New still read as English-only or mismatched on the China product page.

What App Store Review notes mention localization problems?

Common themes include: metadata does not match the app experience in the selected locale; localization appears incomplete; screenshots do not reflect the localized version; promotional text or description is not in the language of the storefront; or the app is not sufficiently localized for markets where it is available. The exact wording varies — treat the note as a checklist, not a single field to patch.

Is machine-translated zh-Hans enough to pass App Review?

Often no. Reviewers compare your Connect fields to what buyers see on device. Raw Google Translate or ChatGPT paste frequently fails on meaning drift, character-limit overflow, keyword stuffing, or screenshot galleries that still show English UI. You need aligned, human-readable zh-Hans fields — not a literal word swap.

What should I fix before resubmitting after a localization rejection?

Audit the zh-Hans row end to end: name, subtitle, keywords, description, promotional text, What's New, screenshot sets per device size, App Preview captions, and IAP display names if your paywall appears in review. Confirm each field matches what the app actually does in Chinese. Submit a metadata-only version if the binary is unchanged, or a new build if in-app strings were part of the note.

What do I send after AppLocale payment?

Your live App Store listing URL, current English listing, any existing zh-Hans copy, the Resolution Center rejection text, target locale (zh-Hans), and your resubmit deadline. Reply from the email address on your Stripe receipt — we deliver to that Stripe email within 24 hours.

How much does AppLocale cost?

$79 one-time via Stripe checkout. No subscription. Seller is Fortune Insight, LLC.

Do you guarantee App Review approval or App Store rankings?

No. We improve clarity and alignment from your existing copy. Apple makes the final review decision. We do not promise approval, keyword position, search rank, or download growth.

What is AppLocale not?

Not legal advice on App Store Guidelines, not a machine translation dump, not in-app string localization, not icon or screenshot design, not paid ads, not ranking guarantees, not QuantRadar, and not investment advice. We do not invent reviews, ratings, or traffic numbers.

AppLocale — fix the zh-Hans row Review rejected

$79 one-time

Buy AppLocale on Stripe

Delivered within 24 hours after Stripe payment. After checkout, reply from your Stripe receipt email with your App Store URL, Review note, and existing listing copy.
No approval or ranking guarantees. Sold by Fortune Insight, LLC.