11 Common Reasons Games Get Rejected on Google Play and the App Store

11 Common Reasons Games Get Rejected on Google Play and the App Store

Few things are more frustrating than finishing a game and getting a rejection email. The good news is that most rejections and policy warnings come from a small set of repeat problems. This guide covers the most common reasons games are rejected or removed on Google Play and the App Store, and how to fix each one.

1. Intellectual Property Violations

The problem: using names, characters, logos, music or artwork from famous games, cartoons, movies or brands, or naming your game to look like a popular title.

The fix: use only original or properly licensed assets. Choose an original name with our Game Name Generator and check trademark databases before publishing.

2. Spam and Repetitive Content

The problem: publishing apps that are nearly identical to your own or others' apps, or minimal reskins of templates.

The fix: make every game meaningfully different: new theme, art, levels and features. Quality beats quantity.

3. Missing or Broken Privacy Policy

The problem: no privacy policy link, a link that does not load, or a policy that does not mention the data your SDKs collect.

The fix: generate a complete policy with our Privacy Policy Generator, host it at a stable public URL and link it in the store console and inside the app.

4. Inaccurate Data Safety or App Privacy Answers

The problem: declaring that no data is collected while using ad, analytics or crash SDKs.

The fix: list every SDK and answer based on their documentation. Read our Data safety guide.

5. Disruptive Ads

The problem: ads that appear unexpectedly during gameplay, cover buttons, cannot be closed or appear right after the app opens.

The fix: show interstitials only at natural breaks, keep banners away from controls and respect frequency limits.

6. Crashes and Broken Functionality

The problem: reviewers find crashes, blank screens or buttons that do nothing. Apple is particularly strict here.

The fix: test on several real devices, including older ones, and test every menu and purchase flow before submitting.

7. Misleading Metadata

The problem: screenshots that do not show the real game, exaggerated claims, keyword stuffing or irrelevant keywords.

The fix: show real gameplay, write honest descriptions and check keyword usage with the ASO Keyword Checker.

8. Outdated Target API Level (Google Play)

The problem: uploading a build that targets an older Android API level than Google Play currently requires.

The fix: update the target API level in Unity Player Settings or Android Studio, update SDKs and test again.

9. Children and Families Issues

The problem: selecting a child audience while using ad SDKs not certified for families, showing personalized ads to children or collecting personal data from kids.

The fix: answer target audience questions honestly and configure ads for child-directed treatment, or target an older audience if your game is not designed for children.

10. In-App Purchase Problems

The problem: purchases that do not work, missing "Restore Purchases" on iOS, or digital goods sold outside official billing.

The fix: use the official store billing systems, test purchases with test accounts and add a restore option. See our IAP guide.

11. Incomplete Information for Reviewers

The problem: reviewers cannot access features because they require a login or special steps.

The fix: provide demo credentials and clear notes in the review information section.

How to Respond to a Rejection

  1. Read the message carefully; it usually cites a specific policy.
  2. Fix the issue fully, not just the example mentioned.
  3. Reply or appeal politely with a short explanation of what you changed.
  4. Keep records of your changes in case the issue comes up again.

Following these rules from the start protects your developer account and saves weeks of back-and-forth with reviewers.

Keep Your Account Healthy Long Term

Avoiding rejection is not only about a single submission. Store policies change several times a year, so subscribe to policy update emails from Google Play and Apple, read them, and schedule time to adjust your games. Keep your SDKs updated, remove games you no longer maintain and respond quickly to any warning. A clean record makes reviews smoother for every future game you publish.

Pre-Submission Checklist

  1. All assets, names and music are original or licensed.
  2. The game is clearly different from your other published games.
  3. Privacy policy URL works and lists every SDK.
  4. Data safety and App Privacy answers match the policy.
  5. Ads appear only at natural breaks and never cover controls.
  6. The build targets the required API level and runs without crashes on real devices.
  7. Screenshots show real gameplay and the description is honest.
  8. In-app purchases work, and iOS has a Restore Purchases button.
  9. Reviewer notes include any login details or special instructions.

Running through this list before each submission prevents most rejections and keeps your developer account in good standing.

About the Author

AA
Abdullah Akasha
Project Manager, QA Lead & Editor at App Source Market

Abdullah is a computer science graduate who works with development teams to plan, test and ship websites and mobile projects. At App Source Market he builds the free developer tools and writes practical guides that help indie developers name, reskin, monetize and publish Unity and Buildbox games.

Our Research & Testing Process

Our guides are based on hands-on work with Unity, Buildbox and the Google Play and App Store consoles, and are checked against the official documentation at the time of writing. Each guide is reviewed for clear, step-by-step instructions and practical examples, and we update it when tools, store policies or requirements change.

Published: November 20, 2026Last Updated: November 20, 2026Meet Our Team →
Comments (0)
Login or create account to leave comments

We use cookies to personalize your experience. By continuing to visit this website you agree to our use of cookies

More