Rejection Decoder
Home / Guidelines / 2.3.10

Guideline 2.3.10 rejection: Other platforms in metadata

What it means, why it happens, and how developers get through it.

Subject line you may see: Guideline 2.3.10 - Performance - Accurate Metadata

In one line: Your app or listing mentions Android, Google Play, or another platform.
Usual next move: Fix the listing, then replyMetadata issues can often be fixed on the product page without a new build. Change the fields, then reply listing exactly what changed.Based on how this guideline is usually resolved, not a prediction for your app.
Paste your rejection to check
On this page: CausesFixReplyReal casesQuestions

Common real causes

How to fix it

  1. Remove other platform names from every metadata field and localization
  2. Check in-app help and onboarding text too
  3. Reply listing each field you changed

What to put in your reply

Thank them and name Guideline 2.3.10.
Say exactly what changed, and in which version and build.
Give a numbered path the reviewer can follow.
Attach proof: screenshots or a screen recording.

The full fill-in-the-blanks reply for 2.3.10 is in the Rescue Kit.

Real cases: others who got 2.3.10

1 public case: 1 pending. Outcomes are what the developer posted.

PendingX · @imhslva · Oct 24, 2026

Rejected for mentioning Android in the description

Still waiting on round 2 as of Oct 25, per a follow-up post. The post does not name the guideline; 2.3.10 is our reading.

Questions developers ask about 2.3.10

What does a Guideline 2.3.10 rejection mean?

Your app or listing mentions Android, Google Play, or another platform.

Why do apps get rejected under Guideline 2.3.10?

The most common real causes: description says 'iPhone or Android'; screenshots or help pages show other platforms; in-app text references Google Play.

How do I fix a Guideline 2.3.10 rejection?

1. Remove other platform names from every metadata field and localization. 2. Check in-app help and onboarding text too. 3. Reply listing each field you changed.

Do I need a new build for Guideline 2.3.10?

Fix the listing, then reply. Metadata issues can often be fixed on the product page without a new build. Change the fields, then reply listing exactly what changed. This is how the guideline is usually resolved, not a prediction for your app.

How should I reply to App Review about Guideline 2.3.10?

Reply in App Store Connect. Thank the reviewer and name Guideline 2.3.10, say exactly what changed and in which version and build, give a numbered path the reviewer can follow, and attach proof such as screenshots or a screen recording.

Stuck on 2.3.10?

Do it yourself, faster

App Store Rejection Rescue Kit: the full decoder, 12 reply templates, Notes for Review templates, and a 60-point preflight checklist.

Get the kit, $12

Have it written for you

Send your rejection, get a reply drafted for your exact case. Kit buyers get $10 off.

AI-assisted, built on Apple's App Review Guidelines. Not a guarantee of approval. If we do not deliver within 24 hours, you get a full refund.

Reply service, $29

Related rejections

2.3 Accurate Metadata2.3.14 Creative assets1.5 Developer information

Source: Apple's App Review Guidelines, section 2.3.10, as revised October 16, 2026. Last checked . Always read the current official text. How we write these guides.