Do new personal Google Play accounts need device verification?

Do new personal Google Play accounts have to do device verification before publishing

Yes. New personal Google Play accounts must complete device verification before an app can be made available on Google Play, and that requirement is separate from the closed test requirement. Google says the account owner must verify access to a real Android mobile device using the Play Console mobile app before publishing.

The part people get wrong is mixing up device verification with tester requirements. Device verification checks that the account owner can sign in to a real Android device through Play Console mobile app. Closed testing checks that the app itself has gone through the required testing flow before production access is granted. Google documents those as two different requirements on two different help pages.

For new personal accounts, Google Play also requires a closed test before production access. The current rule says the app must run a closed test with at least 12 testers who stay opted in continuously for at least 14 days. Only after that can the account apply for production access. That testing requirement is not the same thing as device verification.

The inconvenient part is that both checks matter. Passing closed testing does not replace device verification, and completing device verification does not replace closed testing. A new personal account can still be blocked from publishing if one requirement is done and the other is not. Google also says the production and pre-registration tracks stay disabled until the testing requirements are met.

If you are setting this up for the first time, the simplest order is: finish identity and account setup, complete device verification in Play Console, then run the closed test with the required testers and days, then apply for production access. Google’s device-verification page says the account owner should sign in with the same Google Account used to create the developer account, then complete the task from the Home page in Play Console.

The device itself also has requirements. Google says you can use any non-rooted physical Android mobile device running at least Android 10. The same device can be used to verify multiple developer accounts, and Google says the verification should take less than a minute once you reach it in Play Console mobile app.

Do not treat buying testers or installs as a shortcut for the closed test. Google says incentivised and inauthentic engagement can lead to enforcement, and the policy page for testing requirements points developers back to compliant testing workflows. The safe route is to recruit real testers, usually from your own network or from people who actually want to try the app.

If you are trying to keep the process simple, DevConnect can help with the tester exchange part, and it stays free to use. It does not replace Google Play requirements, but it gives you a place to find people who will test your app and share feedback without paying for testers. https://devconnectplatform.com

A common failure mode is assuming the account can publish once the app is uploaded and the closed test is live. It cannot. For a new personal account, publishing still requires the device-verification task to be completed and the closed-test requirement to be satisfied. If either one is missing, production access stays closed.

Another thing people miss is that internal testing does not count toward the closed-test requirement. Google says internal testing is available to up to 100 chosen testers, but that is a separate track and does not replace the closed testing requirement for new personal accounts.

So the direct answer is yes: new personal Google Play accounts have to do device verification before publishing, and they also have to complete the closed-test requirement before production access. Those are separate gates, and both matter.

What to check in Play Console

Open the Play Console Home page as the account owner and look for the task about verifying access to an Android mobile device. Then check the testing dashboard for the closed test status, including the tester count and the continuous opt-in period. Google’s help pages place both tasks in Play Console, so you do not need to guess whether one has been done.

What happens if one requirement is missing

If device verification is missing, the account has not completed the publishing prerequisite that Google now requires for new personal accounts. If the closed test is missing, or if the tester count falls below the required minimum before the 14-day period is complete, production access is still blocked. Google explicitly says the 14 days must be consecutive for the testers to count.

Practical example

A developer creates a new personal account on August 1, 2026. They finish identity setup, then verify access to a real Android device on August 2, 2026. They start a closed test the same week, but only 10 testers stay opted in. The app still cannot go to production, because Google requires 12 continuous opted-in testers for 14 days, and the device check alone is not enough.

Bottom line for release planning

If you are planning a release date, treat device verification as a required setup step, not as a substitute for testing. Treat the closed test as the release gate for production access. For new personal Google Play accounts, both must be completed before the app can be published to Google Play.

FAQ

Does device verification replace the 12 tester requirement No. Google documents device verification and closed testing as separate requirements. Device verification confirms access to a real Android device, while the 12 tester, 14 day closed test is the production access requirement for new personal accounts.

Can I publish with internal testing only No. Google says internal testing supports up to 100 chosen testers, but it does not count toward the closed testing requirement for new personal accounts.

What kind of Android device can I use for verification Google says you can use any non-rooted physical Android mobile device that runs at least Android 10.

Where do I complete device verification Google says to sign in to Play Console as the account owner, open the Home page, find the device-verification task, and complete it with the Play Console mobile app.

Does Google say how long device verification takes Yes. Google says the device-verification flow should take less than a minute.

What if my testers drop below 12 before 14 days are complete Google says the 14 days must be consecutive, so the requirement is not satisfied until the tester count stays at the minimum continuously for the full period.