Guideline 2.3.10 Rejection: How to Fix Your Metadata and Resubmit
Guideline 2.3.10 tells you to keep App Store metadata focused on the iOS experience. The classic trigger is mentioning another platform — "Also available on Android!", a Google Play badge in a screenshot, or "works on Windows and Mac" in the description. It also covers irrelevant or misleading information stuffed into your name, subtitle, keywords, description or promotional text. Like all 2.3.x rejections, it's metadata-only and fast to fix.
What Apple's rejection email says
"Guideline 2.3.10 — Performance — Accurate Metadata. We noticed that your app or its metadata includes irrelevant information. Specifically, your app's description references Android. Next Steps: Please remove all instances of this information from your app and its metadata, including the app description, promotional text, screenshots and previews. Since your iTunes Connect metadata clearly does not pertain to the iOS experience, it would be appropriate to remove it."
Typical App Review wording for Guideline 2.3.10. Exact text varies per app.
Why apps get rejected under 2.3.10
Reviewers scan every metadata field, and 2.3.10 fires on content that isn't about the iOS app in front of them:
- Other-platform references. "Android", "Google Play", "Play Store", "Windows", "APK", cross-platform availability lists, or Google Play badges inside screenshots. This is the most common cause by far.
- Pricing in the description or screenshots. Statements like "only $4.99/month" are routinely flagged, because App Store prices vary by region and change over time, making the metadata inaccurate for many users. Keep pricing inside the in-app purchase configuration, where it localizes correctly.
- Irrelevant keywords. Competitor app names, trademarked terms, celebrity names or trending terms unrelated to your app in the keywords field, name or subtitle.
- Leftover boilerplate. Test notes, internal version comments, "beta" mentions or template text left in the description or What's New notes.
- Hidden references inside the binary. Occasionally the flag is in-app: UI or help text telling users about the Android version.
Note the phrasing in Apple's message: "your app or its metadata". Reviewers check both the App Store Connect fields and the app's own screens, and they routinely flag more than one location in a single rejection. Assume there are more instances than the one Apple quoted — the example they name is rarely the only one, and a partial cleanup is the most common reason a 2.3.10 bounces a second time.
Step-by-step fix
- Find every offending mention. The rejection names at least one location, but sweep all of them: app name, subtitle, description, promotional text, keywords, What's New, screenshots, app previews and the support URL page. Search for "Android", "Google", "Play", "Windows" and any price strings.
- Edit the fields in App Store Connect. Your app → the version page: description, promotional text and What's New are edited inline; keywords, name and subtitle are under App Information / the version's metadata section. Do this for every localization, not just English — localized descriptions are a common blind spot.
- Replace, don't just delete. Swap "available on iOS and Android" for copy about the iOS app's features. Swap "$4.99/month" for "subscription available" or nothing — the price is shown automatically on your product page from your IAP setup.
- Re-export flagged screenshots. If a screenshot contains a Play badge or a price, edit the image and re-upload it in App Previews and Screenshots.
- Check the binary if Apple said "app and its metadata". Remove in-app references to other platforms (settings screens and onboarding are typical spots); that requires a new build.
How to resubmit
Metadata-only fix: save the edited fields, then reply in the App Review thread stating the metadata has been updated, or resubmit the version for review. New build only if the reference was inside the app itself — then increment the build number, upload, select it and submit again. Turnaround for metadata resubmissions is usually a day or less. Don't bother appealing a 2.3.10 — with roughly 85% of appeals denied, deleting one sentence is the faster path by an order of magnitude.
How AscAuto handles 2.3.10 rejections
2.3.10 is a textbook case for AscAuto's automatic lane. It pinpoints the flagged strings across every metadata field and localization, generates the corrected copy, and applies it via the App Store Connect API when confidence is above your threshold — then resubmits. If the reference lives inside the binary, AscAuto tells you so explicitly and, with GitHub connected, proposes the string change as a pull request instead of pretending a metadata edit will pass.
FAQ
Can I mention my Android app anywhere at all?
Not in App Store metadata. Keep cross-platform marketing on your own website. Inside the App Store, every field should describe the iOS experience only.
Why does Apple care about a price in my description?
Because your description is global but prices are not — they differ by storefront, currency and over time. A hard-coded "$4.99" is wrong for most of the world, which makes the metadata inaccurate. Configure pricing on your IAPs and let the product page display it.
Will fixing only the English description be enough?
No. Reviewers check localizations, and rejections frequently bounce back because a German or Japanese description still contains the Android mention. Fix every localization in the same pass.
Is a new build required for 2.3.10?
Only if the flagged reference is inside the app itself. If it is confined to App Store Connect fields or screenshots, edit the metadata and resubmit the existing build.