Guideline 2.3.10 — other platforms in your metadata
Do not name or show another mobile platform anywhere in your App Store metadata. Guideline 2.3.10 sits in Apple's accurate-metadata rules and covers names, icons and imagery of other mobile platforms in your app or its metadata.
For a React Native or Expo team this is almost always accidental, because the asset pipeline is shared. You rendered one set of marketing screenshots, recorded one preview video, and wrote one description for both stores. If any of those were produced on an Android device or mention Google Play, you have a 2.3.10 rejection waiting.
It is also one of the cheapest rejections to avoid and one of the most annoying to receive, because the fix is a metadata edit and the cost is still a full review cycle.
Where it actually hides
Screenshots rendered from an Android emulator. The most common cause by a distance. Tell-tales: three navigation buttons at the bottom, an Android status bar, a Material-style app bar, or a device frame that is visibly not an iPhone.
A preview video recorded on Android. Same problem, harder to notice because nobody re-watches their own preview.
The description. "Also available on Android," "Download on Google Play," "syncs with our Android app." All of it.
Keywords. People do put competitor platform names in the keyword field. It is indexed metadata and it is covered.
Promotional text. Frequently written in a hurry and the one field that can be updated without a submission — which means it is also the one that gets edited casually and least reviewed.
In-app upsell and settings screens. "Get it on Google Play," a Play badge in an about screen, a restore-purchases explainer mentioning Google. The guideline covers the app as well as the metadata.
The support or marketing URL. Your own website is fine and a Play badge there is normal. A support page linked from the listing that opens with another platform's branding is a different matter and has caused rejections.
What is normally fine
Non-mobile platforms. Referring to a web app, a desktop version or a browser extension is a different situation from naming a competing mobile platform.
Your own website carrying both badges. That is a website, not App Store metadata.
Genuine interoperability where Apple has approved specific interactive functionality. This is narrow and it is not a loophole for "we're on Android too."
The pre-submission check
# your listing copy — replace with wherever you keep it
grep -rniE 'android|google play|play store|samsung|pixel|huawei|galaxy' \
fastlane/metadata/ store/ 2>/dev/null
# strings compiled into the app
grep -rniE 'google play|play store|get it on google' \
--include='*.ts' --include='*.tsx' --include='*.js' --include='*.json' \
src/ app/ 2>/dev/nullThen look at every screenshot, at full size, and check the chrome. This is thirty seconds of work that prevents a multi-day cycle, and almost nobody does it because the screenshots "were already approved" — on the other store.
Why it costs more than it should
The fix is a metadata edit. The cost is a full review cycle: resubmit, wait one to three days, and hope nothing else surfaces. For a launch with a date attached, a 2.3.10 rejection is genuinely expensive relative to how trivial the cause is. The arithmetic of a rejection cycle.
It is also a deterministic, text-and-image check. There is no judgement in it — which makes it exactly the sort of thing that should be caught by a script before a build rather than by a reviewer after one. shipcheck scans listing metadata and in-app strings for other-platform references as part of its metadata pass, locally, before you submit. What it checks.
Questions and answers
What is App Store Guideline 2.3.10?
It is part of Apple's accurate-metadata rules and requires that you make sure your app description, screenshots and previews clearly indicate the app's features and functionality, and that you do not include names, icons or imagery of other mobile platforms in your app or metadata unless there is approved, specific interactive functionality.
Can I mention Android in my App Store description?
Generally no. Naming another mobile platform in your description, keywords, screenshots or preview video is what this guideline is about. Referring to non-mobile platforms such as a web app or a desktop version is a different situation and is normally fine.
Does a screenshot showing an Android phone violate 2.3.10?
Yes, and it is one of the most common ways cross-platform teams get caught. Screenshots must show iOS. A device frame with Android navigation buttons, an Android status bar, or Material-style UI chrome is enough to trigger it.
Where does this hide in a React Native project?
In assets generated once and reused across both stores. Marketing screenshots rendered from an Android emulator, a preview video recorded on an Android device, a support page linked from the listing that leads with a Play badge, and in-app upsell screens that mention Google Play.
What about a Google Play badge on my website?
Your own website is not App Store metadata and a Play badge there is normal. The risk is a page reachable from the listing itself, such as a support URL or marketing URL, that leads with another platform's branding.
shipcheck. “Guideline 2.3.10 — other platforms in your metadata.” Baker Ventures LLC, September 6, 2026. https://shipcheck.bakerventuresstudio.com/rejections/guideline-2-3-10-other-mobile-platforms/