Submitting an app to Google Play is a big milestone, but many apps face rejection during review. Google enforces strict policies to ensure apps are safe, functional, and valuable to users. This guide outlines the most common reasons apps get rejected, what’s often overlooked, and how to fix them.
Apps that crash, freeze, or behave unexpectedly are immediately rejected.
Fix: Test the app on multiple devices and Android versions. Address all crashes and fix any blocking bugs before submission.
Slow loading, unresponsive buttons, or laggy navigation can trigger rejection.
Fix: Optimize code and images, reduce large scripts, and avoid heavy work on the main thread.
Non-functional or placeholder links (Privacy Policy, Terms & Conditions, or Support) are not allowed.
Fix: Verify that all links are live, working, and lead to valid pages before submitting.
“Coming soon” pages or sample data are considered unfinished.
Fix: Ensure the app is fully functional and contains real product data before submission.
Apps that only wrap websites are considered low-value.
Fix: Replace web category links with proper in-app navigation. Make sure products are available and displayed correctly through Vajro.
Apps that exceed Play Store limits or drain battery/memory excessively can be rejected.
Fix: Compress assets, optimize performance, and test on lower-end devices.
Store listings that repeat the same keywords or phrases appear spammy and violate metadata quality standards.
Fix: Edit your description to remove repetitive words. Keep language natural, concise, and professional.
Grammatical errors or incomplete sentences reduce listing quality.
Fix: Proofread and fix grammar, sentence structure, and formatting before publishing.
Descriptions must clearly explain what your app sells and its purpose — not your business history.
Fix:
Avoid stories or personal history.
Don’t mention your app name inside the description.
Ensure the content focuses on what the user can do in your app.
Remove repetitive keywords.
Apps that imitate existing ones or offer minimal value are often rejected.
Fix: Add unique functionality, branding, or shopping experiences that make your app stand out.
Confusing layouts or inconsistent navigation may be rejected for poor usability.
Fix: Follow Android’s Material Design standards and maintain consistency across screens.
Descriptions, screenshots, or titles that misrepresent the app can result in rejection.
Fix: Use accurate visuals and text that truly reflect the app’s content.
Profanity or adult language in any description or text violates Google’s content policies.
Fix: Remove all profanity or explicit words from the app and listing.
Google Play restricts apps containing adult or sexually explicit content, including adult toys.
Fix: Remove all adult products, explicit images, or references from the store and app.
Google prohibits apps promoting or selling tobacco or CBD-related items.
Fix: Delete all tobacco, CBD, vape, or related product listings and references from both your app and its store description.
Violent, hateful, or illegal content leads to automatic rejection.
Fix: Review your catalog and remove any restricted materials.
Apps that only load a website with no added value are rejected.
Fix: Incorporate native Android features such as push notifications or local navigation to increase value.
Ads that interrupt user experience or appear deceptive are against policy.
Fix: Keep ads balanced and ensure they comply with Google’s ad placement guidelines.
Every app must display a Privacy Policy in both the Play Store listing and within the app.
Fix: Add a valid, accessible Privacy Policy link that matches your actual data practices.
Collecting or transmitting user data without justification or consent will result in rejection.
Fix:
Request only the permissions you need.
Encrypt sensitive data.
Explain how and why you collect information.
Tracking users without consent or bypassing Android’s privacy systems is not allowed.
Fix: Use clear consent prompts that comply with Google’s User Data Policy and regional privacy laws.
Using notifications to spam or advertise aggressively is prohibited.
Fix: Send only relevant, user-opted notifications and respect unsubscribe requests.
Google requires all digital purchases to use Play Billing.
Fix: For digital products or subscriptions, use Google Play Billing only.
Using logos, content, or code that you don’t own can block approval.
Fix: Ensure you have proper licenses for all materials.
Certain industries (e.g., finance, gambling, healthcare) need additional licensing.
Fix: Obtain required approvals or remove restricted features before submission.
Leaving out required details such as descriptions, screenshots, or content ratings will halt review.
Fix: Fill every field accurately in Play Console before submission.
If your developer name doesn’t match your store or brand, Google may flag it.
Fix: Ensure consistent naming across all metadata, or provide brand authorization documentation if needed.
Resubmitting without fixing flagged issues leads to suspension.
Fix: Review feedback carefully and make all requested updates before resubmitting.
Apps built with Vajro must have valid products visible for purchase.
Fix: In your Shopify dashboard, verify that all products are available for Vajro integration before submission.
Unfinished or testing builds are not accepted on the Play Store.
Fix: Submit only production-ready versions; use internal or closed testing tracks for beta.
Test thoroughly for crashes, lag, and compatibility across devices.
Verify that all metadata, screenshots, and links are correct and working.
Remove adult, CBD, or restricted content before submission.
Provide unique functionality and value not just a website wrapper.
Follow Google’s privacy, data, and advertising policies.
Maintain accurate store listings with proper grammar and formatting.
Double-check that your Privacy Policy and Terms & Conditions load properly.
Respond promptly and professionally to any reviewer feedback.
Google’s review process typically takes a few days but may be longer for apps in sensitive categories (finance, health, etc.). Submitting only when fully compliant avoids delays.
Monitor review progress in the Play Console. Statuses include Pending Review, Approved, Rejected, or Suspended.
If rejected, Google provides reasons and references. Address every issue before resubmission to avoid repeat rejections.
If you believe a rejection was unfair, submit an appeal via Play Console. Provide evidence and clear justifications.
You can release updates gradually (e.g., 10%, 25%, or 50% of users) to test stability before full rollout.
You may choose to go live immediately after approval or set a specific date. Updates may take several hours to propagate globally.
Post-approval updates that fix crashes or bugs are generally reviewed faster unless they introduce new features.
If your app faces issues not covered above or needs help with a rejection, visit https://support.google.com/googleplay/android-developer and use the “Contact Us” option to reach Google Play Developer Support. You can also access Policy and App Review feedback forms directly in the Play Console under Help → Contact Support.
