# Google Play missing login credentials

> Google Play couldn’t review the app because of missing or invalid login credentials? How to fill in App access so the reviewer gets in.

**App access — App access: Google couldn’t sign in.** 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.

- Google Play · App access. App access: Google couldn’t sign in.
- Interactive page: https://capwr.app/free-tools/app-store-rejection-explainer/google-play-missing-login-credentials
- Rejection explainer: https://capwr.app/free-tools/app-store-rejection-explainer
- Last updated: 2026-10-14

## 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

1. Create a reusable test account that needs no email, SMS or two-factor code, and keep it active.
2. Add it in Play Console → Policy → App content → App access, with step-by-step instructions.
3. Explain how to reach anything that needs a location, hardware or a purchase.
4. 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](https://capwr.app/free-tools/app-store-rejection-explainer). It recognises this one and 26 others, in your browser — nothing is uploaded.

## Other Google Play rejections

- [Google Play Broken Functionality rejection](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-broken-functionality)
- [Google Play webview and minimum functionality](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-webview-minimum-functionality)
- [Google Play invalid privacy policy](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-invalid-privacy-policy)
- [Google Play Data safety section inaccurate](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-data-safety-inaccurate)
- [Google Play account deletion requirement](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-account-deletion)
- [Google Play photo and video permissions policy](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-photo-video-permissions)
- [Google Play Payments policy: use Play Billing](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-payments-policy)
- [Google Play Metadata policy violation](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-metadata-policy)
- [Google Play production access refused](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-production-access-denied)

## Fixed it? Ship the new build to Google Play

CapWrapp builds and signs the Android app from your GitHub repo, bumps the version code, and uploads it to Google Play — then promotes it to production when you are ready.

[Get started free](https://capwr.app/login).

## About CapWrapp

CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)