Why Apps Get Rejected from the App Store, and the UAE-Specific Causes

The guideline numbers behind most App Store rejections, plus the UAE layer that delays local launches: regulated apps must be submitted by the licensed entity, not by your agency or your founder.

KB

Karim Ben Salah

Tech Analyst & Researcher

October 20, 2026 13 min read

Development

Why Apps Get Rejected from the App Store, and the UAE-Specific Causes

Rejection is not a disaster. Most apps get rejected at least once, and a rejection usually costs a day or two rather than a release. What it does cost is certainty, and that is expensive when a launch date has been promised to a client, a board or a marketing campaign that already has media booked.

Apps built for the UAE face the usual rejection reasons plus a second layer that catches local teams repeatedly: Apple requires apps in regulated categories to be submitted by the licensed entity, and it requires compliance with local law in every region where the app is available. That intersects with UAE licensing in ways that turn a review question into a six-week company formation problem.

This guide covers both layers — the ordinary causes with the guideline numbers attached, and the ones specific to building for this market — plus what to do when it happens. Guideline numbers below are quoted from Apple’s App Store Review Guidelines at the time of writing; Apple revises them regularly, so check the current text before relying on a number.

The short answer

Most rejections come from a small set of causes, and almost all of them are avoidable before you submit.

Cause Guideline The fix
Reviewer cannot get past your login 2.1(a) Supply a working demo account and switch your backend on
Crashes, bugs or dead links 2.1 Test on the oldest OS and device you claim to support
Screenshots or description do not match the app 2.3 Use real screenshots from the build you submitted
It is a website in a wrapper 4.2 Add native capability, or ship a web app instead
Selling digital content outside Apple’s system 3.1.1 Use in-app purchase for anything unlocked inside the app
No privacy policy, or no way to delete an account 5.1.1(i), 5.1.1(v) Link the policy and build account deletion in-app
Social login without a private alternative 4.8 Offer an equivalent privacy-preserving login option
Regulated activity, wrong submitter 3.2.1(viii), 5.1.1(ix) Submit from the licensed entity’s developer account
The last row is the one that delays UAE launches by months rather than days.

The ordinary rejections

Nobody could open your app

Guideline 2.1(a) asks for submissions to be final versions, and explicitly tells you to “include demo account info (and turn on your back-end service!) if your app includes a login”. Both halves of that catch people. A reviewer hits a login wall with no credentials, or the credentials work but the staging backend was switched off for the weekend.

If your app needs an Emirates ID, a UAE mobile number for OTP, or an invitation from an administrator to show anything, the reviewer cannot proceed. Provide an account that bypasses those gates, and say so in the review notes. If your OTP arrives by WhatsApp rather than SMS, the reviewer still needs a way in. Apps with role-based access need one account per role, with a note explaining which is which.

Metadata that oversells

Guideline 2.3 requires that metadata “accurately reflect the app’s core experience”. Screenshots from a design mockup rather than the build, a description promising features behind a future flag, or a keyword list naming competitors all fall foul of it. For bilingual apps, the Arabic listing must describe the same app as the English one — localised listings are reviewed too.

A website with an app icon

Guideline 4.2 says an app “should include features, content, and UI that elevate it beyond a repackaged website”. This is the single most common rejection for small business apps in this region, because the brief was often “we need an app” rather than “customers need to do this on their phone”.

If the app genuinely is your website, the honest options are to add something native — and note that starting from a proven app template does not exempt you, since 4.2 is judged on what the finished app does — push notifications, offline access, camera, location, wallet passes — or to ship a progressive web app and skip the store entirely. Our product strategy sessions exist partly to settle that question before anyone writes code, and the design work follows from the answer.

Payments in the wrong place

Guideline 3.1.1 requires in-app purchase to unlock “features or functionality within your app”, listing subscriptions, in-game currency, premium content and full-version unlocks. Physical goods and real-world services are different: a delivery order, a hotel booking or a salon appointment can and should use your own payment stack.

This catches UAE businesses selling digital subscriptions who assumed they could charge through a local gateway. If you sell access inside the app, Apple’s commission applies — which is a pricing decision for any subscription product, not just a technical one. If you sell something delivered in the real world, it does not — which is why commerce apps here mostly keep their existing gateways.

Privacy gaps

