Skip to content

Mobile

App Store and Google Play Submission Checklist: Launch Without Rejections

Many apps are rejected for avoidable reasons. Use this checklist for accounts, policies, privacy details, store listings and testing before you press submit.

By the CodeElectron engineering teamUpdated 6 min read
Illustration of a smartphone showing an app with a verified badge ready for store release

Key takeaways

  • Prepare developer accounts, privacy policy, store listing assets and test accounts well before the release date.
  • Both stores review privacy practices and policy compliance, so declare data collection honestly and consistently.
  • Use test tracks (TestFlight and Google Play testing) to catch problems before public release.
  • Most rejections come from crashes, missing demo access, unclear permissions, misleading metadata or policy gaps.

Start before the app is ready

Store approval has lead time. Developer accounts, business verification, tax and payment details, a privacy policy and listing assets all take time, and the stores’ rules change. Start these in parallel with development so approval never becomes the last-minute blocker. Always check the current requirements in the Apple Developer and Google Play Console documentation, because policies and technical rules are updated regularly.

Accounts and ownership

  • Register the developer accounts under your company name, not a freelancer’s personal account.
  • Complete identity or business verification and payment profiles early.
  • Keep the credentials, signing keys and certificates in your company’s control.
  • Note any extra testing or verification steps the stores currently require for new accounts.

Policies and privacy

Both stores expect a public privacy policy and an accurate description of the data your app collects and how it is used, including data collected by third-party tools such as analytics or crash reporting. The declarations in the store forms must match what the app really does. Request only the permissions you need, and explain them in the app before the system prompt appears.

The store listing

  • A clear name, subtitle and description that match what the app does.
  • Screenshots for the required device sizes, in the languages you support.
  • An icon and, if needed, a short promotional video.
  • Support and privacy URLs that load, plus a contact email that is monitored.
  • Age rating and category answered honestly.

Test before you submit

  1. 1Run the release build, not a debug build, on real devices including a modest phone.
  2. 2Test login, payments, permissions, offline behaviour and account deletion where required.
  3. 3Distribute through TestFlight for iOS and a Google Play testing track for Android.
  4. 4Provide the reviewers with a working demo account and any special steps.
  5. 5Check that every link, privacy and terms page works.

Common reasons for rejection

  • Crashes or broken flows during review.
  • No way for the reviewer to log in or reach paid features.
  • Requesting permissions without a clear reason.
  • Misleading screenshots or descriptions.
  • Missing account deletion or privacy information where required.
  • Content or payments that do not follow platform rules.

A worked example

A team submits a delivery app. The first review fails because the reviewer cannot log in: the app needs a phone number and a code, and no demo account was provided. The fix is a test account with a fixed code and a short note. The second review passes. Adding the demo account to the checklist from the start would have saved several days. This is an illustrative example of a common pattern.

Common reasons for rejection

  • Crashes or broken features found during review.
  • Missing or unclear privacy information, including what data the app collects.
  • Login required without giving reviewers a working test account.
  • Placeholder content, broken links or unfinished features.
  • Permission requests the app does not clearly need.

Next step

Choosing how to build first? Read native or cross-platform apps. To keep the app healthy after launch, see mobile app maintenance cost, or contact our mobile team.

Frequently asked questions

How long does App Store review take?

Review times vary and can range from hours to a few days, longer around busy periods or if there are issues. Plan a buffer and submit early.

Do I need a privacy policy for my app?

Yes, in practice. Both stores expect a privacy policy and accurate data declarations, especially if the app collects personal data or uses third-party SDKs.

What if my app is rejected?

Read the reviewer’s message, fix the issue, and resubmit with an explanation. Many rejections are resolved quickly once the cause is clear.

Have a question we have not covered?

Ask the team directly. We are happy to talk through your situation.