“Testers were not engaged with your app”
That is the line developers report seeing when Google refuses production access. Google's own help page lists the same reason in its own words: “insufficient tester engagement during the testing period”.
What it means
You had twelve people opted in for fourteen days, and the count was right. What Google could not see was those people using the app. Opting in is a click; it says nothing about whether anybody opened the app afterwards.
This is the refusal swap groups produce. Twelve strangers opt in to each other's tests to pass a count, and most never open what they joined. The count passes. The engagement does not.
What Google asks you
The production-access application asks about the closed test itself: how you recruited testers, how engaged they were, whether they used the features you built, whether their use looked like what you expect in production, what feedback they gave and how you collected it, and what you changed because of it. A refusal for engagement often comes with thin answers to those questions, because there was nothing specific to say.
What to do before applying again
- Run the test again with people who use the app. Fourteen days of real use, by people who open it on most of those days.
- Keep a record while it happens. Which tester did what, on which day, including the days nobody turned up. Specific answers come from a specific record.
- Act on what testers find, and ship it. Google's application asks what changed because of the test. An update during the test is the clearest answer.
- Answer the application from the record. Numbers, days and examples, not adjectives.
What PeerTest does about it
PeerTest is an exchange: you earn testers for your app by testing other developers' apps properly, a short check-in most days and four small missions over the fourteen. Testers cannot be bought there, so everyone testing your app is also testing. The result is a report of every tester on every day, the missed days and rejected work included, that anyone can check without an account.
PeerTest cannot promise you Google's decision, and nobody honest can. It can make sure the engagement Google asks about actually happened, and that you can show it.
See what is open on PeerTest →
Google's words are quoted from its Play Console Help page “App testing requirements for new personal developer accounts”, at support.google.com/googleplay/android-developer/answer/14151465, as read on 22 October 2026. Google changes these pages; where this one disagrees with Google's, Google's is right.
PeerTest · Why production access is refused · Example report · Privacy · Terms · Your Privacy Choices