Guideline 5.1.1(i) requires a privacy policy link both in App Store Connect and inside the app. Guideline 5.1.1(v) is the one teams forget: “If your app supports account creation, you must also offer account deletion within the app.” Not a support email, not a web form — in the app. It is a small build task and a reliable rejection when missing.

Guideline 4.8 adds that an app using a third-party or social login must also offer an equivalent option that limits data collection to name and email and lets users keep their email private.

The UAE-specific layer

Section 5 of the guidelines is unambiguous: “Apps must comply with all legal requirements in any location where you make them available… it is your responsibility to understand and make sure your app conforms with all local laws”. Apple does not adjudicate UAE law, but it does require evidence that you are allowed to do what your app does.

Regulated categories must come from the licensed entity

Guideline 3.2.1(viii) states that apps “used for financial trading, investing, or money management should be submitted by the financial institution performing such services and must have necessary licensing and permissions in the locations where you make them available.” Guideline 5.1.1(ix) adds that apps in highly regulated fields such as banking and financial services, healthcare and gambling should be submitted “by a legal entity that provides the services, and not by an individual developer”.

Read that carefully, because it has a practical consequence that surprises people every month: your development agency cannot publish your fintech app from its own developer account. Nor can a founder publish it personally. The licensed entity submits it, which means the UAE licence and the Apple Developer account have to belong to the same organisation before review, not after.

For a fintech product that means the Central Bank authorisation — or your licensed partner institution — sits upstream of the App Store submission. If you are partnering with a licensed institution, decide early whose developer account ships the app, because it affects branding, analytics and who controls updates.

Crypto has its own rule

Guideline 3.1.5(iii) permits apps to facilitate cryptocurrency transactions on an approved exchange “provided they are offered only in countries or regions where the app has appropriate licensing and permissions to provide a cryptocurrency exchange”. In the UAE that means a virtual asset licence from the relevant authority for your jurisdiction. Wallet apps have their own requirement to be published by an organisation rather than an individual.

If you are building blockchain products, settle the licence question before the submission question. Apple will ask.

Health apps face extra scrutiny

Guideline 1.4.1 warns that medical apps “that could provide inaccurate data or information, or that could be used for diagnosing or treating patients may be reviewed with greater scrutiny”, and expects apps to disclose methodology and remind users to consult a doctor. Guideline 5.1.3 restricts what you may do with health data, including a prohibition on using it for advertising or data mining.

Layer UAE healthcare licensing on top — a telehealth service needs its authority’s approval, and patient data has residency expectations — and a health app becomes a compliance project with a UI attached. The same pattern we describe for pharmacy software applies here.

Lending and gambling

Guideline 3.2.2(ix) sets hard limits on personal loan apps: terms must be disclosed, the maximum APR may not exceed 36%, and you may not require full repayment in 60 days or less. That rules out several short-term lending models outright. Gambling sits under the regulated-entity rule and under local law, and the regulatory position in the UAE has been changing — treat it as a legal question first and a product question second.

Features that behave differently here

Voice and video calling over the internet has long been restricted in the UAE, with licensed alternatives offered instead. An app whose core loop depends on in-app calling may pass Apple review and still fail its users here. Design the escalation path to a normal phone call, and verify the current position before promising calling in your App Store description — a feature that does not work in your main market is a 2.3 metadata problem as well as a product one.

The developer account trap

This is not a guideline, but it delays more UAE launches than most guidelines do.

  • Organisation enrolment takes time. Publishing as a company rather than an individual requires a verifiable legal entity, which in practice means your trade licence details matching the business records Apple checks, whether you are set up in Dubai or Abu Dhabi, and a D-U-N-S number for the entity. For a newly formed UAE company this can take longer than the build sprint it is blocking.
  • The account must belong to the client, not the agency. Whoever owns the developer account controls the app, its updates and its reviews. We publish from the client’s account as standard, and you should expect that from any agency.
  • Regulated apps need the licensed entity’s account, as above — so a partner-led fintech launch may need the partner’s account, which is a commercial conversation, not a technical one.
  • Agreements and tax forms block releases silently. An unsigned paid-apps agreement or missing banking details will hold a release with no rejection email to explain it.

Start enrolment on day one of the project. It costs nothing to do early and it is the most common reason a finished app sits unreleased.

What differs on Google Play

Play tends to be faster but less forgiving after the fact: policy enforcement often arrives as a removal rather than a pre-launch rejection. The categories that bite are similar — financial services, health, gambling — and Play additionally requires declarations for sensitive permissions and a data safety form that must match actual behaviour. Budget for both stores having an opinion, and keep your privacy disclosures identical across them, because inconsistency is itself a flag.

