⚡️Cyber Monday Flash Sale 70% Off:
H :
M :
S
⚡️
  1. Home
  2. Knowledge Base
  3. BuddyBoss App Docs
  4. App Publishing
  5. How to Configure Google Play Store Closed Testing

How to Configure Google Play Store Closed Testing

Introduction

Google has introduced a new app publishing policy for Individual Developer Accounts effective November 13, 2023. Any new Google Developer Accounts registered as individuals must now complete a closed testing phase with at least 12 internal testers for a minimum of 14 days before unlocking the Production Tab, which is required to publish apps to the Play Store.

If you registered before November 13, 2023, or are using an Organization Account, this requirement does not apply. For those affected, this policy ensures developers receive early user feedback to improve app quality before a public release.

This article explains how to set up closed testing, invite testers, and meet the requirements to unlock production access.

Explore BuddyBoss Platform | BuddyBoss App | BuddyBoss Pricing | Try BuddyBoss Demo

Create a Closed Testing Track

  1. Log into Google Play Console and select your app.
  2. From the Release section in the left sidebar, go to Testing > Closed Testing.
  3. Choose from your active tracks:
    • If an existing track is available, click Manage Track.
    • To create a new one, click Create Track.
  4. Enter a Track Name and click Create Track.

Note: If this is your first time uploading a build to a test track, you may need to accept Google’s terms and conditions.

  1. Click the Countries/Regions tab and select the regions where you want your app available for testing.
    • To make it available everywhere, select the first checkbox to add all countries.

Add Testers to Your Closed Test

Closed testing allows you to invite specific users for pre-release testing. These testers provide feedback, helping you identify bugs, improve UI, and enhance the overall user experience.

  1. Go to the Testers tab.
  2. Select an existing email list or click Create Email List to add testers.
  3. Enter a List Name and add at least 12 email addresses.
  4. Click Save Changes and then Create.
  5. Add a Feedback URL or email address so testers can send feedback. Click Save.
  6. Click Go to Overview when prompted.

Once approved, you’ll receive a Test Link that can be shared with your testers.

Note:
– Google requires at least 12 testers to opt-in to your closed test.
– The Copy Link option for the test will only become available after Google approves the release.

Create a New Release for Closed Testing

  1. Click Create New Release in the closed testing track.
  2. Under App Bundles, upload the .aab file you downloaded from BuddyBoss (or select from your library).
  3. Click Add to Release.
  4. In Release Details, the version number will be auto-filled.
  5. Add Release Notes—you can include the official BuddyBoss release notes or any custom message for testers.
  6. Click Next, then Save.
  7. In the popup, click Go to Overview.
  8. Click Send Changes for Review.
  9. Confirm by clicking Send Changes for Review again.

Google will review your release in 3-5 days. Once approved, you can share the Test Link with your testers.

Explore BuddyBoss Platform | BuddyBoss App | BuddyBoss Pricing | Try BuddyBoss Demo

Configure License Testing

While waiting for approval:

  1. From the left sidebar, navigate back to All Apps.
  2. Under Setup, click License Testing.
  3. Add license testers from your email lists and click Save Changes.

License Testing helps verify app licensing, ensuring only authorized testers can access the app.

Run the 14-Day Closed Testing Period

After Google approves your closed test release:

  • Share the Test Link with your 12+ testers.
  • Testers must opt-in and use the app for at least 14 days.
  • Collect feedback for improvements.

Once the 14-day testing period is complete, you can apply for production access.

What’s Next After Closed Testing?

Once the closed testing requirements are met:

  1. Go to your app’s Dashboard and click Apply for Production.
  2. Answer questions about:
    • Your closed test
    • Your app/game
    • Production readiness
  3. Submit your request. Google will review it and email the account owner with the result.

Timeline:

  • Review usually takes 7 days or less but may occasionally take longer.

If approved, you’ll unlock the Production Tab, allowing you to upload a build for final Google review and live publishing.

After Gaining Production Access

Once you have access to production:

  1. Create a release in the Production track and upload your app build.
  2. Submit a publishing request via BuddyBoss App > Publishing Service > Google Play Store in your WordPress dashboard.
  3. The BuddyBoss Publishing Team will manage your app submission and keep you updated via email.

Explore BuddyBoss Platform | BuddyBoss App | BuddyBoss Pricing | Try BuddyBoss Demo

Troubleshooting & FAQs

Q: Do I need closed testing if I have an Organization Developer Account?
A: No, this requirement applies only to new Individual Developer Accounts.

Q: Can I skip the 14-day testing period?
A: No. Google enforces this mandatory period for individual accounts.

Q: What happens if I add fewer than 12 testers?
A: You won’t meet Google’s requirement, and production access will remain locked.

Q: When can I share the test link?
A: Only after Google approves your closed test release.

Q: How long does Google take to review a closed test release?
A: Typically 3-5 days, but it may take longer in some cases.

Q: How long does production access review take?
A: Usually 7 days or less after applying for production.

Was this article helpful?

Related Articles

Subscribe to Our Newsletter

Stay In Touch

Subscribe to our Newsletter, and we’ll send you the latest news from BuddyBoss

  • This field is hidden when viewing the form
  • This field is for validation purposes and should be left unchanged.

To speak to our Agency consultant, fill in the form found at our Contact Page.

  • Get Started

    Enter your name and email address to get started with your project...

  • This field is for validation purposes and should be left unchanged.