Closed Test Release Stuck “In Review”: What to Do

Why the first release takes longest

The first time your app is published to any track that needs review, Google is reviewing the app, the listing and your declarations, not just one build. New developer accounts may also get extra checks. Later updates to the same track are usually faster.

Google’s help also notes that after the first publish, the test link can take several hours to become available to testers.

Things you can check

1. Publishing overview. In Play Console, open Publishing overview to see whether changes are actually sent for review, or still waiting for you to send them.
2. Errors and warnings on the release page. Errors block publishing.
3. App content. Every declaration must be complete: privacy policy, ads, app access, content rating, target audience, data safety. See the app content checklist.
4. Inbox and email. Google may have asked a question or flagged a policy issue.
5. Managed publishing. If it’s turned on, approved changes wait until you publish them manually.

What not to do

• Don’t upload the same build repeatedly. It can reset your place in the queue.
• Don’t create a new app to get around it. You lose your progress and package name.
• Don’t panic about the 14 days. The clock only starts once 12 testers are opted in, which can’t happen until the release is live anyway.

Planning around review

Upload your closed test build a few days before you need testers. Line up testers in the meantime so they can opt in the day it goes live. If it’s rejected rather than slow, see closed test release rejected.

Frequently asked questions