App Store Rejection Reasons and How to Avoid Them

Most App Store rejections are not about the idea behind the app. They come from the build and the paperwork: crashes, placeholder screens, a missing demo login, a privacy policy that does not say enough, or an app that is really a website in a wrapper. Apple says that on average more than 40% of unresolved review issues fall under guideline 2.1, App Completeness. For a Dubai business, the other common rejections are account deletion, payment rules, and apps in regulated fields such as finance, health or crypto that are submitted by the wrong legal entity. Every one of these can be checked before you press Submit.

Key takeaways

• Apple’s 2025 App Store Transparency Report shows 2,093,244 rejections out of 9,100,620 submissions reviewed, about 23% of everything submitted.
• Performance problems such as crashes, bugs and incomplete metadata were cited 1,354,418 times, far more than any other section of the guidelines.
• Apps that wrap a website with little native function are rejected under guideline 4.2, and template apps sent in by an agency for a client can fail under 4.2.6.
• Banking, healthcare, gambling and crypto apps should be submitted by the licensed company itself, and Apple does not accept branches or trade names as the account holder.
• If an app lets people create an account, it must also let them delete that account from inside the app.
• A rejection can usually be fixed and resubmitted. In 2025, 387,087 submissions were approved after an earlier rejection.

What the numbers say about App Store rejection reasons

Apple publishes an annual transparency report, and it is the only primary source for how often apps fail review. The 2025 report, published on Apple’s legal site, counts each guideline section cited, and one submission can be rejected under several at once. So the section totals add up to more than the number of rejected submissions.

Two things stand out. Performance is cited more often than the next three sections combined, and that is the section a team controls most directly. Legal is second, and legal here mostly means privacy, data handling and licensing rather than anything exotic. Apple also says that on average 90% of submissions are reviewed in less than 24 hours, so a rejection rarely costs weeks. It costs a day or two per round, and the rounds add up when a launch date has been announced.

App completeness: the rejection you can almost always prevent

Guideline 2.1 asks for final versions with complete metadata and working URLs, tested on a device, with demo account details if the app has a login, and with the back end switched on. Apple’s own list of common issues under this heading is short: crashes and bugs, broken links, placeholder content and incomplete review information.

One issue we often see with Dubai projects is the staging back end. The build points at a test server that someone shuts down over the weekend, or the reviewer’s demo account was created on staging and does not exist in production. The reviewer opens the app, the login fails, and the submission comes back under 2.1. Nothing was wrong with the app. The environment was.

A second pattern is the region-locked feature. A delivery app that only serves addresses inside Dubai, or a clinic booking app that needs an Emirates ID number, may show an empty screen to a reviewer who is not in the UAE. Apple’s guidance is direct on this: if features need an environment that is hard to replicate, give the specifics in the App Review Information section, and be ready to supply a demo video. A sample address in Business Bay and a test ID that the back end accepts will save a round.

A practical pre-submission check:

1. Install the exact build you will submit on a physical iPhone running the current iOS version and go through every screen.
2. Log in with the demo credentials you will give Apple, against the production back end.
3. Tap every link in the app, including support, terms and the privacy policy.
4. Search the app and its metadata for “lorem”, “test”, “TBD” and sample prices.
5. Write review notes that explain anything location-based, hardware-based or invitation-only.

When your app is really a website

Guideline 4.2 says an app should offer features, content and interface that go beyond a repackaged website, and 4.2.2 adds that apps should not be primarily marketing material, web clippings, content aggregators or a collection of links. The exception is catalogs.

This is the rejection many Dubai SMEs meet first. A real estate brokerage, a restaurant group or a consultancy wants “an app” for the brand, and the quickest build is a WebView around the existing website. Apple reviews that as a website in a frame and usually rejects it. Adding a splash screen and a push notification permission does not change the outcome.

The fix is either to give the app a job that a website does poorly, or not to build an app. Saved searches with alerts for a brokerage, a loyalty card with order history for a restaurant, or document upload with status tracking for a business setup firm are native jobs. If the honest answer is that customers only need to read content and send an enquiry, a progressive web app gives them an installable icon without going through App Review at all.

Agencies should also know guideline 4.2.6. Apps created from a commercial template or app generation service are rejected unless the provider of the content submits them directly. A company that sells the same restaurant app shell to twenty Dubai restaurants, each under the agency’s own developer account, is the case this rule was written for. Guideline 4.3 on spam adds that multiple bundle IDs of the same app, such as one per branch or per emirate, should be combined into one.

Privacy, data and account deletion

Section 5 was cited 495,673 times in 2025. It covers privacy, intellectual property and licensing, and privacy is the part that trips up UAE business apps most often in our experience. Guideline 5.1.1 requires a privacy policy link both in App Store Connect and inside the app. The policy must say what data is collected, how and for what, confirm that third parties such as analytics and ad SDKs give the same protection, and explain retention, deletion and how consent can be withdrawn.

The gap we see most often is the SDK list. A marketing team adds an analytics SDK, a chat widget and an attribution tool late in the project, and the privacy policy was written before any of them. The App Privacy details in App Store Connect then disagree with what the binary does.

Three further rules catch UAE apps regularly:

