The most common App Store rejection reasons are: an incomplete app or one that crashes during review, no demo account for the reviewer, an app that is just a wrapped website, privacy problems such as a missing privacy policy or no in-app account deletion, selling digital content without in-app purchase, and screenshots or descriptions that do not match the app. Most are avoided with thorough testing and a checklist before submission. If you are rejected, read the guideline number in the message, fix that issue and reply clearly in App Store Connect.
- why apps get rejected by the app store
- app store rejection reasons
- apple rejected my app what to do
- guideline 4.2 minimum functionality fix
- how to pass app store review first time
Why does apple reject apps? The short answer
Why apps get rejected by the App Store is less mysterious than many founders think. Apple reviews every app and update by hand against the App Store Review Guidelines, and most rejections fall into a few recurring groups: an incomplete or crashing app, an app that does not offer enough value, privacy problems, a payment method that does not fit the content type, or misleading store metadata. The good news: almost all of them can be avoided before you submit.
This guide explains each reason in plain language, with what it means for Gulf apps in particular, such as delivery, booking and store apps that use mada and Apple Pay. If you are still setting up accounts, start with publishing your first app to the App Store and Google Play.
The most common rejection reasons
| Reason | Approximate guideline | How to avoid it |
|---|---|---|
| The app crashes or has broken links or placeholder content | 2.1 App completeness | Test every screen on real devices and remove any 'coming soon' text or fake data |
| No demo account for the reviewer | 2.1 | Add a username and password, or a test phone number with a fixed code, in the review notes |
| The app is just a wrapped website | 4.2 Minimum functionality | Native screens, notifications, persistent sign-in and real mobile features |
| Accounts cannot be deleted in the app | 5.1.1 Privacy | A clear delete-account button in settings |
| Unexplained or unnecessary permissions | 5.1.1 | Ask for a permission when needed, with text that clearly explains why |
| Selling digital content through an external gateway | 3.1.1 In-app purchase | Use in-app purchase for digital content |
| Screenshots or description do not match the app | 2.3 Accurate metadata | Screenshots from the real app and an honest description with no competitor keywords |
| User-generated content with no reporting or blocking | 1.2 User-generated content | Filtering, a report button, user blocking and a contact method |
Incomplete apps and crashes: the number one reason
The reviewer opens your app like any new user. If it crashes, shows a blank screen, has a button that does nothing or an 'under construction' page, rejection is almost certain. Reviewers also often test on different devices and iOS versions, including iPad, even if you designed for iPhone.
- Test on a real iPhone running the latest iOS, and try a weak connection and no connection.
- Make sure every link works, including privacy policy, terms and support.
- Remove test products, lorem ipsum text and zero prices.
- If the app needs sign-in, give the reviewer a ready demo account with realistic data.
- If sign-in uses a phone number and OTP, set up a test number with a fixed code, because the reviewer will not receive an SMS on a Saudi or UAE number.
- If some features only work in certain cities, explain that in the review notes and provide a test address.
Minimum functionality: why wrapped websites get rejected
Guideline 4.2 asks that an app deliver a real app experience and value beyond a repackaged website. An app that opens your store's website in a frame, with its web menus and footer and no notifications or mobile features, is often rejected under this rule. Repeated 'template' apps that differ only in name and logo can also be rejected under the spam rule, 4.3, which matters for agencies publishing similar apps for several clients.
- The website as is inside a WebView
- Links that leave for the browser
- Nothing works offline
- Identical copies for different clients
- Bottom navigation and native screens
- Order or booking status notifications
- Persistent sign-in and Apple Pay
- Content and experience specific to each brand
For the different ways to turn a website into an app, read turn your website into an iPhone and Android app. In Fanann, real iOS and Android apps are built from the same conversation, sharing your site's data and adding mobile features.
Privacy and account deletion
Privacy is one of the strictest areas of Apple review. Check these points:
- A privacy policy at a public URL, inside the app and on the store page, explaining what you collect and why. Read how to write a privacy policy for a Saudi app.
- In-app account deletion: if the app lets users create an account, it must let them delete it from inside the app, not only by email.
- The privacy label in App Store Connect: answer accurately about the data the app collects, including any third-party services built in.
- A reason for every permission: 'We need your location to set the delivery address' beats generic or empty text.
- Ad tracking: if you track users across other apps and websites for advertising, you must ask permission through the App Tracking Transparency framework.
- Sign-in: if you offer third-party login such as Google, you may need to offer an equivalent privacy-focused option such as Sign in with Apple. Phone-number sign-in alone usually does not require it.
In-app purchase: when must you use it?
Many apps get caught here, and the core rule is clear:
- Digital content and in-app features such as course subscriptions, paid feature unlocks or virtual currency: you generally must use Apple's in-app purchase.
- Physical goods and services delivered outside the app such as orders, delivery, bookings and event tickets: paid through your own gateway, such as mada, Apple Pay, Tabby, Tamara or KNET, without in-app purchase.
- Do not add links that push users to buy digital content on your website to bypass Apple's system, except where current rules in your country allow it.
If your model is a digital subscription, read what it costs to publish on the App Store and Google Play to understand commissions before you set prices.
Pre-submission checklist, and what to do if you are rejected
- 1Full test
Every screen on a real iPhone, with a weak connection and offline.
- 2Demo account and notes
A ready account or test phone number with a fixed code, plus a short explanation of any feature that is not obvious.
- 3Privacy
Privacy policy, account deletion, permission texts and an accurate privacy label.
- 4Store metadata
Screenshots from the real app in Arabic and English, an honest description and the right age rating.
- 5If you are rejected
Read the guideline number in the message, fix that exact issue rather than something similar, then reply in App Store Connect explaining what changed. If the reviewer misunderstood, clarify respectfully with screenshots; you can also appeal through the official channels.
Review my app and prepare it for App Store review. Make sure that: no screen or button is broken and there is no placeholder text, a clear Arabic error message shows when the internet drops, a 'Delete my account' button in settings deletes the account and its data, an Arabic and English privacy policy page is available at a public URL, location, notification and camera permissions are requested only when needed with text explaining why, there is a reviewer demo account with a test phone number, a fixed verification code and sample orders, and payment goes through the payment gateway because we sell physical goods. Then write review notes in English explaining how the reviewer can test the app.
Try it in FanannNext step: print the reasons table in this article and go through it line by line with your app before you press submit.
Key takeaways
- Crashes, broken links and missing demo accounts are among the most common and most avoidable rejections.
- An app that only shows your website without mobile features risks rejection under the minimum functionality rule.
- Privacy comes first: a privacy policy, in-app account deletion and a reason for every permission.
- Physical goods and real-world services are paid through your gateway; digital content needs in-app purchase.
- The rejection message names the guideline; fix that exact issue and reply respectfully and clearly.
Frequently asked questions
What are the most common App Store rejection reasons?
Apple rejected my app. What should I do?
How do I fix guideline 4.2 minimum functionality?
Do I need Sign in with Apple in my app?
How long does App Store review take?
Ask your AI assistant about this
Copy this prompt into the AI assistant you use, then add the details of your own case.
I am reading this guide: “Why apps get rejected by the App Store, and how to avoid it” https://fanann.com/en/blog/app-store-rejection-reasons/ My question: why apps get rejected by the app store Use that page as a source and explain the answer step by step for my situation, tell me what to check before I start, and cite the page link.