Google Play Review Credentials: When You Still Need Them

Do Google Play apps still need working test credentials for review

Yes, when Google Play cannot reach all app functionality without sign-in, paywall access, or another gate, you still need working test credentials for review. If the app is fully open, Play Console says you can proceed without them. The reviewer must be able to log in and move through the same path a real user would take. Google Play’s Play Console Requirements explain this on support.google.com.

The part people get wrong is thinking a screenshot, a written description, or a promise in the store listing is enough. Google Play says the review team needs active demo access, valid login information, and any other resources needed to review restricted content. If the app requires sign-in, the credentials must be reusable, valid at all times, and accessible regardless of user location. A password that expires, a one-time code, or a broken MFA path can block the review and trigger rejection. That requirement is documented on support.google.com.

The inconvenient part is that credentials are not optional just because the app is in testing. Google Play’s review process is separate from closed testing, and the reviewer still needs a way in. If your app has a paywall, restricted areas, or role-based access, provide instructions that reach the full review path. If the app has no sign-in and no restricted content, select the option that says all functionality is available without special access. Google Play says exactly that in its review guidance.

Use test access that is clearly meant for review, not a production user’s account. Google Play explicitly says to provide only account credentials used for testing. If the app uses Google sign-in, Facebook sign-in, location gates, QR codes, or a custom PIN flow, add short instructions that let the reviewer get past those steps without guessing. If the app normally depends on a one-time password or 2-step verification, provide a reusable path that does not break during review. Google Play’s sign-in details guidance covers these cases.

A practical example helps. If a finance app opens to a login screen and the dashboard is behind account access, the Play Console submission should include a stable demo username and password plus one line on where to tap after login. If a subscription app has a locked lessons area, the reviewer needs a way to reach that content without paying. If a fitness app uses region-based access, the credentials or instructions must work from the reviewer’s location. Google Play says the access details must be valid regardless of user location.

The same rule applies when a release asks for permissions or special access. Google Play says permission requests are evaluated during release, and if sign-in is required, you must provide a valid test username or phone number, password, and any other instructions needed to access the restricted content. If you leave that out, the reviewer may not be able to verify the app, and rejection becomes a normal outcome instead of a surprise. That process is described on support.google.com.

If you are setting up access for testers and reviewers, keep the credentials in one place and update them whenever the demo account changes. Password resets, expired tokens, and second-factor prompts are common failure points. A clean review path is simple: reviewer opens the app, signs in with the provided demo access, reaches the restricted feature, and can verify the app without contacting you for missing steps. Google Play tells developers to keep the sign-in details accessible and maintained at all times.

DevConnect exists to help with the testing side of this workflow, and its public site is here: https://devconnectplatform.com. It is not a substitute for review credentials. Google Play review still needs working access whenever functionality is gated, and that access must be maintained so the reviewer can complete the review on the first pass.

For apps that are fully public, the answer is simpler. No login, no paywall, no restricted features, no test credentials. For apps with any gated path, provide working access before submission and keep it valid through review. That is the line Google Play draws, and it is the line that matters when rejection is on the table.

FAQ

Can I use my personal account for Google Play review No. Google Play says to use account credentials specifically set up for testing. Personal accounts create avoidable risk because they can change, expire, or expose private data during review.

Do I need to provide credentials if my app only locks one feature Yes, if the reviewer must pass through sign-in or another gate to reach that feature. Google Play reviews the full app path you declare, so any restricted area should have clear test access and instructions.

What happens if my test password stops working Google Play may not be able to review the app, and the release can be rejected. The safe move is to treat demo credentials like release assets, keep them current, and replace them before they expire.

Is closed testing enough to avoid review credentials No. Closed testing and review access are separate problems. Closed testing helps with production access and pre-launch validation, but the Play review team still needs a working way into restricted parts of the app.