If your closed testing release is still "In review", it's usually just waiting in Google's queue. Google says reviews can take "a few hours or up to seven days (or longer in exceptional cases)", and new developer accounts may see longer reviews. Before you assume it's stuck, check that the changes were actually sent, that nothing is blocking them, and that managed publishing isn't holding back an approved release.
How long a closed testing review can take
Google doesn't promise a fixed time. Its managed publishing help says reviews can take "a few hours or up to seven days (or longer in exceptional cases)" and recommends planning a buffer of at least a week. The publishing help adds that new developer accounts may see reviews of "up to seven days or longer in exceptional cases".
So a review that has run three or four days is within the normal range, especially on a new account. Anyone who tells you the "real" review time is a specific number of hours is guessing.
Check 1: Is it really in review?
The most common "stuck" release was never sent. Saving a release or editing testers doesn't submit anything. The changes sit in Publishing overview under Changes not yet sent for review until you click Send for review.
- Open Publishing overview in Play Console.
- Look for a list of changes not yet sent for review.
- If your release, testers or countries are there, send them.
If this is your first closed release, our article on why a tester invite isn't approved explains this step in detail.
Check 2: Is something blocking the submission?
Closed testing needs app setup to be finished first, and unfinished tasks or release errors can stop your changes from going through. Look for errors or unfinished tasks on the Dashboard and in Publishing overview. The usual suspects:
- App content declarations under Policy and programs > App content (privacy policy, ads, app access, target audience and content, content rating, and others)
- The Data safety form, which is required for closed, open and production tracks
- Release errors, such as a version code that was already used or a bundle that doesn't meet the target API level rule
Our closed testing checklist lists everything that needs to be in place before day 1. If the release itself failed to upload properly, see uploading your first AAB.
Check 3: Did managed publishing hold it back?
With managed publishing turned on, you choose when approved changes go live. That means a release can pass review and still not reach testers because nobody pressed publish. Google describes it as a way to control when changes go live.
If your status suggests the changes were approved but testers still can't see anything, open Publishing overview and check whether approved changes are waiting for you to publish them. Managed publishing is useful later, for timing a launch, but on a first closed test it often causes confusion. If you don't need it, turn it off.
Check 4: Was it approved, and the link is just slow?
There's a second wait after approval. Google notes that "after publishing an open, closed, or internal test for the first time, the test link can take several hours to become available to testers." The opt-in link also only shows once the app status is Published, not Draft or Pending.
If the release says published and testers get an error, give it a few hours before changing anything. If it still fails after that, work through opt-in link not working? 8 fixes.
Check 5: Did Google email you?
Google contacts developers by email, so check the inbox of the account owner, including spam and any filters, and look for notices in Play Console itself. A release that seems stuck is sometimes waiting on you, not on Google. If you find a rejection or a policy notice, fix the specific issue it names before sending again.
What not to do while you wait
- Don't keep changing the release. Every edit you send adds a new change to review. If you must fix something, fix it once and send it.
- Don't create a second app or track to "get around" the queue. It doesn't skip review, and it splits your testers.
- Don't assume resubmitting speeds things up. Google doesn't say that it does.
- Don't let your testers drift. If they're waiting on you, tell them the expected window so they don't lose interest before day 1.
When it's beyond the normal range
If the review has gone well past seven days, everything was sent, nothing is blocked, and there's no email, it's reasonable to contact Google Play developer support through the help options in Play Console. Describe what you submitted, when, and what the status shows. Google doesn't publish an escalation timeline, so keep your expectations open.
Plan the wait into your schedule
The closed test's 14 days can't start until the release is reviewed, published and testers opt in. A realistic plan for a new account:
- Finish app setup and the App content declarations first.
- Upload the bundle, set countries and testers, and send everything for review together.
- Leave about a week of buffer, as Google recommends.
- Tell testers the link will come "within the next few days", not "tomorrow".
If you use GoPlayTester, the setup guide shows the exact send step, and our testers start from 8 PM WIB in queue order once your testing link works. If you haven't arranged testers yet, you can order here while the review runs.
Quick checklist
- Changes appear as sent, not under "Changes not yet sent for review"
- No unfinished App content or Data safety tasks
- No release errors on the closed track
- Managed publishing isn't holding approved changes
- First publish: waited a few hours for the link
- Inbox and email checked for policy messages
