Step 6: publish the closed testing track

The opt-in link only exists once the track is published. Upload your AAB, roll the release out to the track, send it for review and wait for “Published”.

J
Written By JordanLast updated 1 hour ago

What this step is for

Testers can only join once a release is live on the track, and Google shows the opt-in link only when the app is “Published”.

How to do it

  1. Create a release on the closed testing track and upload your AAB file.
  2. Roll it out to the track and send it for review.
  3. Open “Publishing overview” and check that nothing waits under “Changes not yet sent for review”.
  4. Wait for the track's “Published” status. Google's review can take from a few hours to seven days, and longer for some new accounts.
  5. Click “Done” on this step in Peerbeta.

Common mistakes

  • Thinking the release is in review when it was never sent: changes wait until you click “Send for review”.
  • Leaving managed publishing on and forgetting it: approved changes wait under “Changes ready to publish” until you click “Publish changes”.
  • Uploading new builds during the review to speed it up. Google counts the review time from the last change, so it can push you back in the queue.
  • Sharing the link the minute it shows up. After the first publish, Google says the test can take several hours to become available.

Was this helpful?

Your feedback shapes what we write next.