• If the app supports account creation, guideline 5.1.1(v) requires account deletion inside the app, not only by emailing support.
• Apps may not require personal information unless it is directly relevant to the core function or required by law, so a mandatory mobile number and date of birth to browse a menu will be questioned.
• Permission prompts need purpose strings that explain the use clearly, and Apple suggests an example, such as location being used to show the nearest branch in Dubai Marina.

Apps that use a third-party or social login for the main account must also offer an equivalent login that limits data to name and email, lets people hide their email, and does not track them for advertising without consent. Guideline 4.8 exempts apps that use a government-backed electronic ID. In the UAE that is UAE PASS, which the telecoms regulator TDRA describes as the national digital identity for citizens, residents and visitors. An app that signs people in only with UAE PASS or with its own accounts does not need a second option. Guideline 5.1.2 now also asks apps to disclose clearly when personal data is shared with third-party AI and to get explicit permission first, which matters for any Dubai app built on a chatbot.

Payments: in-app purchase or your own gateway

Section 3, Business, was cited 283,820 times in 2025, the fastest-growing section in the report. The rule behind most of it is simple once it is stated plainly.

Two mistakes cause most of these rejections. The first is a digital subscription sold through a card form in the app, which Apple treats as avoiding in-app purchase. The second is the reverse: a services business that tried to charge for a physical booking through in-app purchase and was told to use a normal gateway. A fitness studio in JLT that sells both class bookings and on-demand videos needs two payment paths, and the review notes should explain which is which.

Guideline 3.1.1 also says purchased credits may not expire and that restorable purchases need a restore mechanism. That matters to loyalty-style designs where points are bought rather than earned.

Regulated apps and who submits them

Apple’s list of common issues includes “submitted by incorrect entity”. Guideline 5.1.1(ix) says apps in highly regulated fields, naming banking and financial services, healthcare, gambling, air travel and crypto exchanges, should be submitted by the legal entity that provides the service and not by an individual developer. Apple asks for partnership documents or authorisation to be attached in App Store Connect when the relationship is not obvious.

For UAE companies this raises two practical points. The first is the developer account itself. Apple’s enrollment page says an organisation must be a legal entity that can contract with Apple, that it does not accept trade names or branches, that it needs a D-U-N-S number, and that the website and work email must sit on the organisation’s own domain. The organisation’s legal name becomes the seller name on the App Store. A founder who opened an individual account years ago to test builds will need an organisation account before a regulated app goes live.

The second is the licence. A crypto exchange app must only be offered where it holds the relevant permissions, under guideline 3.1.5. For a virtual asset business based in mainland Dubai or a Dubai free zone, that is normally VARA, which regulates virtual assets across the emirate except the DIFC under Law No. 4 of 2022. Medical apps that claim accuracy face guideline 1.4.1, which asks for regulatory clearance documents where they exist and rejects apps that claim to measure things like blood pressure with phone sensors alone. VPN apps under 5.4 must come from an organisation and must supply licence information for any territory that requires one. If you are not sure whether your activity needs a licence in the UAE, settle that with your regulator or a lawyer before submission. Apple’s section 5 says compliance with local law is the developer’s responsibility.

Metadata, screenshots and the name

Guideline 2.3 covers the store listing, and it is cheap to get right. App names are limited to 30 characters. Keywords should describe the app, not borrow competitors’ names or stuff in pricing. Screenshots must show the app in use rather than only the splash screen or login page, and they must match the device type they are uploaded for.

For bilingual UAE apps, the listing should match what the app does. If the app opens in English with an Arabic toggle, screenshots in Arabic only can look misleading, and the reverse is also true. Apple lets you localise the listing per language, so use it. Guideline 2.3.6 asks for honest answers to the age rating questions, which matters for apps with user chat or user-generated content. If the app will need ongoing store work after launch, app store optimisation is a separate task from getting through review.

What to do after a rejection

A rejection message names the guideline. Read it literally, and work out first whether the problem is in the build, the metadata or the review notes, because each has a different fix.

• Reply in the App Review section of App Store Connect when the reviewer has misunderstood something, and attach a short screen recording.
• Fix and resubmit when the issue is real, and say in the notes what changed.
• Book a 30-minute App Review appointment over Webex, which Apple offers, when the guideline is ambiguous for your case.
• Appeal to the App Review Board only when you believe the app complies. Apple allows one appeal per rejected submission and asks for specific reasons.
• Request an expedited review for a critical bug fix or an event-linked launch, with the steps to reproduce the bug or the event date.

For bug-fix updates, Apple may offer to approve the current version and let you fix newly found issues in the next submission, provided there are no legal or safety concerns. Accepting that offer keeps a hotfix moving. If releases keep stalling, the cause is usually process rather than code, and it is worth putting a release checklist into your app maintenance and support routine.

If you are preparing a first submission, or an app has been rejected and the message is not clear, our mobile app development team can review the build, the listing and the review notes against the current guidelines before you resubmit.

Sources checked on 29 September 2026: Apple App Review Guidelines (last updated 8 June 2026), Apple’s App Review page, the Apple Developer Program enrollment page, the 2024 and 2025 App Store Transparency Reports, TDRA’s UAE PASS page and VARA’s About page. Guideline numbers and figures change, and this is general information rather than legal advice. Cover photo: Dubai Metro (29129193311) by Stefan Wisselink, via Wikimedia Commons (CC BY 2.0).