On this page
New personal developer accounts face a second pre-publish requirement alongside the closed test: verifying that they have access to a real Android mobile device. It's a quick, one-time task done through the Play Console mobile app — and an emulator or a rooted phone won't satisfy it.
What device verification is
Starting in early 2024, Google began requiring developers with new personal accounts to verify that they have access to a real Android mobile device before their app can be made available on Google Play. The stated purpose is user trust and safety: ensuring developers can properly test their apps on hardware before making them available to users, which Google Play states helps improve the quality of apps on the store.
Who it applies to
How to complete it
The whole flow runs through the Play Console mobile app and the same Google account that created the developer account. You'll need a phone or tablet that runs Android 10 or newer.
Sign in to Play Console as the account owner
Log into the web version of Play Console using the Google account that was used to create the developer account.
Open the device verification task
On the Home page, find 'Verify that you have access to an Android mobile device' and click View details.
Scan the QR code
The QR code launches or installs the Play Console mobile app on the device you want to use for verification.
Sign in on the device
Open the Play Console mobile app and log in as the account owner, then select your developer account.
Tap Verify and follow the instructions
Follow the on-screen steps. Device verification using the Play Console mobile app takes less than a minute.
Confirm the task is gone
After verification, the device verification task no longer appears on the Home page in Play Console.
How it fits with the closed testing milestone
For new personal accounts, device verification and the closed testing requirement are two separate gates that run in parallel. The closed test — at least 12 testers opted in continuously for 14 days — unlocks the production access application, while device verification confirms you can test on real hardware before your app goes live. Completing one does not complete the other, and both are checked against the same account.
Common questions
Frequently asked questions
Why can't I see my developer account in the Play Console mobile app?
You're probably signed into the wrong account. Make sure you're using the same Google Account that you used to create your Google Play developer account.
What sort of device can I use?
Any non-rooted physical Android mobile device that runs at least the Android 10 operating system.
Can I use a device I already used for a different developer account?
Yes. The same device can be used to verify multiple accounts.
Does it have to be the device with the phone number I provided at sign-up?
No. The phone number of the device used for verification is not used or collected as part of the process.
Will I need to keep the same device for future verifications?
No. Google may ask you to verify again in the future, but you will not have to use the same device.
What is my device information used for?
Google states it wants to ensure that developers have the basic tools they need to succeed, and may use some of the information for abuse prevention efforts.
Watch the AppsTestLab explanation
Sources & references
Official Google documentation- Device verification requirements for new developer accountssupport.google.com
- App testing requirements for new personal developer accountssupport.google.com
These links open Google's official Play Console Help pages used to verify this guide. AppsTestLab guidance is independent and not affiliated with Google.
Get help doing this