Guideline 2.3.10
Guideline 2.3.10 - Accurate Metadata: References to Other Mobile Platforms
Our Take
Apple is rejecting your app because it contains references to other mobile platforms in the app itself, its metadata, or its screenshots. This includes mentions of Android, Google Play, Windows Phone, or any non-Apple platform. Apple does not want their store to serve as advertising for competitors. This rejection most commonly hits cross-platform apps where developers forget to remove Android-specific references. Common triggers include: (1) screenshots showing Android UI elements (back button, navigation bar, status bar icons), (2) the app description mentioning 'Also available on Android' or 'Download on Google Play', (3) in-app links or buttons directing users to the Google Play Store, (4) using Android-style UI components like the Material Design floating action button, and (5) using the terms 'Google Play' or 'Android' anywhere in the binary or metadata. The fix is straightforward but requires thoroughness. Developers often fix the obvious references but miss subtle ones -- like a 'Share' feature that generates a message containing a Google Play link, or a help page loaded from a web server that mentions Android.
Resolution Guide
Search the codebase
Do a project-wide search for: 'Android', 'Google Play', 'Play Store', 'Windows Phone', 'Samsung', and any platform-specific terms. Check strings files, HTML content, and embedded web pages.
Update App Store metadata
Remove platform references from: description, What's New, promotional text, keywords, and any localized versions.
Retake screenshots on iOS
If your screenshots were captured from an Android build or show Android UI elements, retake them on an iPhone or iPad. Pay attention to the status bar, navigation patterns, and system UI.
Check share functionality
If your app generates share links, verify the share text doesn't include Google Play links. Use a smart link service that redirects to the appropriate store.
Audit web-loaded content
If your app loads content from your website (help pages, FAQs, terms of service), check those pages for platform references. Use conditional rendering or separate mobile-optimized pages.
Check push notification templates
If your backend sends push notifications, verify the templates don't include cross-platform references.
Prevention
Example Rejection Email
Before & After
App description: 'SyncNote keeps your notes in sync across all devices. Also available on Android and Google Play!' Screenshot shows Android navigation bar at bottom.
App description: 'SyncNote keeps your notes in sync across all your Apple devices -- iPhone, iPad, and Mac.' Screenshots captured on iPhone 15 Pro showing iOS native UI.
What changed: Remove all competitor platform references. Reframe cross-device sync as Apple ecosystem sync in the iOS listing.
Community Solutions · 0
Sign in to share your solution.
More Guideline 2 (Performance) rejections
- Guideline 2.1 - App Completeness: App Crashes During Review
- Guideline 2.1 - App Completeness: App Requires External Hardware Not Provided for Review
- Guideline 2.1 - App Completeness: Crashes on Launch
- Guideline 2.1 - App Completeness: Demo Account Not Working
- Guideline 2.1 - App Completeness: IAP Products Not Found in Binary
- Guideline 2.1 - App Completeness: Missing App Icon