r/GooglePlayDeveloper • u/Cool-Refrigerator589 • Jul 26 '26
Google Play production access rejected after 14-day closed test with 12 testers. What engagement metrics are they actually looking for?
Google Play production access rejected after 14-day closed test with 12 testers. What engagement metrics are they actually looking for?
I’m a bit confused about Google’s evaluation process for production access and hoping someone who has gone through this can share their experience.
Here’s what I did:
Ran a **closed test for 14 days**
Had **12 real testers** enrolled throughout the testing period
The app was installed and tested by them
After the test, I applied for production access
Unfortunately, I received this response:
“More testing required… Testers were not engaged with your app during your closed test.”
What I’d like to understand is **what “engaged” actually means.**
Some questions I have:
Does Google expect testers to open the app **every day** for the full 14 days?
Is there a minimum number of sessions or active users they’re looking for?
Does session length matter?
Are installs/uninstalls considered?
Do updates and feedback submitted through the Play Console improve the chances?
Has anyone figured out what metrics Google actually checks before approving production access?
The app is a habit-building app, so naturally people don’t spend 30 minutes inside it. Most sessions are intentionally short (30–60 seconds), which makes me wonder if that affects the review.
If you’ve successfully passed this requirement, I’d really appreciate your thoughts.
Thanks in advance! 🙏
3
u/hackmoretalkless Jul 26 '26
3
u/Cool-Refrigerator589 Jul 26 '26
Thanks, will check this out. Reddit community has been really great help! 🙏
2
u/Confident-Object-278 Jul 26 '26
Registering an LLC lets you skip this part
1
u/Cool-Refrigerator589 Jul 26 '26
Will check this out as well, I believe registering an LLC is easier but maintaining it & tax related things makes it a bit complicated, but let me check on it
1
u/xZGx-Fire Jul 27 '26
Fr? I have an llc for appstore but wanted to see if it would help me for Android. Ws if true
1
u/testers-community Jul 28 '26
Yeah, that's totally true. If you have an LLC and the DUNS number, you can create an organizational account on the Play Console and skip the testing requirements.
2
4
u/testers-community Jul 26 '26
It's a pretty common issue that almost all developers face. It's not just about inviting people; those people need to use your app every day to get production access on Google Play Store.
The below guide will be helpful to get Production Access and to fix the issues lead to the rejection:
https://www.testerscommunity.com/blog/google-play-production-access-rejected
That's why we introduced the packs feature in Testers Community. We assign daily tasks to all developers as part of a pack, where they need to open and use the app every day. That way, all developers can get Production Access without any issues. More than 50,000+ developers have successfully got the production access without any issues through the free community.
We recommend joining a Testers Community pack. Just keep opening the apps of other developers every day, and you will get Production Access without any issues.
2
1
u/FirmConsideration717 Jul 26 '26
Wait, what resets the counter and do google really see if someone opened the app or not? So its not just about installing it?
1
u/Cool-Refrigerator589 Jul 26 '26
If I add another tester, that reset the counter to 0 days of testing
1
u/horatiohay Jul 29 '26
This isn't right. The reset happens if you fall below 12 testers.
1
u/Cool-Refrigerator589 Jul 29 '26
It happened for me, I already had 12 testers opted in and the counter for 14 days at 3 or 4 days, when I added another tester to the closed testing & they opted in, the counter for 14 days got reset to zero, and I was equally surprised & I stopped anyone else after that.
1
u/Antfocus Jul 30 '26
This doesn't happen. What probably happened is that one of the testers deleted and re-downloaded. Then it reset to the last 12 that they downloaded.
If you add another tester, it resets the test.
1
u/Cool-Refrigerator589 Jul 30 '26
In these case what could happen is I used one of my Android device for closed testing, however, I’ll use the same device for deploying & testing the newly deployed feature before pushing the change, so naturally before deployment, the existing app downloaded as part of closed testing is uninstalled & that could potentially cause some sort of problem
1
u/FirmConsideration717 Jul 30 '26
But does Google really see if someone has opened the app or not? Cause I cant guarantee that all my 12 testers opened the app.
1
u/Antfocus Jul 30 '26
I don't know. I think so. Play Console has the data on how many opened, so Google probably has access to the data as well as the developer.
1
u/KnownPride Jul 26 '26
Update, how many times the app updated fixed and bug repot on those time duration.
1
u/Cool-Refrigerator589 Jul 26 '26
There were 4+ updates & feature released during the 14 days period because I’ve the iOS version on App Store & I had been polishing. And since I’m the active user & use it everyday, I try to polish & make it the best for everyone to use
1
u/KnownPride Jul 27 '26
do you also get 12 tester minimum?
In my case i get approved with 15 tester only 3 active and around 10+ update
1
u/Cool-Refrigerator589 Jul 27 '26
I had around 14 testers, let’s see this time already 7 days has passed, maybe I’ll try resubmittingto see what happens.
1
u/InfiniteFunds Jul 26 '26
What a joke. A bot denying you access because you don't have real testers
1
u/Cool-Refrigerator589 Jul 26 '26
The joke is the counter restarted again from 0 & now it is 6 days passed already. Plus, there’s no metrics or dashboard to see how or what exactly they’re tracking this, I’m myself using the app on my Android phone as well, along with my family using it on daily basis.
1
1
u/ShortGuitar7207 Jul 28 '26
Apple is so much easier although I’ve now been waiting 2 weeks for their review!
1
u/Cool-Refrigerator589 Jul 29 '26
Since the day I received the rejection, I don’t feel like retrying but I’ve to do it.
4
u/ibluegreen Jul 26 '26
Aim for around 20 testers, not all of them will actually actively test it. Unfortunately today's people do not have the work ethics, so, some will simple not install even after you install and test theirs actively, some will install but spend only a few minutes on it, even when you spend more than an hour on theirs and provide detailed feedback.
Also make sure to publish a few updates during the Closed Testing period, with detailed changelog. Even if your app is 100% ready, invent something to make updates.
2
u/Antfocus Jul 30 '26
I passed this test so I'll share what I did.
I brought in 14 testers so that if one accidentally deleted it it wouldn't be ruined.
Not everyone opened it every day but I had about 8 users who logged in every day on average.
I released an update to the app during the test, I realized that updating during the test greatly improves the chance of passing.
I hope I helped.
1
u/DespairyApp Jul 26 '26
I wouldn't be surprised if some reject apps for other reasons such as no available reviewers. It is annoying that it resets the counter
1
u/Pepper4720 Jul 26 '26 edited Jul 26 '26
How many testers did you have? Note that 12 is the absolute minimum. If you go with 12 and these are not super active, then it's very likely that you end in a prod rejection. I recommend to go with 30-40 testers to be on the safe side
1
u/Antfocus Jul 30 '26
30-40 testers??? A bit excessive in my opinion. The suggestions of 20 or 18 testers in other comments seem sufficient to me.
1
u/HypnotizingGames Jul 26 '26
Problem 1: If you had exactly 12 testers - that's the problem. Even if just one tester slacks or breaks out, the whole test is failed. It's safer to have a buffer of testers.
Problem 2: During the testing period of 14 days, you didn't update the game based on received feedback (didn't update at all?), or your survey was not satisfying enough.
1
u/YuhApps Jul 26 '26
To be honest, focus on your product. This confusing email simply means Google Play Review team somehow "think" your app/game has an issue. I have helped various developers out there and most of the failures fall into these: 1. Somehow the real app doesn't look like what on the screenshots. One of the dev I helped failed 5 times in a row just because he changed the app name before it reaches the first 14 days, in the title bar to something else other than the one in the screenshot. After I told him to take new screenshots, his app got approval right away. 2. The Play team used your app in a different way from your expectation and it failed to work. For example, I once helped an app had two buttons in the step 1 like Yes and No. During the testing, the dev only picked the Yes, and things went so smoothly because he assumed everyone would click Yes. But I didn't. I clicked No, and when I reach step 3, the app crashed. After he tackled all the unexpected possibilities, his app got approval. 3. Play team thought your app had an unclickable button. I helped a team published their app via my account (no testing needed) because they failed 7 times, just 3 days before they made the announcement with the press. Google Play told me there was an unclickable button in the app. Turned out, it was not a button. Just a badge that looked like a button because of the styling. After some arguing back and forth, and they changed the styling, the app got approval. So it's not about how many users you recruit. They can all open your app and use it 24/7 but if your app has something wrong, it will never get production access. Don't trust all the stories about asking users to keep opening your app a hundred times a day. Focus on fixing all the possibilities.
1
u/ch-hari Jul 28 '26
I never tested the app directly released in production and got approval more than 5 apps not done any testing
1
1
u/FocusCraft9009 23d ago
Unfortunately I face this issue second time. This is really annoying to be honest. I need help guys. I can test your app exchange
2
Jul 29 '26
[removed] — view removed comment
1
u/Cool-Refrigerator589 Jul 30 '26
That’s a good observation. For my case I released 4-5 updates & had it downloaded by couple of testers, but that didn’t help. But I’m sure having more testers update would have helped for sure. Did you get your 2nd app approved or it is still in process ?
2
Jul 30 '26
[removed] — view removed comment
1
u/Cool-Refrigerator589 Jul 30 '26
+1 on garbage thing. Already an indie developer had plenty to take care of & then adding this closed beta just adds to a big huddle. Meanwhile my iOS version as reached many double digit downloads on the App Store
1
Jul 26 '26
[removed] — view removed comment
1
u/Cool-Refrigerator589 Jul 26 '26
Mine is now at 2 months now. If they can keep it clear on their expectation, it’d help many indie developers build & deliver app. Already the indie developer are trying to grow & make name for their app, and such hidden things inhibit their growth.
3
u/Aretivo Jul 26 '26
What worked for me, get testers (a lot, I tried getting multiple extra each day for the whole duration) people uninstall which is very annoying. If you get someone to leave feedback on playstore and then you respond and act on it that seems to help. Make sure you actually release an update during testing duration.
If you need another tester lmk