An app store submission checklist should cover five things: testing on real devices instead of only a simulator, accurate metadata and screenshots that match the live app, a working privacy policy and support URL, functioning core features like login and payment, and permission requests that map to something the app actually does — these five areas account for the large majority of App Store and Google Play rejections.
What are the most common app store rejection reasons?
Neither Apple nor Google is looking for reasons to reject a legitimate app — reviewers are checking that it works as described and doesn't mislead users. In practice, the same handful of issues come up again and again:
- Crashes or bugs found during review — the reviewer opens the app, taps through the main flows, and something breaks.
- Incomplete or inaccurate metadata — screenshots, the app description, or the icon don't match what the app actually looks like or does.
- A missing or unclear privacy policy — no privacy policy URL, or a policy that doesn't explain what data the app actually collects and why.
- Broken core functionality — a login screen that fails, a checkout that errors out, or a feature that's advertised but not actually present in the build.
- Guideline violations around permissions — asking for camera, location, contacts, or microphone access with no visible feature in the app that explains why.
What should you prepare before submitting your app?
Most avoidable rejections come down to not having the basics ready before you open the submission form. Work through this before you hit submit:
- Test on real devices, not just a simulator or emulator — some crashes, permission prompts, and performance issues only show up on actual hardware, and reviewers test on real devices too.
- Have a live privacy policy URL and a working support URL ready — both fields are required, and a broken link is an easy, fully avoidable rejection.
- Prepare screenshots that show what the app looks like right now, in its current build — not an older version, a redesign that hasn't shipped, or a mockup.
- Write an app description and title that describe what the app actually does, without claiming features that aren't in the current build.
- Set up a demo account or test credentials if the app requires login, so a reviewer can get past sign-in and actually test the app.
- Go through every permission the app requests and confirm each one is tied to a feature a reviewer can find and use.
How does the app store review timeline actually work?
Review is not instant, and it's not guaranteed to happen on a fixed schedule. Apple's App Store review typically takes somewhere in the range of a day or two, though it can run longer for a new developer account, a first submission, or an app with more complex functionality. Google Play review can range from a few hours to several days, especially for apps that trigger additional manual checks. Neither store publishes a guaranteed turnaround time, and both can take longer around major releases of their own operating systems.
Build in buffer time
Don't submit the week you need to launch. Treat review as a step that can take longer than expected — plan for it to happen at least one to two weeks before any announced launch date, so a rejection and resubmission cycle doesn't blow up your timeline.
What should you do if your app gets rejected?
A rejection is expected, common, and almost always fixable — it isn't a verdict on the app being fundamentally broken. Both stores tell you specifically why: Apple's Resolution Center message names the guideline and often the exact screen or flow involved; Google Play's rejection notice names the specific policy violated. Read that reason carefully, fix precisely what it describes, and resubmit. Most apps go through at least one rejection-and-fix cycle before approval, and reviewers see the same handful of mistakes daily, so a clear, specific fix is usually reviewed and cleared quickly on the second pass.
How is Apple's review different from Google Play's?
Apple's App Store review is done by a human reviewer who actually opens and uses the app, which is why broken flows and mismatched screenshots get caught reliably — and why the review is generally stricter on design and functionality guidelines. Google Play relies more heavily on automated checks plus policy review, with human review reserved mainly for flagged apps or specific categories; it tends to move faster for straightforward apps but is stricter about certain policy areas, like permissions and data safety disclosures. Preparing for the stricter of the two — treating every screenshot, permission, and flow as if a person will check it by hand — covers both.
Frequently asked questions
How long does Apple App Store review take?
Typically around one to two days, though it can take longer for a new developer account, a first submission, or an app with more complex review requirements. There's no guaranteed fixed turnaround time.
What is the most common reason apps get rejected from the App Store?
Crashes or bugs found during the reviewer's testing and metadata that doesn't match the actual app — inaccurate screenshots or descriptions — are consistently among the top reasons, along with unclear privacy policy disclosures.
Can I resubmit an app right after it gets rejected?
Yes. Once the specific issue in the rejection notice is fixed, the app can be resubmitted immediately — there's no waiting period or penalty for a first-time rejection.
Do I need a privacy policy even if my app doesn't collect personal data?
Yes. Both Apple and Google require a working privacy policy URL for every app regardless of what it collects — the policy should state plainly what data is or isn't gathered.