App Store guidelines we debug first

Start with the guideline Apple cited. Each page covers symptoms, likely causes, and a next action — not a restatement of the public guideline text.

9 entries

1.1Safety — Objectionable Content1.1 is Apple judging what your app can produce, not only what it shows today. For generative apps, a template that could be used to create objectionable content is enough — even if the template itself looks harmless.
2.1App Completeness2.1 is Apple saying the review could not finish. The reviewer hit a wall — login, crash, empty feature, or a binary that does not match the listing — so they stopped.
2.3Accurate Metadata2.3 is a listing problem. The store page promises something the binary does not do, or the screenshots, name, or category mislead a reviewer about what they will open.
3.1.1In-App Purchase3.1.1 is about how digital value is paid for. If the app unlocks content, features, or subscriptions, Apple expects IAP — and a reviewer who can complete that purchase in sandbox.
3.2(f)Developer Program License Agreement 3.2(f) — Dishonest or Fraudulent Activity3.2(f) is not an App Review guideline. It is the Developer Program License Agreement clause Apple uses to remove an account for dishonest or fraudulent activity — most often because what users see is different from what review saw.
4.2Minimum Functionality4.2 is Apple saying the app does not do enough as an app. A wrapped site, a few static pages, or a utility that just launches Safari will land here.
4.3Spam4.3 is Apple grouping your submission with something they have already seen. The useful question is not “what is spam?” It is “what did they think you duplicated?”
4.8Login Services4.8 is narrow. If you offer a third-party social login, Apple expects Sign in with Apple on the same screen, with equivalent features, unless you qualify for an exception.
5.1.1Privacy5.1.1 is about what you collect and how you explain it. A permission you never use, a vague purpose string, or tracking without ATT is enough.