Rejection Guides

Each rejection has a detailed guide to help you understand and resolve it. Here's what you'll find on each page.

Page sections

Metadata pills

At the top of every rejection page, you'll see colored badges showing the risk level (Low, Medium, or High), difficulty to resolve, and how many developers have reported this rejection.

Variation tags

Some rejections have common variations — different wording or contexts for the same underlying issue. These appear as tags below the metadata pills, helping you confirm you're looking at the right guide.

Our Take

A plain-language explanation of what this rejection means, why Apple or Google flags it, and common scenarios that trigger it.

Resolution Guide

Numbered steps you can follow to fix the issue. Each step includes a title and detailed instructions.

Example Email

A styled mockup of the rejection email you likely received, so you can confirm you're looking at the right guide.

Appeal Callout

When a rejection is commonly appealed successfully, you'll see a callout box with guidance and a link to the appeal generator.

Before & After

Side-by-side comparisons showing what not to do versus the correct approach, so you can see the fix visually.

Community Solutions

Solutions contributed by other developers who resolved this rejection. You can upvote helpful solutions or mark them as "worked for me" to help others.

Risk and difficulty levels

Risk indicates how likely this rejection is to delay your release. Difficulty reflects how complex the fix typically is. Both are based on community data and editorial review.