
App rejected by the App Store: what to do and how to avoid it

Crashes, a missing demo account, privacy: why Apple rejects an app, how to fix it or appeal, and how to protect your company's developer account.
An app is most often rejected by the App Store for a very concrete reason: a crash during testing, a broken link, a missing demo account or an incomplete privacy policy. The rejection is not final. You read the reason in App Store Connect, you fix it and you submit again, and if you believe the review team got it wrong, you can appeal. In 2025, Apple in fact approved 387,087 submissions after an initial rejection.
The subject came up again this week on X, where several independent developers described long waits in "Waiting for Review" and unexpected account closures. Here is what you need to know if your company is preparing an app, or has just received a rejection.
Why is Apple rejecting so many apps at the moment?
The volume has risen sharply. According to its 2025 transparency report, the App Review team examined 9,100,620 submissions over the year and rejected 2,093,244 of them, nearly one in four. A year earlier, Apple reported 7.7 million submissions reviewed.
Apple itself links this increase to AI development tools. Generating an app in a few hours has become possible, and many of these projects reach review without having been tested on a real iPhone. We have detailed the limits of this approach in our article on vibe coding for an SME. For a company with a serious submission, the direct consequence is a busier queue and stricter checks on apps that look like mass-produced content.
What are the most common reasons for rejection?
Apple's report classifies rejections by major section of the review guidelines. The Performance section comes far ahead with 1,354,418 rejections in 2025. It is followed by legal issues, privacy included (495,673), design (415,532), business rules such as payments (283,820) and safety (151,159).
Behind these figures, Apple's App Review page lists very down-to-earth causes. Here are the most common:
- The app crashes or shows a blank screen during testing, often because the staging server was switched off.
- Placeholder text or buttons that lead nowhere were left in the interface.
- No demo account is provided even though the app requires a login.
- The privacy policy is missing, or the prompts asking for access to the camera or location do not say what it is used for.
- The screenshots on the store listing do not match the actual app.
- The app merely displays the company's website, which guideline 4.2 rejects by requiring more than a repackaged website.
- Users can create an account but cannot delete it from within the app, whereas guideline 5.1.1 requires it.

Photo: Lauren Mancke on Unsplash
None of these errors requires a major overhaul. They almost always come from something overlooked when preparing the submission.
What should you do when your app is rejected?
How do you read the rejection reason?
The rejection message appears in App Store Connect, with the guideline concerned and often a screenshot of the screen at fault. You can reply directly in that thread to ask for clarification. Apple also offers 30-minute video appointments with the App Review team, which are useful when the reason remains unclear.
Should you fix it or contest it?
In the vast majority of cases, you fix it. If the criticism is justified, the new version goes back into review after the fix. If, on the other hand, you believe the app complies with the guideline cited, you can refer the matter to the App Review Board. Apple accepts a single appeal per rejected submission, and you must explain precisely why the app complies.
Can a new review be speeded up?
Yes, in two situations provided for by Apple: fixing a critical bug in production, or an app tied to a dated event. The request for an expedited review is made from the developer website. Apple also states that an update fixing a bug can be accepted even if other points remain to be resolved, provided they are dealt with in the next version.
Does an SME risk having its developer account closed?
The risk exists but it mainly targets fraud. In 2025, Apple closed 193,035 developer accounts, 192,702 of them for fraud. Out of 10,127 appeals, only 499 accounts were reinstated. A closure is therefore very rarely reversed, which is why it pays to avoid situations that look like abuse.
For a company, three precautions are enough in most cases. The account must be opened in the company's name, with its D-U-N-S number, by a person authorised to bind it, with an email address on the company's domain and a live website, as Apple's enrolment procedure requires. The membership costs 99 dollars a year. Next, avoid publishing several near-identical copies of the same app, which guideline 4.3 treats as spam. Finally, be wary of off-the-shelf app generators: guideline 4.2.6 rejects apps created from a commercialised template when they are not submitted by the content provider itself.
For the same reason, have your app published on your company's account rather than on that of the agency or freelancer developing it. It stays yours, and a problem with a provider cannot make it disappear from the store.
Are the rules the same on Google Play?
The substance is similar, the procedure differs. For a personal account created after 13 November 2023, Google requires a closed test with at least 12 testers for 14 days before you can apply for production access, then announces a usual review time of around 7 days, according to the Play Console help. An organisation account is not subject to this testing requirement, which is one more reason to open the accounts in the company's name. Apple's timelines and the D-U-N-S verification are detailed in our guide to the mobile app MVP, its timelines and its steps.
How do you prepare a submission that passes first time?
Before sending a version for review, check these points one by one:
- Test the app on several real iPhones, on a mobile network and on Wi-Fi.
- Keep the server and the API online for the whole review period.
- Provide a valid demo account, or a demo mode, in the review notes.
- Publish a privacy policy that can be reached from the app and the store listing.
- Write permission prompts that explain the actual use of the camera, photos or location.
- Offer account deletion in the app if account creation exists.
- Retake the screenshots from the version submitted.
This preparation work is part of our iOS and Android mobile app development offer: our MVP, available from CHF 4,900 or €4,900, includes publication on a store. If you first want to get a sense of your budget, our article on the cost of a mobile app in Switzerland gives orders of magnitude, and the online budget calculator provides a first estimate in a few clicks.
If your app has just been rejected, send us the message you received in App Store Connect. We will quickly tell you whether it is a fix of a few hours or a deeper problem.
Frequently asked questions
Why was my app rejected by the App Store?
The exact reason is shown in App Store Connect, with the number of the guideline concerned. The most common causes are a crash during testing, a missing demo account, a missing privacy policy or an app that does nothing more than display a website.
Can you appeal an App Store rejection?
Yes, to the App Review Board, with a single appeal per rejected submission and specific reasons showing that the app complies with the guideline cited. If the rejection is justified, it is quicker to fix the issue and submit a new version.
Can an App Store rejection lead to the developer account being closed?
No, an ordinary rejection does not close the account. Closures mainly target fraud: in 2025, 192,702 of the 193,035 accounts closed by Apple were closed for that reason.
In whose name should a company open its Apple Developer account?
In the company's name, with its D-U-N-S number, by a person authorised to bind it. That way the app remains the company's property, even if it changes provider.
How much would your project cost?
Project type, features, timeline: a costed estimate in two minutes, with no commitment.
Has your app just been rejected?
Send us the message you received from Apple or Google: from Rumilly, we will tell you frankly what needs fixing and how long it will take. Write to us or book 15 minutes with Jérémy.