Most closed tests that run late don't fail on day 10. They stall on day 0, because the account isn't verified, a declaration is missing, or the testers can't open the link. Work through these ten items before you invite anyone, and your testers can opt in, which starts their 14 days, as soon as the track is published and the opt-in link works.
This checklist assumes a new personal developer account, where Google requires a closed test with at least 12 testers opted in for 14 continuous days. If you are new to the rule, start with what Google Play closed testing is.
Account
1. Identity verification is complete
Personal accounts without a verified payments profile have to provide an official government ID. Accepted documents vary by country. Accounts that stay unverified can have apps removed, so finish this first (Verify your identity).
2. Device verification is done
New personal accounts must confirm access to a real Android device through the Play Console mobile app. The device must be a non-rooted physical Android phone running Android 10 or later. Look for the task on the Play Console Home page (Device verification).
App
3. App setup and App content declarations are filled in
You can't use closed testing until app setup is complete. Go to Policy and programs > App content and work through every item that applies: privacy policy, ads, sign-in details (app access), target audience and content, the content rating questionnaire, and any permission declarations (App content).
4. Data safety form and privacy policy
The Data safety form is required for apps on closed, open or production tracks, even if your app collects no data. You need a working privacy policy link as well (Data safety). Make sure the URL loads on a phone and isn't a placeholder.
5. A signed app bundle that meets the target API rule
New apps must be published as an Android App Bundle (AAB), and on your first upload you configure Play App Signing. From August 31, 2026, new apps and updates for phones and tablets must target Android 16 (API level 36) or higher (Target API level). Check targetSdkVersion in your build before you upload.
6. A build that is stable enough to test
Testers can't give useful feedback on an app that crashes on launch. When you upload a bundle, Google automatically generates a free pre-launch report that runs your app on test devices and flags stability and compatibility problems. Results usually arrive within an hour. Read it and fix anything serious before testers arrive.
7. Test login details, if your app needs a login
If parts of the app sit behind a sign-in, add working credentials under the app access (sign-in details) declaration so Google's reviewers can reach every feature. Decide how testers will log in too: their own sign-up, or accounts you create for them.
Testers and track
8. At least 12 testers, each with a Google account
You need a minimum of 12 testers opted in on the day you apply, and each one must have stayed opted in for the preceding 14 days. Anyone who opts out early stops counting. Plan for a few more than 12 so one dropout doesn't reset your timeline.
Google suggests asking friends, family, colleagues, classmates and communities where your future users are. Every tester needs a Google account (or a Google Workspace account). Collect the exact address each person uses on their phone.
9. The right countries on the closed track
Closed track availability is synced with production countries by default. If you or your testers are in a country that isn't selected, they likely can't get the app. Check the Countries/regions tab when you manage the closed track and make sure every tester's country is included.
10. A feedback channel and a buffer for review
Testers can send private feedback through Google Play, and you'll find it under Monitor and improve > Ratings and reviews > Testing feedback. You must summarize that feedback when you apply for production, so set up a simple channel as well. Google itself suggests a messaging group for testers.
Then plan time. Closed releases go through review, which can take a few hours or up to seven days, and Google recommends a buffer of at least a week. After the first publish, the opt-in link can take several hours to work.
Common day-0 mistakes
- Not sending the change. Adding testers or countries only saves a draft. The change must be sent for review from Publishing overview. This article covers it.
- Testing on internal instead of closed. Internal testing doesn't count toward the requirement.
- Inviting the wrong email. Testers must use the Google account you added to the list.
- Planning exactly 12 people. One opt-out and you're below the minimum.
Quick checklist
- Identity verified
- Device verified with the Play Console app
- App content declarations complete
- Data safety form and privacy policy done
- Signed AAB targeting API 36 or higher
- Pre-launch report checked
- Login credentials provided, if needed
- 12+ testers with their Google account emails
- Testers' countries selected on the closed track
- Feedback channel ready and a week of buffer in your plan
Once all ten are ticked, the 14 days are mostly a matter of waiting and acting on feedback. When testing ends, our production access guide helps with the application.
If you can't gather 12 testers, GoPlayTester can run the 14-day closed test with real testers on real devices. Follow our setup guide to add the tester group, or order here.
