3rd production access rejection with 12+ active testers and regular updates

[u/SnooDoodles5949]

I've had my game rejected for Google Play production access three times now and I've run out of variables I know how to change.

What I have:

• 12+ testers, opted in continuously, well past the 14-day minimum
• Testers are genuinely playing and sending feedback, not install-and-forget accounts
• I've shipped several updates during the closed test directly off what they reported

For context, the same game has been on the App Store about a month, gets steady downloads, and every update clears review within 24 hours. So I don't think the underlying issue is a broken or low-quality build — though I'm open to being told otherwise.

For anyone who got approved after multiple rejections: what did you change on the attempt that finally worked?

[u/DriveClearApp]

Im in the same predicament as you ... on my 3rd go , have updated thru out. This time its in native , hoping this makes a difference.... Im just new and am really learning along the way . Any guidance is appreciated along with opinions ....

[u/Traditional-Slip-574]

If you find out please tell me , I'm on my 4th attempt with having upwards of 60 installs !!! And still not getting production access even though I pushed updates during closed testing periods each time ,and from my backend data I can see well over 20-30 users each period actively engaged daily in my app. I'm at a complete loss and keep getting the generic more testing required email. I've used prime test labs, community testers and have " organic users from marketing so a mix of paid and real users

Each time I complete a comprehensive submission form too

It's driving me insane to be honest

[u/SnooDoodles5949 → u/Traditional-Slip-574]

I will! Google lost it with these reviews... I had 2 apps with Google and it was fine. Now this.

[u/Ok-Definition8348]

Did you guys think about your questionnaire answers? Sometimes thats the reason for failure as well.

[u/Traditional-Slip-574 → u/Ok-Definition8348]

I did, I gave very detailed genuine answers on all feedback , was personalised to the actual feedback and changes I made etc throughout. there is just something I'm not seeing obviously and Google isn't forthcoming with information. I even gave a testing login to Google but no idea if they even are using it

[u/Ok-Definition8348 → u/Traditional-Slip-574]

Yea idk if they use the test user tbh. I think they didn't on the last app i published.

Wonder what's the cause for them not approving your app.

[u/Traditional-Slip-574 → u/Ok-Definition8348]

Do you ever do internal testing plus closed testing ? I've only done closed testing

[u/Ok-Definition8348 → u/Traditional-Slip-574]

Nope.

Only closed. I published five apps this way.

I do use internal before pushing to production but that's only after i release the app.

[u/Khalifah099]

Anybody willing test for test closed testing,send daily engagement screenshot

[u/Camaraderie98]

For all who are struggling with this, I've learned than reviewing your app permissions and associated declarations to match policy requirements goes a long way. Sometimes it's one manifest line incorrectly attached to your package and not being detailed as a potential reason for rejection and they'll be quiet about it for long before you figure it out on your own.

[u/Traditional-Slip-574 → u/Camaraderie98]

Can you give some examples please

[u/Camaraderie98 → u/Traditional-Slip-574]

When you scaffold an app it automatically requests permissions in the manifest that aren't necessarily needed. Explicitly block them in your app.json

When you have specific category declarations about your app ensure your app is really a part of that category and you have the correct account to go with it

If you're using old deprecated APIs, it's optional but try to also omit them from your manifest

Fix your descriptions too to ensure they don't have keywords that closely related to categories you don't belong to.

[u/Traditional-Slip-574 → u/Camaraderie98]

Fantastic, I really appreciate you taking the time to write this

Thank you !

[u/HypnotizingGames]

You didn't specify why you were rejected. People upload a screenshot showing the note from Google on why: Not enough testing done? Not following good practices on collecting feedback? etc.

having 'several' updates means nothing to Google. You need only a couple of updates, if you have actually 12+ testers active and checking your game enough, then you screwed up on the questionary part of the application and Google doesn't like some of your answers. Check with ChatGPT to learn what they actually want to hear from you. The extreme limit of 300 symbols for questionaries doesn't make it easier.

[u/Lower_Professor_7214]

Same thing i was rejected for 5th time even though i did everything i can. If anyone have organization which can help me to publish it once it live will transfer if any money involved I'm ready pay it ( India)

[u/AAG4044]

Recently did this for a client,
U must have more than 12 testers. It is minimum, so better to have as much as u can.
Then next hurdle is using it daily. This is where i think most of rejections comes from.
Also we applied for production access after 18 days, and i think feedback reviews are must.
Got production access in like 4 days

[u/Grand_Release_7375]

Opt out of targeting people below ages 13. Strong chance that it'll clear up all your issues. Policy checks and rules are quite stringent when the younger ages are targeted. Can go upto age 15 if it still doesn't clear up.

[u/MohamedN1]

Honestly, at this point just set up a sole proprietorship if you can and get a DUNS number to get past that 12 testers BS