How review actually works
When your app is submitted, a human reviewer at Apple installs it and uses it. Most reviews complete within 24–48 hours in 2026, but a rejection restarts the clock — and each round-trip can cost you days. Google Play review is largely automated and usually faster, but it has its own paperwork that trips people up.
The difference between a launch that takes three days and one that takes three weeks is almost always preparation, not luck.
The rejections we see most
1. Privacy disclosures that don't match the app
Apple requires "App Privacy" labels declaring exactly what data you collect, and every third-party SDK you include must ship a privacy manifest. We've had a submission flagged because an advertising SDK shipped a malformed privacy manifest — not our code, but our problem to fix. We now audit every SDK's privacy declarations before submitting.
2. Subscription rules (the infamous 3.1.2)
If your app sells subscriptions, Apple has exacting requirements: pricing must be unmistakable before purchase, terms and privacy links must appear in the right places, and a "restore purchases" path must exist. This guideline is one of the most common rejection reasons in the entire store — and it's entirely avoidable if you've built paywalls before.
3. The reviewer couldn't use the app
If your app requires an account, you must give reviewers a working demo login. If it depends on your backend, the backend has to be up during review. Obvious in hindsight; forgotten constantly.
4. It broke on iPad
Even iPhone-only apps run on iPad, and reviewers frequently test there. Camera orientation, layout, and permissions all behave differently on tablets — we learned this one with our own camera-heavy app and now test tablets before every submission.
5. Metadata mismatches
Screenshots showing features that don't exist, descriptions promising things the app doesn't do, or an app category that doesn't fit. Reviewers check.
Google Play is different, not easier
- The Data Safety form must match your actual data collection — mismatches get apps flagged months after launch.
- New personal developer accounts must run a closed test with real testers before production access, which can add weeks if you didn't plan for it.
- Google's pre-launch report auto-tests your app on real devices and surfaces crashes — read it before promoting a release, not after.
- Subscription products, tax settings, and store listings all live in a console that assumes you've done this before.
Our pre-submission checklist
- Every SDK's privacy manifest audited; App Privacy labels written to match reality
- Paywall reviewed against guideline 3.1.2, restore-purchases tested
- Demo account created and verified from a clean device
- Tested on iPhone and iPad, plus a spread of Android devices via the pre-launch report
- Screenshots, description, and category cross-checked against the build
- Backend monitored during the review window
What this means if you're hiring a developer
Ask any agency you're evaluating one question: "What apps have you shipped through App Store review — under your own name?" Reading the guidelines is not the same as surviving them.
We handle store submission end-to-end for every client app, under your accounts, because we've done it repeatedly for our own.