# Guideline 2.3.10: Android mentioned in the app > Rejected under Guideline 2.3.10 for mentioning Android or Google Play in screenshots, the description or the app? What to remove, and the reply. **Guideline 2.3.10 — Accurate Metadata: mentions of Android or other platforms.** Something in the app or the listing points to another platform: an Android status bar in a screenshot, a “Get it on Google Play” badge, or “also on Android” in the description. - App Store · Guideline 2.3.10. Accurate Metadata: mentions of Android or other platforms. - Interactive page: https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-10-other-platforms - Rejection explainer: https://capwr.app/free-tools/app-store-rejection-explainer - Last updated: 2026-10-14 ## What this rejection means Something in the app or the listing points to another platform: an Android status bar in a screenshot, a “Get it on Google Play” badge, or “also on Android” in the description. ## Why reviewers send it App Store listings and apps should be about the iPhone version. A web app’s footer with a Google Play badge, an Android screenshot, or “also on Android” in the copy are all treated as irrelevant third-party platform information. ## The message App Review sends ``` Guideline 2.3.10 - Performance - Accurate Metadata We noticed that your app or its metadata includes irrelevant third-party platform information. Specifically, your app’s screenshots include Android references. ``` The exact wording changes from one review to the next; the guideline number is what to look for. ## How to fix it 1. Remove Google Play badges, Android device frames and Android mentions from the screenshots, the description and What’s New. 2. Check the app itself: a website footer with store badges often ships inside a wrapped app. 3. Hide web-only links such as “Download the Android app” when the app runs on iOS. 4. Update the listing — and the build, if the app shows them — and resubmit. ## Fix it with Lovable, Bolt or Cursor If the app was built with an AI builder, paste this into it, then check the result on a phone: ``` When the app runs on iOS (Capacitor.getPlatform() === "ios"), hide Google Play badges, “Get it on Android” links and any other mention of Android. ``` ## What to reply in App Store Connect Replace the [brackets] with what you actually changed: ``` Guideline 2.3.10 — We removed every reference to other platforms from the screenshots, the description and the app’s [footer / about screen]. ``` ## Got a different message? Paste the whole rejection into the [rejection explainer](https://capwr.app/free-tools/app-store-rejection-explainer). It recognises this one and 26 others, in your browser — nothing is uploaded. ## Other App Store rejections - [App Store Guideline 4.3 Spam rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-3-spam) - [Guideline 4.2 Minimum Functionality rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-2-minimum-functionality) - [Guideline 2.1 App Completeness rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-app-completeness) - [Guideline 2.1 Information Needed: demo account](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-information-needed-demo-account) - [Guideline 4.0 Design rejection: sign-in in Safari](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-0-design) - [Guideline 2.3.3 Accurate Metadata: screenshots](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-3-screenshots) - [Guideline 2.3.8: app icon or name doesn’t match](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-8-app-icon) - [Guideline 4.8 Login Services: Sign in with Apple](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-8-sign-in-with-apple) - [Guideline 5.1.1(v): account deletion required](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-v-account-deletion) - [Guideline 5.1.1: permission purpose string](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-purpose-string) - [Guideline 5.1.1: sign-up required to use the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-sign-up-required) - [Guideline 5.1.1(i): privacy policy link missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-i-privacy-policy) - [Guideline 5.1.2: App Tracking Transparency](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-2-app-tracking-transparency) - [Guideline 3.1.1: digital goods without In-App Purchase](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-1-in-app-purchase) - [Guideline 3.1.2: subscription information missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-2-subscriptions) - [Guideline 1.5: support URL doesn’t work](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-1-5-support-url) ## Fixed it? Send the build back to App Review CapWrapp builds the fixed commit on GitHub’s Mac machines, uploads it to TestFlight, and sends the build you pick to App Review from one page — no Xcode. [Get started free](https://capwr.app/login). ## About CapWrapp CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)