Handling App Store Rejections
You finished your app, submitted it for review, and waited. Then the email came: "Your submission has been rejected." Your stomach drops. What now?
Take a breath. Rejections happen to everyone. Apple rejects about 40% of submissions. Google is more lenient but still catches plenty. The key is understanding why you were rejected and how to fix it.
Common Apple Rejection Reasons
Apple's App Store Review Guidelines are 30+ pages long. Here are the issues that trip up most developers.
Guideline 2.1: App Completeness
Your app crashed during review, showed placeholder content, or had broken features. Reviewers test your app and if something doesn't work, you're rejected.
Fix: Test thoroughly before submitting. If your app requires an account, provide demo credentials in the review notes. If features require specific conditions (location, hardware), explain how to test them.
Guideline 2.3: Accurate Metadata
Your screenshots don't match the actual app. Your description promises features that don't exist. Your app name is misleading.
Fix: Keep screenshots updated with each release. Don't oversell. If you changed features, update all metadata to match.
Guideline 3.1.1: In-App Purchase
You're selling digital goods outside Apple's IAP system. Or you're linking to an external purchase page. Apple wants their 30% cut.
Fix: Digital content (premium features, subscriptions, virtual goods) must go through IAP. Physical goods and services can use external payment. Know the difference.
Guideline 4.2: Minimum Functionality
Your app is too simple. A basic web wrapper with no native functionality. A marketing brochure for your business. Apple calls these "not useful."
Fix: Add real value that justifies being an app. If it could just be a website, make it more than a website.
Guideline 5.1: Privacy
You're accessing data you didn't ask permission for. Your privacy policy is missing or doesn't match your actual data practices. You're collecting data you don't need.
Fix: Only request permissions you actually use. Have a clear privacy policy. Update the App Store's privacy nutrition labels accurately.
Guideline 4.3: Spam
Your app is too similar to another app you submitted. Or too similar to existing apps with no differentiation.
Fix: Each app needs unique value. Don't template-spam the store with slight variations.
Common Google Play Rejection Reasons
Google's policies differ from Apple's. Here's what catches people.
Deceptive Behavior
App does something different than described. Hidden functionality. Misleading users about what they're downloading.
Fix: Be transparent about what your app does. No hidden features or behaviors.
Malware and Unwanted Software
Google's automated systems flagged something suspicious. Could be actual malware, could be false positive from obfuscation or unusual network patterns.
Fix: Don't include sketchy SDKs. If false positive, appeal with explanation of what the flagged code does.
Restricted Content
Sexual content, violence, hate speech, dangerous activities. Google has content policies and automated systems to enforce them.
Fix: Review Google's restricted content policies. If your content is borderline, err on the side of caution or implement age verification.
Impersonation
Using trademarks, logos, or branding that suggests affiliation with another company. "Unofficial X client" apps get hit with this.
Fix: Don't use other companies' trademarks. Make clear you're not affiliated. Get permission if possible.
Permissions
Requesting dangerous permissions (SMS, call log, location) without clear justification. Google has tightened significantly on this.
Fix: Only request permissions you demonstrably need. Fill out permission declarations explaining why each is required. Some permissions now require additional approval.
Reading the Rejection Message
Rejection messages are often frustratingly vague. But there are clues.
Look for:
- Specific guideline numbers: Both Apple and Google cite which rule you violated
- Screenshots: Sometimes they show exactly where the problem is
- Device info: What they tested on (maybe it only breaks on iPad)
- Binary vs metadata: Is the problem your app code or your store listing?
If genuinely unclear, you can ask for clarification. Apple has the Resolution Center. Google has appeal forms. Be polite and specific.
The Appeal Process
Sometimes rejections are wrong. Maybe the reviewer misunderstood your app. Maybe policies changed and your existing behavior is newly forbidden. Appeals exist.
When to Appeal
- You believe the rejection misinterprets your app
- You have legitimate justification for the flagged behavior
- The rejection message seems inconsistent with actual guidelines
When Not to Appeal
- You clearly violated the rule and hope to argue your way out
- You think the rule is stupid (that's not their problem)
- You haven't actually fixed anything
How to Appeal Effectively
- Stay professional: Frustrated rants don't help. Be calm and factual.
- Reference specific guidelines: Show you've read the rules and explain why you comply.
- Provide context: "This feature is for X purpose, which is why we need Y permission."
- Include evidence: Screenshots, videos, or documentation supporting your case.
Appeals take time. Apple's App Review Board may take a week. Google's escalations can take longer. Be patient.
Preventing Future Rejections
Read the Guidelines
Sounds obvious but most developers don't actually read them until after a rejection. Both Apple's App Store Review Guidelines and Google's Developer Program Policies are required reading.
Use Pre-Launch Reports
Google Play Console offers pre-launch reports that test your app on various devices automatically. This catches crashes and obvious issues before review.
Beta Test the Flow
Have someone unfamiliar with your app try the exact flow a reviewer would. Fresh eyes catch things you've gone blind to.
Document Everything
Use the notes field during submission. Explain how to test features, provide test accounts, note anything unusual. Reviewers have limited time. Make their job easy.
Stay Updated on Policy Changes
Both platforms update policies regularly. What was allowed last year might not be allowed now. Subscribe to developer news, follow policy blogs.
If You Keep Getting Rejected
Repeated rejections for the same issue signal a fundamental problem:
- You might not understand the rule correctly
- Your fix might not actually address the problem
- Your app concept might be inherently against guidelines
Consider hiring a consultant who specializes in app store compliance. Or pivot your approach entirely. Banging your head against the same rejection is a waste of time.
The Silver Lining
Rejections sting, but the review process exists for good reason. It keeps malware out, protects users, and maintains store quality. Your app has to meet a standard. That standard is why users trust apps from these stores.
Every rejection is a learning opportunity. You understand the rules better afterward. Your next submission will be cleaner. And when you do get approved, you know your app meets the bar.
The Bottom Line
Rejection isn't the end. It's a speed bump. Read the message carefully. Understand the actual violation. Fix it properly. Resubmit.
If you believe you're right, appeal professionally. If you're wrong, learn and adapt. Either way, you'll get through it.
Most successful apps have been rejected at some point. You're in good company. Now go fix whatever's broken and ship the thing.