Google Play Missing Login Credentials: App Access Fix

What this rejection means

Part of the app is behind a login and the reviewer had no working credentials — or they expired, needed a one-time code, or only worked in one country.

Why reviewers send it

Reviewers need to reach every part of the app. If it is behind a login and the App access section has no working account — or it asks for a one-time code — Google rejects the release.

The message Google Play sends

Issue found: Missing login credentials

We couldn’t review your app because parts of it are restricted behind a login. Provide valid login details and any other instructions in the App access section of Play Console.

The exact wording changes from one review to the next; the policy name is what to look for.

How to fix it

Create a reusable test account that needs no email, SMS or two-factor code, and keep it active.
Add it in Play Console → Policy → App content → App access, with step-by-step instructions.
Explain how to reach anything that needs a location, hardware or a purchase.
Resubmit.

Fix it with Lovable, Bolt or Cursor

If the app was built with an AI builder, paste this into it, then check the result on a phone:

Add a password sign-in path for a reviewer demo account that skips email and SMS verification, and seed that account with sample data.

What to tell Google Play

Replace the [brackets] with what you actually changed:

We added working credentials and instructions in the App access section. The account needs no verification code.

Got a different message?

Paste the whole rejection into the rejection explainer. It recognises this one and 26 others, in your browser — nothing is uploaded.

Google Play missing login credentials