A pre-submission checklist

  • Demo account that works, with the backend running, plus one account per role and notes explaining them.
  • OTP and Emirates ID gates bypassed for the review account, or an explanation of how to get past them.
  • Account deletion reachable inside the app, not only on the website.
  • Privacy policy linked in App Store Connect and in the app, with privacy labels matching what the code actually collects.
  • Screenshots from the submitted build, in every localisation you list, including Arabic.
  • Payments in the right lane: in-app purchase for digital unlocks, your own gateway for physical goods and services.
  • Licences to hand if you are in a regulated category, submitted from the licensed entity’s account.
  • Tested on the oldest OS version you claim, on a real device via an automated build pipeline, on a normal connection — and on a VPN-free UAE network if any content is geo-dependent.

When you do get rejected

Read the exact guideline cited, because the reviewer’s message is usually terse and the guideline is specific. Reply in Resolution Center with a direct answer — a build fix, a clarification, or evidence such as a licence — rather than an argument. If you believe the reviewer is wrong, there is an appeal process separate from resubmission, and for genuine emergencies an expedited review request exists and should be used sparingly.

Most importantly, do not resubmit the same binary with a longer note. If the cited guideline is 2.1 or 4.2, something has to change in the app. Teams that treat a rejection as a conversation to win rather than a defect to fix are the ones that lose weeks.

Frequently asked questions

Why do apps get rejected from the App Store?

Most rejections come from a handful of causes: the reviewer cannot get past a login because no demo account was provided (2.1(a)), crashes and broken links (2.1), metadata that does not match the app (2.3), apps that are repackaged websites (4.2), digital content sold outside in-app purchase (3.1.1), and missing privacy policies or in-app account deletion (5.1.1). Nearly all are avoidable before submitting.

Can my development agency publish my fintech app?

No. Apple requires apps used for financial trading, investing or money management to be submitted by the financial institution providing the service, with the necessary licensing in each region where the app is available, and apps in banking, healthcare and gambling to come from the legal entity providing the service rather than an individual developer. The licensed entity’s developer account must publish it.

Do UAE apps need in-app purchase, or can we use a local payment gateway?

It depends on what you sell. Anything unlocked inside the app — subscriptions, premium content, virtual currency — must use in-app purchase. Physical goods and real-world services, such as a delivery, a booking or an appointment, can use your own gateway, which is why most UAE commerce apps keep their existing payment stack.

How long does App Store review take?

Usually a day or two for a straightforward app, though regulated categories take longer because a human may need to check licensing evidence. The bigger risk to your timeline is not review itself but developer account enrolment, which for a newly formed UAE company can take weeks.

Does an app need a UAE licence to be on the App Store?

Not in general, but it does if the app performs a regulated activity. Financial services, virtual assets, healthcare and gambling all require the appropriate UAE authorisation, and Apple expects the submitting entity to hold it. For everything else, the usual requirement is simply that the app complies with local law wherever it is available.

What should I do when my app is rejected?

Read the cited guideline carefully, fix the actual cause, and reply in Resolution Center with what changed or with the evidence requested. Resubmitting the same build with a longer explanation rarely works, and appealing is a separate process from resubmission.

The bottom line

Rejections are a process problem, not bad luck. The ordinary causes are all preventable with a checklist, and the UAE-specific ones come down to a single principle: if your app performs a regulated activity, the entity holding the licence has to be the entity submitting the app.

Do two things at the start of any project here. Begin developer account enrolment on day one, and settle whose account ships the app if a licence is involved. Those two decisions prevent more delay than any amount of careful coding.

We ship iOS and Android apps for UAE businesses — usually Flutter or React Native, always from the client’s own store accounts, and with submission handled as part of the build rather than a surprise at the end. See what that costs in our Dubai app development cost guide, or tell us what you are building and we will flag the review risks before you write the first line of code.

KB

Author

Karim Ben Salah

Tech Analyst & Researcher

Senior leader at Burj Code, Dubai’s premier digital agency. 12+ years building apps, websites, and marketing strategies for UAE brands.

Found this useful?

Work With Burj Code

Ready to grow your business?

We build apps, websites, and marketing strategies for UAE brands. Free 30-minute consultation with a senior team member — no SDR, no sales script.