App Store 1.1 rejection: Objectionable content
By The Draftbit team · Updated
Sources checked
This guide is for iPhone and iPad apps with text, images, audio, video, or interactive content that Apple considers harmful or offensive.
Apple flagged your content, but “objectionable” doesn’t tell you which screen needs work. Guideline 1.1 covers several different problems, from discriminatory material to misleading features. We’d start with the numbered subrule and the reviewer’s example before changing your whole app.
Find the content Apple means
Follow the reviewer’s route through the submitted build, including content loaded from your server. Check search results, sample accounts, ads, and material uploaded by users. A clean home screen doesn’t settle a concern about what people can reach after signing in.
The pages below separate the specific rules. For example, 1.1.2 concerns violence, while 1.1.6 concerns false information and deceptive features. If the notice only says 1.1, ask Apple which content triggered the decision and include the screen or feature you believe it means.
Make the correction stick
Remove or redesign the offending material and check how it could return through imports, uploads, or remote configuration. If users supply the content, also work through user-generated content and its moderation requirements.
Test the same route with a fresh account. In your reply, identify the content changed and where Apple can verify it. An age rating alone doesn’t make otherwise prohibited material acceptable.
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Apple App Review guideline 1.1 Checked 22 September 2026