App rejection help guides

Guideline 4.3(a) spam rejection: what it means and how to fix it

Apple's 4.3(a) rejection says your app is too similar to other apps. Here is what reviewers compare, why honest apps get caught, and what to change before you resubmit.

Guideline 2.1 App Completeness rejection: how to find and fix the bug

Got 'The app exhibited one or more bugs' or 'Information Needed' under Guideline 2.1? Here's how to reproduce what the reviewer saw and what to send back.

Guideline 5.1.1(v) account deletion rejection: what Apple requires

If your app lets people create an account, Apple requires a way to delete it inside the app. Here's what counts, what doesn't, and how to reply.

Guideline 4.2 Minimum Functionality rejection: when your app looks like a website

Apple rejects apps that feel like a repackaged website. Here's what 'not sufficiently different from a mobile browsing experience' means and how to add real app value.

Google Play 'Invalid Data safety form': how to fix it

Google says your Data safety form doesn't match what your app collects. Usually an SDK is the cause. Here's how to find it and update the form.