Skip to content
AppDues
Log in
Contact salesSign up

App Review Submission Checklist for Late-Stage Releases

When a launch date is close, review becomes the critical path. The work that matters is not adding features but reducing the app to a reviewable release, giving reviewers everything they need, and avoiding changes that push a submission back in the queue. This guide covers both stores, with special attention to Google Play's closed-testing gate and Apple's reviewer-access expectations.

Start with the real deadline

Work backward from the moment your app must be publicly downloadable, not from the moment you press submit. A build that is only in TestFlight or a Google Play testing track does not count as publicly available. Apple also notes that an approved app can take up to 24 hours to appear in the App Store, so plan for a buffer of at least a day or two before any submission window closes. If a competition or launch event has its own rules, read them separately. Treat any dated event rule as specific to that event, not as a general store requirement.

How the two review pipelines differ

Both stores require a developer account before you can publish. Apple charges $99 per year; Google Play charges a one-time $25 registration fee. Organization accounts need extra verification, which can include a D-U-N-S number. New personal Google Play accounts may also need to complete a closed test before production access.

Apple's release tracks are TestFlight for beta testing and the App Store for public release. Google Play offers internal, closed, open, and production tracks. You do not have to use every testing track, but the production track is the one that makes the app publicly available. Neither store admits an app until a reviewer has checked that it is not misleading, broken, or unsafe.

If you have not submitted yet: cut to the core

The first priority is to get a build into the review pipeline. That means stripping the app to the features your core users would value most and postponing everything else. Comment out draft features, remove unfinished authentication if the main experience does not depend on it, and hold back subscriber-only extras.

A useful decision rule is to sort every unfinished item into one of three buckets:

  • Cut: features that are not needed for the core experience.
  • Fix: bugs or missing assets that would block a reviewer.
  • Document: anything a reviewer cannot infer, such as a test account, a third-party login requirement, or a demo mode.

Do not spend the final days polishing features that reviewers will never see. Spend them removing reasons for rejection.

Should the first submission include in-app purchases?

Purchases and subscriptions give reviewers more to check. Missing metadata, unclear instructions, or misconfigured products can cause a rejection. One option is to submit a complete free version first and add monetization in a second submission after the first is approved. That only makes sense if there is enough time for two reviews. If the deadline is close, including monetization in the first submission may be safer than betting on a second review. Whichever route you choose, test purchases in the platform sandboxes before submitting the monetized version.

Google Play's 14-day closed-testing gate

For personal Play Console accounts created after November 13, 2023, production access requires a closed test with at least 12 testers opted in continuously for 14 days. Start with the earliest functional version of the app and keep building while the test runs. After the full 14 days have elapsed, you can apply for production access.

Google can ask for another round of testing when it judges that tester participation or engagement is too low. Lower that risk by having testers open the app regularly and send you their feedback. Recruiting testers can start with friends and family; community channels can help if that pool is too small. The clock is the constraint here, so a closed test that starts late cannot be compressed by submitting a polished build later.

Use TestFlight and testing tracks before review

A closed or open test group is useful beyond gathering product feedback. It can surface the same problems a reviewer would flag: crashes, performance problems, confusing copy, and incomplete features. Fixing those before submission saves reviewer time and gives you a tighter feedback loop.

Prepare store assets and legal links

Apple and Google publish detailed rules for screenshots, descriptions, privacy policies, and terms of service. Read the current guidance before editing store copy. Avoid claiming beta status in a production listing or calling an unreleased app the number one app for anything.

For apps with subscriptions, both stores expect appropriate Terms of Use links. Apple provides a standard EULA that can be linked from the App Store description. A privacy policy must exist at a real URL and must match the privacy declaration you submitted. Placeholder links or empty pages are a common avoidable problem.

If the app is already in review

Before withdrawing a submission, understand the cost. Apple removes the build from the review queue, and resubmitting starts the process over; Apple does not promise to review in the order received. Google counts review time from the latest submitted change, and sending more changes while an app is under review may push it to the back of the queue.

Do not restart review for a minor improvement. First check whether the change can be made without withdrawing the build, or whether the missing information can be supplied through the store's review communication tools. If you find something likely to block access or cause a rejection, restarting may still be the faster choice.

Give reviewers a working account

If the app has authentication, create a test account and put the username and password in the fields prepared for reviewer credentials. Reviewers will not create accounts themselves. Disable two-factor authentication on that account, because it will block the reviewer. If the account cannot work without 2FA, build a demo mode that shows every part of the app and explain it in the review notes.

If the app uses Google or another third-party login, include Sign in with Apple as well, since Apple requires it. If third-party authentication is essential to the app's function, such as a Gmail client, document that in the review notes.

For subscription apps, make sure the test account does not have an active entitlement. Otherwise the reviewer may not see the paywall and cannot review the purchase flow.

A worked example: a subscription app with email login and a monthly plan. The reviewer account is created with a fresh email and password, 2FA is switched off, and no purchase has ever been made on it. The review notes state that the paywall appears after onboarding, that the monthly plan is the only product, and that the account has no active entitlement so the paywall is visible. If the team later needs 2FA for security, they add a demo mode that walks through onboarding, the paywall, and a sandbox purchase instead of handing over a live account.

Record a short demo video

Apple has increasingly asked developers to provide a screen recording of the app in use, especially for in-app purchases and authentication. A simple recording under a minute is enough: show how the app works and what happens after a subscription purchase. Consider attaching it before a reviewer asks.

Do not rely on expedited review

Apple allows an expedited review request for extenuating circumstances, such as a critical bug fix or a release tied to an event the developer is directly associated with. Apple does not explicitly say that hackathon or competition timelines qualify, and each request is decided individually. The original guidance was not to use expedited review for a competition deadline. Submit early and follow the checklist instead.

A practical sequence for the final weeks

Aim to have the app in review within two weeks, and preferably within one. Stop adding features. Fix launch-blocking bugs and get to a minimum viable release that can be submitted. Once a version is approved, later reviews tend to move faster, so a monetized update has a better chance after the first approval.

A simple order of operations:

  1. Confirm the public-availability deadline and add a buffer for store propagation.
  2. Start or verify any required Google closed test immediately.
  3. Cut non-core features and fix reviewer-blocking issues.
  4. Prepare the privacy policy, terms links, screenshots, and description.
  5. Create a reviewer test account with no 2FA and no active entitlement.
  6. Record a short demo video if purchases or authentication are involved.
  7. Submit, then avoid unnecessary changes while the build is in review.

Frequently asked questions

How much buffer should I leave before a submission deadline?

Plan for the app to be publicly available at least a day or two before the deadline. Apple notes that an approved app can take up to 24 hours to appear in the App Store, and a build that is only in TestFlight or a Google Play testing track is not public.

Who needs Google Play's 14-day closed test?

Personal Play Console accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in continuously for 14 days before applying for production access. Google may require more testing if participation or engagement is insufficient.

Should I withdraw a build to make a small change?

Usually not. Withdrawing removes the build from Apple's review queue and resubmitting starts the process over. Google counts review time from the latest submitted change, and additional changes may push the app back in the queue. Check whether the change can be made without withdrawing first.

What should a reviewer test account include?

Provide a working username and password in the reviewer credential fields, disable two-factor authentication, and make sure the account does not have an active subscription entitlement so the paywall is visible. If 2FA is unavoidable, build a demo mode and document it in the review notes.