Build log/Engineering

How to pass Apple App Store and Google Play review first time

Apps are rejected for a familiar set of reasons, including crashes, missing information, no demo login, payment rules and privacy forms. Here is a checklist to work through before you submit.

The short answer

  • Common reasons for rejection include crashes, placeholder content, incomplete store information, a login without a demo account, and breaches of payment or privacy rules.
  • Apps that sell digital content or features inside the app generally have to use Apple’s and Google’s in-app purchase systems, while physical goods and real-world services do not.
  • Both stores require apps that let people create an account to let them delete it, and both require accurate privacy disclosures before an app is published.

To pass Apple App Store and Google Play review first time, submit a finished app that does not crash, give reviewers a working demo login, fill in every privacy and store form accurately, follow each store’s payment rules and let people delete their accounts. App review is the check each store makes against its published rules before an app or update is made available to the public. The common reasons for rejection are predictable, and this article goes through each of them.

How the two review processes work

Apple reviews every app and every update against its App Review Guidelines before release, and its reviewers try the app as a customer would. If something is wrong, Apple names the guideline the app breaks in App Store Connect. You can reply, fix and resubmit, or appeal to the App Review Board if you think the decision is wrong.

Google Play checks apps against its Developer Program Policies, using a mix of automated and human review. First submissions from new developer accounts can take longer than later updates. Google also currently requires new personal developer accounts to run a closed test with real testers for a set period before they can publish to production, which is one more reason to register the Play Console account as your organisation.

For both stores, allow time. Plan a launch around a review that may need a second attempt, and never announce a date that depends on the first submission being approved.

Common reasons apps are rejected

Apple publishes guidance on the issues it sees most, and Google’s policies cover similar ground. These are the ones that catch first-time submissions.

ReasonStoreHow to avoid it
Crashes, broken links or placeholder contentBothTest the exact build you submit on real devices, and remove unfinished screens and sample text
A login with no way for the reviewer to get inBothProvide a working demo account or a full demo mode, with any instructions needed
Screenshots or descriptions that do not match the appBothShow the real app in use, and leave other platforms out of Apple listings
Digital goods sold without in-app purchaseBothUse the store’s billing for digital content and features used in the app
Missing or inaccurate privacy informationBothDeclare what the app and every SDK in it actually collects
No way to delete an accountBothAdd account deletion in the app, plus a web link for Google Play
Sensitive permissions without justificationBothExplain clearly why the app needs the camera, location or contacts, and complete Google’s declaration for restricted permissions
Social login without a private equivalentAppleOffer a login that meets guideline 4.8, such as Sign in with Apple
A thin wrapper around a websiteAppleGive the app features that make sense as an app, under guideline 4.2

Demo accounts and access for reviewers

If your app needs a login, the reviewer needs one too. Apple asks for an active demo account or a fully featured demo mode in the App Review Information section, and Google Play asks for access instructions in the App access section of Play Console. Create an account that stays active, holds realistic sample data and is not protected by a two-factor code sent to someone’s personal phone. If a feature needs a particular location, device or piece of hardware, explain how the reviewer can see it, or attach a video.

Business software catches people out here. An app for a firm’s own staff, or one that only works after a sales call, still has to be reviewable. Apple also has routes for apps that are not meant for the general public, such as unlisted distribution and custom apps for businesses, so check those before you submit a private app to the public store.

In-app purchase rules for digital goods

Both stores generally require digital content and features that are bought and used inside the app, such as subscriptions, premium features or in-game currency, to be sold through their own in-app purchase systems. Physical goods, and services delivered in the real world, such as a delivery, an event ticket or a booked tradesperson, are paid for with ordinary methods such as card or Apple Pay.

Live lessons need a careful read. Apple’s guidelines allow ordinary payment for real-time person-to-person services between two individuals, such as one-to-one tutoring, while one-to-few and one-to-many live services must use in-app purchase. If your app teaches, coaches or consults, read the current wording closely before you design the checkout.

The rules on telling users about prices elsewhere, or linking to a website to pay, differ between countries and have changed several times recently, including in the United States and the European Union. Check the current rules for every storefront you sell in.

Privacy forms and account deletion

Both stores ask you to declare what data your app collects and why. On the App Store these are the privacy details shown on the product page, and on Google Play this is the Data safety form. The declarations must cover data collected by third-party code in your app as well as your own, including analytics, crash reporting and advertising SDKs. Apple also requires a privacy manifest that explains why the app uses certain system APIs, and an app that tracks people across other companies’ apps and websites must ask permission through App Tracking Transparency. Both stores require a link to a privacy policy.

Any app that lets people create an account must also let them start deleting it from inside the app. Google Play additionally requires a web link where people can ask for their account and data to be deleted without reinstalling the app. Deleting an account should remove the personal data that goes with it, apart from records you are legally required to keep. UK GDPR gives people a right to erasure in many circumstances in any case, with one month to respond to a request.

Apps for children face further rules, through Apple’s Kids Category and Google Play’s Families policy. In the UK, the ICO’s Children’s code applies to online services likely to be accessed by children, as covered in our guide to the Children’s code for edtech.

A checklist before you submit

  1. Test the exact release build on several real devices, including an older one, and on a poor connection.
  2. Remove test screens, placeholder text and links that go nowhere.
  3. Create a demo account with realistic data and put the details in the review notes.
  4. Check that every permission prompt has a clear, specific explanation.
  5. Confirm how each purchase is paid for and whether store billing applies.
  6. Complete the privacy details, the Data safety form, the age rating questionnaires and any content declarations.
  7. Add the privacy policy and support URLs, and check that they load.
  8. Make sure account deletion works in the app, and from the web link for Google Play.
  9. Prepare screenshots from the real app at the sizes each store asks for.
  10. Send the build to TestFlight external testers and a Google Play closed test first. Apple reviews the first build sent to external testers, and Google’s pre-launch report runs the app on real devices and flags crashes.
Launching an app? Plan the store accounts, demo login and privacy declarations alongside the build, well before the launch date. See how we approach mobile apps.

Questions people ask

How long does App Store review take?

It varies, and Apple does not promise a fixed time. Many submissions are reviewed within a day or two, but first submissions, complex apps and busy periods can take longer, and a rejection adds another round. Build a buffer of at least a week into any launch plan.

Can I appeal an App Store rejection?

Yes. You can reply to the reviewer in App Store Connect to explain or ask for clarification, and if you believe the decision is wrong you can appeal to the App Review Board. Google Play also has an appeals process for policy decisions. Fixing the issue and resubmitting is usually quicker than an appeal.

Do I need Sign in with Apple?

Only in some cases. If your app uses a third-party or social login such as Google to set up or sign in to the main account, Apple’s guideline 4.8 generally requires an equivalent option that limits data collection to name and email and lets people keep their email address private. Sign in with Apple meets that requirement. Apps that use only their own accounts do not need it.

Why was my app rejected for being a website in an app?

Apple’s minimum functionality guideline, 4.2, expects an app to offer more than a repackaged website. An app that only shows a website in a web view is often rejected. Add features that justify an app, or consider whether a progressive web app fits better.

Written by Flavoureak

We build and run Estimark, CurioKids and CalcStack, and we build web and mobile software for other businesses. Start a project.