What Is the Closed Testing Requirement?
Since November 2023, Google requires all new personal developer accounts to run a closed test with at least 12 testers for a minimum of 14 consecutive days before they can publish an app to the production track. This policy was introduced to reduce spam, low-quality apps, and policy-violating submissions on the Play Store.
Organization developer accounts may have different requirements, but most new accounts face this rule.
Why Google Added This Requirement
Before this policy, the Play Store received millions of spam and scam app submissions. By requiring a real testing period with real users, Google ensures that:
- Developers are serious about their apps
- Apps have been tested by actual users before reaching the public
- Low-effort spam apps are filtered out before publication
- Policy violations are caught earlier in the development cycle
Step-by-Step Guide
Step 1: Create a Closed Testing Track
- Open Google Play Console
- Select your app
- Go to "Testing" in the left sidebar and select "Closed testing"
- Click "Create track" (or use the default closed testing track)
- Choose your testers: email list or Google Group
Step 2: Recruit 12 Testers
You need at least 12 unique testers who:
- Have Google accounts (Gmail or Google Workspace)
- Opt in to the test through the provided link
- Actually install and open the app on their Android devices
Where to find testers:
- Friends and family
- Online communities related to your app's niche
- Beta testing platforms (BetaFamily, TestingCatalog)
- Developer forums and social media groups
- Colleagues and professional contacts
Step 3: Upload Your APK or AAB
Upload a signed app bundle to the closed testing track. This should be a production-quality build, not a debug build. Google will run pre-launch tests on it.
Step 4: Wait 14 Days
The 14-day clock starts when your first tester opts in and installs the app. Key points:
- All 12 testers must opt in and remain active during this period
- The 14 days must be consecutive (no pauses)
- If testers drop below 12, the counter may reset
- Google tracks actual device installs, not just email opt-ins
Step 5: Apply for Production Access
After the 14-day period completes successfully:
- Go to "Production" in Play Console
- You should see the option to "Request production access"
- Google reviews your request (typically 1-3 business days)
- Once approved, you can publish to production
Common Problems and Solutions
Testers Not Showing Up
- Send the opt-in link directly (not just the Play Store link)
- Make sure testers are using the correct Google account
- Remind testers to actually open the app after installing
Counter Not Starting
- Verify that testers have both opted in AND installed the app
- Check the Play Console dashboard for the current tester count
- Ensure the app bundle is properly uploaded and available
Testers Dropping Out
- Recruit 25-30 testers to have a buffer
- Keep testers engaged with updates and communication
- Use a simple app version that works reliably (avoid crashy builds)
App Rejected During Closed Testing
- Google still reviews closed test apps for policy compliance
- Fix any violations before the 14-day period starts
- A rejected closed test does not reset the timer if testers remain active
Tips for Success
- Start recruiting testers before your app is ready - Gathering 12 reliable testers takes time
- Use a Google Group - Easier to manage than individual email lists
- Communicate with testers - Let them know what the app does and ask for feedback
- Monitor the dashboard daily - Catch tester dropoff early
- Have a fallback plan - If you lose testers at day 10, you need replacements fast
- Use this time productively - Gather real feedback and fix bugs during the 14 days
Exceptions and Edge Cases
- Organization accounts created with a DUNS number may be exempt from the 12-tester requirement (they may only need a shorter testing period)
- Existing accounts that already have published apps are not affected
- Transfer of apps between accounts may have different rules
- Reinstating removed apps may require completing the closed testing again