Contents
An app store rejection costs time, pushes back launch dates and causes stress just before the finish line. Most rejections at Apple and Google Play have recurring causes: incomplete apps, missing test accounts, privacy disclosures that do not match the app or violations of payment rules. If you know these causes and check for them systematically before submission, you will usually get through on the first or second attempt.
How review works at Apple and Google
Apple reviews every new app and every update before release, combining automated checks with human reviewers. The basis is the App Review Guidelines, which are updated regularly. Google Play relies more on automated checks and policy enforcement, which can also take effect after publication, up to removing an app or suspending a developer account.
Apple's review is usually quick but can take longer before holidays or when questions arise. At Google, the first review of new accounts and apps may take longer; new personal developer accounts must also complete a closed test with a minimum number of testers before production access. Plan a deliberate buffer for your first launch.
The most common rejection reasons at Apple
| Reason | Guideline (Apple) | Typical example | Fix |
|---|---|---|---|
| Incomplete or buggy app | 2.1 App Completeness | Crashes, placeholder text, dead links, "coming soon" features | Thorough testing on real devices, submit only finished features |
| No test access | 2.1 | Login required, but no demo credentials provided | Provide a working demo account with sample data in the review notes |
| Too little functionality | 4.2 Minimum Functionality | The app is just a wrapped website without app-specific value | Use native features such as push, offline, camera or device integration meaningfully |
| Spam or copycat | 4.3 Spam | Many near-identical apps, e.g. one app per location | One app with a selector instead of many clones |
| Digital content without in-app purchase | 3.1.1 In-App Purchase | Unlocking digital content through your own payment system | Use Apple's payment system or carefully check applicable exceptions and regional rules |
| Privacy | 5.1.1 Data Collection | Missing privacy policy, unnecessary permissions, no account deletion | Justify permissions, offer account deletion in the app |
| Misleading metadata | 2.3 Accurate Metadata | Screenshots show features that do not exist | Align screenshots and description with the actual app |
| Login services | 4.8 Login Services | Only a third-party social login without a privacy-friendly alternative | Check current requirements and add a suitable login option |
Guideline numbering can change; the current version always prevails.
Typical issues on Google Play
- Data safety section does not match the app: embedded SDKs collect data not declared in the form. Review every SDK and its documentation.
- Sensitive permissions: background location, SMS, call logs or all-files access require justification and are only allowed for specific core features.
- Target API level: Google requires apps to target recent Android versions regularly. Outdated apps can become invisible to new users.
- Payment policies: Google also has its own billing rules for digital content.
- Account deletion: apps that allow account creation must offer deletion in the app and via a web link.
- Audience and content: apps targeting children are subject to additional requirements, for example regarding ads and SDKs.
Pre-submission checklist
- App tested on several real devices and OS versions, no crashes in the main flows.
- No placeholders, test text, debug menus or non-functional buttons.
- Demo account with sample data in the review notes, plus explanations of special features or required hardware if needed.
- Privacy policy linked in the app and the store; privacy disclosures at Apple and Google cover all embedded SDKs.
- Permissions requested only when needed, with clear explanation texts.
- Account deletion in the app if accounts can be created.
- Payment model checked against store rules for digital and physical goods.
- Screenshots, description and age rating match the actual app.
- Production backend reachable and stable during review.
A thorough beta test reduces the risk considerably; see beta testing with TestFlight and Google Play. You will find the full list of preparations in our app launch checklist.
What to do after a rejection
- Read the reason carefully: Apple usually names the guideline concerned and often adds screenshots. On Google, the Play Console points to the policy violated.
- Ask factually: if the reason is unclear, reply in the Resolution Center or via support. Misunderstandings can often be resolved without a new build, for example with a better demo account.
- Fix rather than work around: do not try to hide features from review. That only postpones the problem and can lead to more serious consequences.
- Appeal only for genuine errors: both platforms offer appeal processes. Argue concretely with the policy text.
- Document the lesson: record what caused the rejection so it does not happen again with the next update.
Special cases: WebView apps, subscriptions and AI content
Apps that are essentially a website in an app frame fail particularly often. Check in advance what real added value the app offers; our article on turning a website into an app has guidance. For subscription apps, reviewers look for transparent prices, clear terms and a visible note on how to cancel. Apps with user-generated or AI-generated content need reporting and moderation features and the ability to block users.
In our projects, store submission is part of the scope. You can get a fixed-price offer including publication through our offer wizard.
Agentic coding workshop for your team? From €799 net – request a quote by e-mailConclusion
App store rejections are rarely arbitrary; they usually result from avoidable gaps: unfinished features, missing test access, inconsistent privacy disclosures or payment models that do not fit the rules. With a fixed checklist, a proper beta test and honest store information you reduce the risk significantly. And if a rejection happens anyway: respond factually, fix the problem and learn from it for future updates.
Frequently Asked Questions
How long does Apple's app review take?
Many apps are reviewed within a few days, often faster. Before holidays, for new accounts or when there are questions it can take longer, so plan a buffer for your launch.
Why is my WebView app being rejected?
Usually for lack of functionality under guideline 4.2, when the app is just a website without additional value. Native features such as push notifications, offline use or device integration improve your chances significantly.
Do I have to use Apple's or Google's in-app purchases?
For digital content and features, generally yes; for physical goods and services consumed outside the app, no. Some regions now have different rules, which you should check before implementation.
Can I appeal a rejection?
Yes, both platforms offer appeal processes. It makes sense when you can show factually, with reference to the policy text, that the rejection is based on a misunderstanding.