Closed testing stuck "In review": how long it really takes

Updated November 8, 2026

Your closed testing release shows "In review" and nothing moves. Your 14 days can't start until testers can opt in, so every day in review feels lost. Here's what Google actually commits to, what makes a review slower, and the checks that often reveal the release was never waiting on Google at all.

What Google says about timing

Step	What Google says	Source
Review of a change (release, listing, app content)	"a few hours or up to seven days (or longer in exceptional cases)"	Play Console Help
New and certain other accounts	"we'll take more time to thoroughly review your app ... up to seven days or longer in exceptional cases"	Play Console Help
After approval, the opt-in link	"can take several hours to become available to testers" after the first publish of a test	Play Console Help
Production access application (later)	"usually takes seven days or less, but can occasionally take longer"	Play Console Help

When Google announced the testing requirement, it also said it would spend more time on some new apps, "such as apps designed for children or that request certain device permissions" (Android Developers Blog).

So for a new personal account, a week in review is within what Google describes. Past a week, start checking.

One release or all of them?

Pattern	Likely cause	Check first
First release of a new app, a few days in	Normal extended review	Wait, and run checks 1 to 3
"Approved", but testers still can't join	Managed publishing or link delay	Checks 2 and 6
Each new build seems to restart the wait	Resubmitting during review	Check 3

Checks to run, in this order

1. Is it really in review?

Changes aren't sent to Google automatically. They wait in Publishing overview > Changes not yet sent for review until you click Send for review. After a rejection, Google says your new changes "aren't sent for review automatically" either: you must send them yourself (Play Console Help).

Fix: open Publishing overview. If your release sits in "Changes not yet sent for review", send it.

2. Is managed publishing on?

With managed publishing on, approved changes stop in Changes ready to publish and wait for you to click Publish changes. That includes "changes to how testers are configured for a track (for example, setting a new email list or Google group as the list of testers)" (Play Console Help).

So you can be "approved" for days without anything going live. Google even suggests managed publishing for apps subject to extended review times, so some developers turn it on early and forget.

Fix: check the "Managed publishing status" section of Publishing overview. If changes are ready, publish them.

3. Did you submit more changes while in review?

Google is explicit: the review time "is counted from the last submitted change to an app". If you submit a change while others are in review, "your app may be pushed to the back of the app review queue" (Play Console Help).

Fix: stop re-uploading builds to "unstick" the review. Batch your changes. If a build is broken, fix it, but don't resubmit just to nudge the queue.

4. Is something blocking the release?

If your release page shows an Errors summary, Google won't publish until you fix the errors. Warnings don't block (Play Console Help). Google gives unfinished App content items, such as the content rating questionnaire or your target audience details, as examples of errors to fix (Play Console Help).

5. Is your first release on internal testing?

Internal tests are usually fast and not reviewed. Two exceptions, per Google: if your app's first release is on internal testing, it must be reviewed before it's published, and if your previous submission was rejected, the next one must be reviewed even on internal testing (Play Console Help). Expect the same waits as above.

6. Approved, published, and testers still can't join

Then you're past review. Google says the test link can take several hours to become available after the first publish (Play Console Help). If it's still failing after that, the problem is the link or the tester's account: see closed testing link not working.

Use the wait well

A week in review is a week you can use:

Recruit and brief your testers now, with their Google account addresses, so the 14 days can start the hour the link works.
Fill App access if your app has a login: Google's reviewers need working credentials, and so will the production review.
Prepare your production application notes. The form asks about recruitment, tester activity, feedback and what you changed. See how to apply for production access.
Plan your dates. Your 14 days count per tester, from their opt-in. See how the 14 days are counted.

When to contact Google

Contact Google through the Contact us link in Play Console Help when:

your release has shown "In review" for more than seven days,
you haven't submitted any other change in that time,
there's no Errors summary and nothing waiting in "Changes not yet sent for review" or "Changes ready to publish".

Give the package name, the track, and the date you sent the release for review. Before that point, support will usually tell you to wait. For the whole process, see the Google Play closed testing guide.

Frequently asked questions

How long does Google take to review a closed testing release?

Google says processing can take a few hours or up to seven days, or longer in exceptional cases. Some developer accounts, such as new ones, get a longer review.

Does sending another update restart the review?

It can. Google counts the review time from the last submitted change, so submitting changes while you're in review may push your app to the back of the queue.

My release was approved. Why can't testers join yet?

After the first publish of a test, Google says the link can take several hours to become available. If managed publishing is on, approved changes also wait until you publish them.

How long does the production access review take?

That's a separate review. Google says it usually takes seven days or less, but can occasionally take longer.