Claims made in your app description, screenshots, or in-app content have to be accurate — no promising functionality that doesn't exist, and no fabricated reviews, endorsements, or statistics.
Why apps actually get flagged
Common triggers include claiming AI/ML capabilities the app doesn't actually have, or listing features in the description that were removed from the build before submission.
A real example
"Your app description or metadata includes false or misleading information about the app's functionality."
The short version, in more detail
Guideline 1.1.6 is about honesty in what an app claims to be and do. The description, screenshots and in-app text must not promise functions the app does not have, and apps must not invent reviews, endorsements or statistics. Pranks and joke apps that pretend to do something real, such as a fake lie detector or fake device scan, are commonly caught here.
What this guideline covers
Claims in the description, screenshots and in-app text about functionality.
Fabricated reviews, endorsements, awards or statistics.
Apps that pretend to perform something they cannot, such as scanning or detecting.
Capabilities described in the listing that are not present in the submitted build.
What usually triggers this rejection
Claiming AI or machine-learning abilities the app does not have.
A description that lists features removed from the build before submission.
A prank or novelty app presented as if it performs a real measurement or diagnosis.
Fake testimonials or ratings included in screenshots.
Claims of official affiliation or approval that do not exist.
How reviewers evaluate it
Reviewers compare the listing's claims with what they can actually do in the app.
They test the features that the description emphasises most.
They look for in-app text that implies capabilities beyond what the app delivers.
They are especially alert to health, security and measurement claims.
Common misunderstandings
A disclaimer buried in fine print does not offset a headline claim that is untrue.
Marketing language is still held to accuracy when it describes functionality.
Novelty apps are not exempt if they could mislead users into thinking the function is real.
Common questions
What if a feature is still in development?
The listing should describe what the submitted build actually does, not what is planned.
Do AI claims get extra attention?
Yes. Reviewers check whether the AI feature really exists and works as described.
Are testimonials allowed?
Real ones can be used, but invented reviews or endorsements are a violation.
Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current App Store Review Guidelines for the exact wording.
Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.