Shipping mobile apps that get approved
A checklist to avoid the most common App Store and Google Play rejections.
By the AdPlus Services team
A rejection from Apple or Google can push a launch back by days or weeks. Most rejections come from a familiar set of issues that are easy to prevent with a pre-submission check.
Complete, accurate store listings
- Screenshots that show the real app, at the required sizes
- A description that matches what the app actually does
- A working support URL and contact email
- Correct age rating answers
Privacy details that match reality
Both stores ask what data your app collects and why. Your answers must match the app and any third-party SDKs it includes, such as analytics or advertising tools. Publish a privacy policy and link to it from the app and the listing.
Permissions with a clear purpose
Only request the permissions you need, and explain why at the moment you ask. Vague permission messages are a common reason for rejection on iOS.
Account deletion
If users can create an account in your app, both stores now expect a way to delete it from within the app. Plan for this early, because it usually needs backend work.
Payments that follow the rules
Digital goods and subscriptions sold inside apps generally need to use the platform's in-app purchase system. Physical goods and services are different. Check the current guidelines for your case before building checkout.
A working demo account
If parts of your app require login, give reviewers working test credentials and notes on how to reach key features. A reviewer who can't get in will reject the build.
Stability on real devices
Crashes during review are an instant rejection. Test release builds on a range of real devices and OS versions, and use crash reporting from the first beta.
Treat this list as part of your release process, not a last-minute check, and most submissions go through first time.
