Guideline 1.2 — User-Generated Content
If users can post, message or upload, Apple requires a specific set of safety controls — and it checks that they exist, not that you intend to add them.
What the rejection usually says
Your app enables the display of user-generated content but does not have the required precautions in place.
Wording varies between reviewers; the substance does not.
Why it gets triggered
- No way to report offensive content from within the app.
- No block function for abusive users.
- No filtering of objectionable material before it appears.
- No stated commitment to act on reports promptly.
How to fix it
1.Add reporting to every piece of content
A report action on each post, comment, profile and message. One tap, no account needed to use it.
2.Let users block other users
Blocking must hide that user's content and stop them contacting the blocker.
3.Filter before publication
Automated filtering of objectionable text and imagery, plus a moderation queue you actually monitor.
4.Publish your terms and your response time
State that offensive content is not tolerated and that reports are actioned within 24 hours — then meet it.
A reply you can adapt
Short, specific, and stating what changed — reviewers read hundreds of these.
Thank you. This build adds all four requirements: per-item reporting, user blocking, automated filtering of text and images before publication, and a published commitment to act on reports within 24 hours. Reviewer steps are in the notes.
AppSubmit does this for your app, specifically
Paste the rejection and the decoder reads it against your actual listing, build and release history — then writes the fix plan and drafts the reply. It also watches your submissions, so the next rejection reaches you as a notification rather than a surprise.
Decode a rejection free