Google Play Console 14-Day Closed Testing Checklist (2026 Edition)

Step-by-step checklist to guarantee Google Play Production Access approval

Successfully publishing an Android app on Google Play requires completing 14 continuous days of Closed Testing with at least 12 opted-in testers. To help developers navigate this requirement without errors, we compiled the ultimate 5-phase checklist.

Phase 1: Pre-Testing & Track Setup

• Create a Closed Testing Track in Google Play Console (do not use Internal Testing).
• Ensure your AAB/APK artifact is uploaded and in 'Active' status on the Closed Testing track.
• Set Country & Region availability to include all 176+ target regions.
• Copy your Web Opt-in URL (https://play.google.com/apps/testing/your.package.id).

Phase 2: Tester Recruitment & Opt-in

• Recruit at least 12 (preferably 14-15 for buffer) verified manual testers via CloseTesting.
• Add all tester Google account emails to your Play Console email list.
• Confirm all 12+ testers click 'Accept Invitation' on the Web Opt-in page.

Phase 3: 14-Day Active Monitoring

• Ensure testers maintain a daily app opening streak for 14 continuous days (336 hours).
• Monitor Android Vitals in Play Console for ANRs (Application Not Responding) and crash spikes.
• Collect user feedback and bug reports from testers via campaign chat or email.

Phase 4: Release Updates & Bug Fixes

• Increment `versionCode` and deploy bug fix updates to the Closed Testing track as needed.
• Document all changelogs and tester feedback responses.

Phase 5: Production Access Application

• Wait until the 14-day counter reaches 100% on the Play Console Dashboard.
• Complete the Production Access Questionnaire with specific details on recruitment and feedback.
• Submit for Google Play manual review.

Following this 5-phase checklist eliminates guesswork and ensures your Production Access request passes Google Play review on the first attempt.