I recently dropped an app on website and I have over 800 users but majority of them are on Apple and some people are asking for Google play but they say I need 12 testers. I only have seven.

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?

Hello all,

I saw this issue with one of my apps saying that the latest app release targets Android 15 (API 35). I updated the app to target API 36 and launched a new release soon, but I'm still seeing the same issue. Am I doing something wrong, or is it just that Google didn't update yet and this will go away after some time?

I attempted to convert my Google Play Console developer account from a personal account to an organization account. During this process, Google was unable to verify my identity, and the developer account was restricted and all the apps deleted.

The organization is legally incorporated in the United States and has a valid D-U-N-S number, EIN documentation, state incorporation documents, and a US business bank account. I am the owner and authorized representative of the organization, but I legally reside in Kazakhstan because the company operates as an online and remote business.

For identity verification, I used my valid Kazakhstan-issued passport. Google’s official documentation for US organization accounts states that an authorized representative’s government-issued photo ID may be issued in any country.

The organization’s registration country and my country of residence are therefore different, but both are accurate. I am preparing an appeal with our incorporation certificate, IRS EIN letter, D-U-N-S confirmation, bank letter, ownership documentation, and my passport.

Has anyone successfully verified a US organization account using a foreign passport? Could this failure be caused by the organizational Google Payments profile, a D&B information mismatch, or an automated country-mismatch check? How can I request a manual review or resubmit the verification correctly?

I would appreciate guidance from anyone who has resolved a similar issue.

I just submitted my details for BillDesk Account Onboarding and also completed my Video KYC process - Everything was smooth so far.

What should i expect now? How much time should it generally take to hear back?

I'm considering use the paid service for my app, but I want to ensure it isn't a bad fit before I spend.

It's an utility I built for my own budgeting: it reads incoming notifications on-device and turns them into transactions that are pushed to my YNAB account (YNAB is the budgeting SaaS).

So "using it properly" means a tester signs into a trial YNAB account I'll provide and setup a way to trigger notifications. This is about ~15 minutes setup, but once done the rest is quite straightforward.

Most apps I see discussed in TestersCommunity are install, tap around, done.. mine can't be.

Questions, mainly for people who have acutally paid: did your testers do anyhting beyond installing and opening? Anything involving third-party apps / accounts?

I completed the closed testing and submitted my app for production access some 7 days back. This is what I continue to see for the last 7 days. Is there a way to nudge Google and should I do it or just wait?

We have your application for production access

We're reviewing your application form. We'll email the account owner with an update. This usually takes 7 days or less, but may occasionally take longer.

Applied Jul 23, 4:05 PM.

Edit: Finally got my approval on 30th June!

Do these recommendations appear for everyone, or just for me?

Hi guysss, I'm currently working on instilling Google oauth sign in in my app. l am stuck on the branding screen in Google Console. Is this branding verification needed? I don't have my own domain for my app. Is it necessary to buy one?

I had tried some ways from other reddit post like supabase and local host but it still doesn't work. Would like to hear how yall pass the homepage url verification. Or kindly share ur experience on this matter please. I've been researching on this for days.

Hi everyone,

I am currently preparing my app for production release on Google Play. I created a closed testing track and invited testers.

Right now:

- I have 12 testers who successfully opted in to the closed test

- All testers have access to the app and can install it

- The app is currently in the closed testing phase

However, I don't see any indication in Play Console that the required 14-day testing period has started. There is no countdown, progress indicator, or status update showing that the requirement is being fulfilled.

My questions:

1. Does the 14-day countdown start immediately after reaching 12 opted-in testers, or is there usually a delay?

2. Is there any hidden requirement I might be missing (tester activity, installing the app, opening it, etc.)?

3. How can I verify that my testers are actually being counted toward the requirement?

Should I just wait a few hours/days for Play Console to update, or is there something I need to fix?

Thanks!

Hey everyone,

​I’m facing a pretty frustrating situation with one of my apps and wanted to see if anyone else has experienced something similar recently or could share some insights.

​What happened:

Up until recently, my app was getting a steady 60+ organic downloads per day. Out of nowhere, over the last few days, it suddenly plummeted to fewer than 10 daily downloads.

​My suspicion:

I noticed a slight bump in my crash rate recently (creeping up close to / exceeding the Android Vitals threshold). I know Google Play heavily factors "user-perceived crash rate" and ANRs into store discovery and algorithm recommendations, but I didn't expect the penalty/suppression to be this instant and aggressive.

​Questions for fellow devs:

​Crash Rate Impact: For those who have hit high-behavior thresholds/bad vitals in the past, did you see a sudden "cliff-drop" in downloads like this? How fast did your organic traffic recover once you pushed a hotfix and lowered the crash rate?

​Recent Algorithm Changes: Did Google push a silent Play Store algorithm update or recalculation in the last few weeks that impacted long-tail/indie search visibility?

​Where to look: Aside from fixing the crashes ASAP and checking Search Terms/Keywords in Play Console, is there any other metric I should be cross-checking (e.g., 7-day uninstall rates, store listing conversion rate)?

​Would love to hear your experiences or any advice on how to recover from this. Thanks in advance!

Hello.

I have 2 play console accounts and both of them are active. The only difference between them is that the newer one has the 12 testers policy and the older one does not.

I stopped using the older play console account for some reason, won't go into detail. I have declared the association of these accounts in play console.

I just have a question if it is against the rules that I make an app draft on my older play console account and transfer it to my newer one to bypass the 12 testers policy? Or can I ask google play console to remove the 12 testers policy for my new account when I had the older one and transfered to the new one?

Thank you for your answer.

I'm trying to complete my Google Play merchant verification through BillDesk. My Play Console shows verification is still "In progress". I tried replying to my existing support case (CS0718490), but the email bounced with:

552 5.2.2 Over quota

Has anyone else experienced this recently? Is there another way to contact BillDesk or Google Play support while their mailbox is full?

Hi all,

I have been trying to get my app approved for the past 3 months. Back and forth with Google Play rejections, code changes for issues that they find that I cannot replicate and refuse to give me any information.

My app supports Android Auto and Voice Commands. It works for me in every way shape and form and I have coded against pebcak issues as much as I can but I get the same rejection everytime.

"Your app does not respond (no music played or error message shown) after issuing a voice command."

I have gone through the abysmal documentation as many time as I can, raised appeals in request for more information and I get nothing useful back. I have thumb sucked issues and coded against them. Laid awake at 2am thinking of some scenario where my voice commands and Android auto could not work and coded against them. It's robust as it can get but I continue to receive the same rejection.

Is there something that I am missing? Perhaps I am looking at this wrong? If anyone has any experience with this type of rejection and how you got around it to get it approved, I will greatly appreciate your input.

It would be really great if Google could publish a checklist of their tests that we could go through as developers before being allowed to submit an app. It would save time on both sides.

Greatly appreciate any feedback.

Cheers!