Why Games Get Rejected From the App Store, and How Long Review Takes

App Store review normally takes 24 to 48 hours, though it stretches around major holidays and platform events. Google Play is often faster, sometimes hours, but can take longer for new developer accounts.

Rejection is normal. It is not a judgement on your game. Most rejections come from the same handful of causes.

The most common rejection reasons

The reviewer could not access the content. If your game has a login, a region lock, or content behind a code, the reviewer will hit that wall and reject. Always supply working demo credentials in the review notes.

Broken links. Support URL and privacy policy URL must load. A dead link is an instant rejection and an embarrassing one.

Inaccurate privacy declarations. You said you do not collect data, but your ad SDK does. Reviewers check this against what the binary actually does.

Placeholder content. Lorem ipsum, test buttons, debug menus, unfinished screens. Ship a finished build, not a nearly finished one.

Crashes on launch. Usually a device or OS version you did not test. Reviewers test on current hardware with the latest OS.

Misleading metadata. Screenshots showing gameplay that is not in the game, or a description promising features that do not exist. Show what you actually built.

Payment rules. Selling digital goods outside the store's payment system breaks the rules. Physical goods and services are different, but digital currency, unlocks, and cosmetics must use in-app purchase.

Gambling and loot mechanics. If your game has randomised paid rewards, you must disclose the odds. This gets checked.

How to make review go smoothly

Write thorough review notes. Explain what the game is, how to reach the main loop quickly, and include a test account. If something looks unusual, explain it before they ask.

Test on a real device running the current OS, not just a simulator.

Submit early in your week. A rejection on a Friday can cost you the weekend.

When you get rejected

Read the exact guideline they cite. Apple's rejections reference specific rule numbers and generally mean precisely what they say.

Fix only what they raised, then resubmit. Rebuilding half the game because you assume they meant something broader wastes days.

If you genuinely believe the rejection is a mistake, you can reply in Resolution Center and make your case. This works more often than people expect, but only when you are actually right and can explain why clearly.

Plan for it

Budget one rejection cycle into your launch timeline. If you have a hard launch date tied to marketing, submit at least two weeks early.

Teams that submit three days before a planned launch and treat approval as guaranteed are the ones sending apology emails.