All Articles
guidelines5 minAug 20, 2026Updated on Aug 2026

How to Avoid Apple Rejections Under Guideline 2.3.10 (Rival Platforms & Copy-Paste Traps)

App Review Guideline 2.3.10 is the #1 cause of metadata rejections for cross-platform apps. Here is why it happens, how reviewers check, and how to fix it automatically.

Share Guide:𝕏LinkedIn
iPhone on sleek desk representing App Store Review Guideline 2.3.10 compliance
Photo byPatrick Wardon Unsplash

Key Takeaways (Executive Summary)

  • Apple Guideline 2.3.10 prohibits all mentions of competitor platforms (Android, Google Play, APK, Pixel, Samsung) in iOS metadata and screenshot frames.
  • Over 34% of first-submission rejections in Flutter/React Native apps stem from copy-pasting release notes or subtitles between store consoles.
  • Apple uses both automated regex scanners during upload and OCR text extraction on uploaded screenshot assets.
  • Pre-submission scanning with deterministic rule engines prevents submission delays and review queue resets.

What is App Review Guideline 2.3.10?

Apple's App Store Review Guidelines explicitly state under Section 2.3.10:

"Make sure your app's metadata and visual assets do not include references to other mobile platforms, such as Android, Google Play, Windows Phone, or competitor hardware."

While this rule sounds simple, it accounts for more than 34% of first-submission metadata rejections in cross-platform development studios using Flutter, React Native, or Unity.


Why Cross-Platform Studios Get Hit Most Often

When studios release an app on both Google Play and the App Store, copywriting is often drafted simultaneously. Common pitfalls include:

  1. Subtitle & Promo Text Copy-Paste: Phrases like "Also available on Android" or "Syncs with Google Play games" copied from marketing briefs.
  2. Device Hardware in Screenshots: Showing an Android device frame (e.g. Pixel or Galaxy punch-hole camera) in App Store screenshots.
  3. What's New Notes: Including patch notes mentioning "Fixed Android crash on Samsung S24".

How Apple Reviewers Detect Violations

Apple runs both automated string scanners during the pre-review ingestion phase and manual review inspections:

  • Regex string matching: Automated detection of keywords like android, google play, apk, samsung, galaxy.
  • OCR screenshot inspection: Text recognition inside screenshot mockups for competitor branding or UI buttons (e.g., "Sign in with Google Play Games").

Step-by-Step Fix Protocol

1. Deterministic Text Replacement

Never submit an App Store Connect update with terms referring to external stores. Replace references with neutral ecosystem terms.

2. Audit What's New and Version History

Reviewers check the localized release notes in every single storefront locale. Ensure shared release templates do not contain multi-platform changelogs.

3. Verify Screenshot Device Mockups

Ensure all screenshot mockups rendered in Figma or design tools use Apple hardware frames (Dynamic Island / iPhone 15/16 Pro geometry) without Android status bars or navigation pill bars.


Violations vs Compliant Copy

Context❌ Rejected Copy (Guideline 2.3.10)βœ… Compliant Copy (Approved)
SubtitleCross-platform iOS & Android trackerCross-platform universal mobile tracker
DescriptionSync progress with Google Play GamesCloud sync across all your mobile devices
What's NewFixed crash on Android 14 / Pixel devicesPerformance improvements and bug fixes
ScreenshotsMockups showing Android center punch-hole cameraiPhone Dynamic Island mockup frame

Audit your own app in seconds

Detect 2.3.10 rejections, keyword cannibalization, and Google Play policy violations before you submit.

Run free audit now

Frequently Asked Questions

What happens if my app gets rejected under Guideline 2.3.10?
Your submission status will change to 'Metadata Rejected'. You do not need to recompile the binary; simply edit the offending text or replace screenshots in App Store Connect and reply to App Review in Resolution Center.
Does Guideline 2.3.10 apply to What's New release notes?
Yes. In fact, What's New is the most common place where Android references slip through (e.g. 'Fixed Android crash'). Apple scanners check release notes on every single update.
Can I mention cross-platform cloud sync in my description?
Yes, provided you use ecosystem-neutral language such as 'Sync across all your mobile and desktop devices' rather than explicitly mentioning Android or Google Play.

More ASO Engineering Guides