# Google Play production access refused

> Google refused production access after your 12-tester closed test? Why it happens, how to run the test again, and what to answer this time.

**Production access — Production access refused: more testing needed.** Your request for production access after the 12-tester closed test was turned down. Usually testers barely used the app, fewer than 12 stayed opted in for the 14 days, or the answers in the request were thin.

- Google Play · Production access. Production access refused: more testing needed.
- Interactive page: https://capwr.app/free-tools/app-store-rejection-explainer/google-play-production-access-denied
- Rejection explainer: https://capwr.app/free-tools/app-store-rejection-explainer
- Last updated: 2026-10-14

## What this rejection means

Your request for production access after the 12-tester closed test was turned down. Usually testers barely used the app, fewer than 12 stayed opted in for the 14 days, or the answers in the request were thin.

## Why reviewers send it

New personal developer accounts must show a real closed test before publishing: 12 or more testers opted in for 14 days, actually using the app. Google reads the answers in the request; thin answers or a test nobody used are refused.

## The message Google Play sends

```
Your app requires more testing to be granted production access.

We reviewed your application for production access and found that your app needs more testing before it can be published on Google Play. Continue testing with your closed test testers.
```

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

## How to fix it

1. Keep the closed test running: 12 or more testers opted in for 14 days in a row, actually opening the app.
2. Ship updates during the test that respond to feedback. New builds on the closed track don’t reset the clock.
3. Collect feedback in writing — a form or a group — so you can quote it.
4. Apply again with specific answers: what testers did, what they said, and what you changed.

The [12-tester countdown](https://capwr.app/free-tools/google-play-12-testers) tracks the 14 days and drafts the answers for your next request.

## What to tell Google Play

Replace the [brackets] with what you actually changed:

```
Our closed test ran with [n] testers for [n] days. They [what they did]. Based on their feedback we [changes], shipped in versions [x] and [y].
```

## 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 missing login credentials](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-missing-login-credentials)
- [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)

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