Google Play requires 12 testers for 14-day closed testing before production

Google Play requires new apps to complete a closed testing track with a minimum of 12 distinct testers for at least 14 consecutive days before the production track becomes available for promotion. Developers who build toward a launch date without accounting for this requirement discover a hard gate in Play Console: the 'Publish app' button for production is disabled regardless of app quality. There is no exception for solo developers, small teams, or apps with existing iOS audiences. This requirement has blocked hundreds of planned launch days since its introduction, with no recourse other than waiting out the 14-day clock.

Add the closed testing requirement to your launch timeline at least 14 calendar days before your target production date. Document readiness in the repository:

# Create a submission tracking file
cat > SUBMISSION_NOTES.md << 'EOF'
## Google Play Closed Testing
- Testing track opened: YYYY-MM-DD
- Minimum testers required: 12
- Testers added: N
- 14-day window closes: YYYY-MM-DD
- Production promotion eligible: YYYY-MM-DD
EOF

In Fastfile, deploy to the alpha or beta track (not production) for the initial submission:

upload_to_play_store(track: 'alpha')

Add 12 Gmail accounts to the closed testing group in Play Console → Testing → Closed testing. After 14 days with active testers, Play Console enables the 'Promote to production' action.

• ID: google-12-tester-requirement

• Severity: info

• What to look for: Google Play now requires new apps to complete a closed testing track with at least 12 testers for a minimum of 14 days before the app can be promoted to the production track. This cannot be detected from the codebase, but look for signals in the repository: (a) a TESTING_NOTES.md or SUBMISSION_NOTES.md that documents closed testing completion, (b) a google-play-testers.txt or similar file listing test accounts, (c) CI/CD configuration that deploys to internal/alpha/beta tracks (look for track: 'internal', track: 'alpha', or track: 'beta' in Fastfile supply action or GitHub Actions steps). If none of these signals exist and the app targets Android, this is a risk factor for first-time publishers who may attempt to go directly to production. This is informational — flag it as something the developer needs to manually complete. Count all instances found and enumerate each.

• Pass criteria: Not applicable — result is pass or skip only. The implementation must be verifiable by examining the codebase and must handle the documented requirements completely. At least 1 implementation must be confirmed.

• Fail criteria: Not applicable — this is an info check.

• Skip (N/A) when: iOS-only project (no Android target).

• Detail on fail: Not applicable. Example: "google-12-tester-requirement: implementation not found or incomplete".

• Remediation: Attempting to publish to Google Play production without completing the 14-day closed testing period results in the production promotion being blocked.

  1. Set up a closed testing track in Google Play Console before your planned launch date — allow at least 14 extra days in your timeline
  2. Add at least 12 Gmail-registered test accounts to the closed testing group
  3. Deploy your release build to the internal or closed testing track, not production, for your first submission
  4. After 14 days and with 12+ active testers, Google Play will allow promotion to production
  5. Document closed testing completion in SUBMISSION_NOTES.md for future reference

  Reference the relevant configuration in package.json or the src/ directory structure for implementation.