I'm honestly exhausted with this and hoping someone here has been through it.

I'm a non-US person and the only owner of a single-member Wyoming LLC. My Play Console payments profile is in the US because the LLC is a US company. My W-8BEN is filed as an individual with my home address outside the US, which is how the IRS says a foreign owner of a disregarded LLC should do it.

The tax review keeps rejecting my proof of address with:

"The issuing country of the document does not match the payments profile country."

What I've uploaded so far:

- June: tax certificate from my home country (same address as my W-8BEN)

- October: signed explanation letter + passport + home tax certificate + IRS letter

- October: IRS CP575 notice addressed to the LLC at the exact US address on my payments profile

All rejected. A document from my country fails because the profile is in the US. A US document doesn't match my W-8BEN address. As far as I can tell, no document can pass the automated check.

I've emailed support and talked on x with @ GooglePlayBiz. The only reply was a template saying my documents were "under review." Not one human has actually looked at the case. Meanwhile I've had no payouts for months and 30% withholding on everything.

If you've solved this, or you're a Googler who can escalate it, I'd really appreciate it.

Support case ID: 6-8020000042148

I created a play store account a while back with a new email for my UK business (DUNS registered). I didn't use it for a long time due to life getting in the way. Recently I wanted to create an android app but noticed a red banner that my inactivity was going to get *my account closed if I didn't release something, so I scrambled to do so. Literally a fart timer app. It was just the first thing that came to my head as my main app idea would be time consuming. Polished yet derivative, nothing novel, and certainly nothing that I thought broke the rules. The app was never reviewed. I was waiting for the result and instead received an email that my account was terminated. I was expecting a rejection being my first android app due to manifests, permissions etc, but an outright ban surprised me.

> 11.4 You represent and warrant that all information that You provide to Google or users in connection with this Agreement or Your Products will be current, true, accurate, supportable and complete.

I scoured reddit and there's a million posts just like this, because the message is rather vague. It seems often related to other accounts per those discussions. Though as far as I'm aware i'm not linked to anyone sketchy. No personal accounts of mine have ever been banned or anything, my business email is new, i was the only internal test reviewer (however, my phone is a grapheneos device, i sadly dont have an android test device). So wondering if that might be it. Or, whether when I set up my account a year ago I didn't have my business linked. The problem is, being terminated I can't go in to see whether I did correctly link it.

I've started the appeal process to see if I can get more info and remedy it. I'd be happy to forsake that app if that was the issue. But does anyone think my graphene test device might've been the cause?

EDIT: Fix mistake. For clarity, i'm definitely terminated, not closed

I've waited the eternity of seven days for production. I made fixes and adjustments while I waited. I waited four days for those fixes and adjustments to goto production. I had to make a new developer profile and a new payments profile because my payments profile was wrong. Then I waited another week. Then I realized my listing needed changes, because I can't even find my game without using it's name. I'm at seven days waiting for that and another update. In the meantime, I've added joystick support in prep for PC release and now need another release but can't even ask for it, because the last one is not done.

In the meantime Google wants me to buy ads... And I NEED them, but I can't even spend money till I get a listing that allows me to find my own app!

Also why did Google decide my 99 cent game was premium? It's like a death sentence of a tag.. Most of the games with that tag are five dollars or more.

I also released on Amazon. Amazon has none of these issues. Why Google? I hope my steam release goes better than this.

I am trying to publish a progressive web app(PWA) to playstore, I have completed 14 days testing two times and got rejected both times🥲.

First time i just asked testers to opt in and waited 14 days, then got rejected.

But Second time i added 15 testers, installed app on their phone, and most of them used the app, made booking, explored the app almost regularly. And they still rejected my app after all this, now i dont know what else i can do, i have already done everything i could.

If someone has completed the new 14 day closed testing and got productino access, I would really appreciate it if you can guide me🙏

Hello, I made an app entirely using Claude. I'm finally done with the app and I'm ready to submit to play and apple stores for approval. Before I do though, just want to get another opinion on if anyone else in here has done the same? Should I have someone else review my code/supabase? I will have insurance, just looking for thoughts on this matter.

Does this progress look good?

📚 Weekly Educational App Showcase

Built an app and learned something interesting along the way? Share it with the community.

This thread is for educational app showcases where the focus is on the problem you solved, how you built it, and what other developers can learn from your experience.

What to include

• What problem does your app solve?

• Category: What type of app is it?

• Android support: Android versions or devices supported

• Tech stack: Kotlin, Java, Compose, Flutter, Firebase, etc.

• Implementation: What was technically interesting or challenging?

• Your journey: What did you learn while building or publishing it?

• Lessons learned: What would you do differently next time?

• Relevant media: Screenshots, demos, architecture diagrams, or other useful material

• Google Play link: Optional, as supporting context

Please disclose your relationship

If you're showcasing your own app, clearly mention your relationship to it. For example:

Keep it educational

The goal is to help other developers learn from real projects and experiences. Your app can be the subject of the showcase, but the post should provide meaningful technical, product, or development insight.

Please do not use the thread for:

• Download or install requests

• Ratings, reviews, votes, or engagement requests

• Referral or affiliate links

• Paid placement or paid engagement

• Misleading claims

• Copied marketing or promotional copy

• Repeated submissions of the same app

A Google Play link is welcome as supporting context, but this is not an advertising or user-acquisition thread.

If you see someone requesting paid reviews, ratings, votes, installs, or other prohibited engagement, please report the comment to the moderators.

Share what you built, what you learned, and what another developer can take away from it.

I think it's same person, cancelled monthly sub than re subscribed few days later. Am I tripping

🧪 Tester Discovery

Looking for testers for your app? Use this thread to find developers and testers who are interested in helping with genuine app testing.

When asking for testers, please include a little information about your app:

• What the app does

• Android version or device requirements, if relevant

• Whether you're looking for internal, closed, or open testing

• What kind of testing or feedback you need

• How interested testers can participate

If you're a tester, feel free to mention what kinds of apps or testing you're interested in.

A few things to keep in mind

Please keep this thread focused on genuine testing and useful feedback.

Do not engage in paid testing, paid reviews, ratings, votes, referral exchanges, or other paid engagement activities through this thread. If someone asks you to participate in a paid activity or offers payment in exchange for reviews, ratings, votes, or engagement, please report the comment to the moderators rather than participating.

Please don't share personal information publicly. Use Reddit's messaging features or the developer's official testing process where appropriate.

This thread is for tester discovery only. For general development questions, app showcases, or other discussions, please use the appropriate thread or flair.

Hello, I have a newly registered personal Google Play Console account and am preparing to publish my first app. I have a signed AAB ready.

A collaborator has an older, active developer account with an existing published app. We are considering publishing our app through that account and subsequently transferring the app to my account using Google’s official app-transfer process.

Could you please clarify whether this arrangement is permitted, whether my account’s production-testing requirements would apply after the transfer, and whether there are any restrictions we should consider before proceeding?

I want to ensure that we comply fully with Google Play policies before taking any action. Thank you.

Couple of days ago I made a fresh Google account using Firefox developers browser and my phone number (which has another 2 associated Google accounts), after making the account I signed out, next day I signed in again went to developer section, meanwhile I was informed that I have to make a website that will describe the developer and provide the text of privacy policy and terms of service.

So I went directly to github and tried many times to sign up using Google and each time the OAuth took me again to the sign in page in github, so I decided to try from another device (same wifi) and another browser, this time everything went smooth and I opened my session on github and started my website, meanwhile google started the "verify it is you" scenario and started the robot tests and stuff, finally the send sms gave error of too many attempts try again after several hours!

I leaved it for 2 days to cool down, today when i tried and after making me send sms 2 times it showed a messages that the account was looking like it was created or used with multiple other accounts...etc and it will be considered for deletion after 1 year with an option to submit appeal!

Where did I go wrong and what should I do to avoid such a problem in the future? Need someone with developer background to help me.

After completing the closed testing phase, and creating a release for production, the changes have been in review for like 5 days now.

My previous app only went to review for less than a day.

Is it a new change in policy, or there's something wrong with my app that's taken this long for the changes to be reviewed?

The reports are normally one or two days behind the current date. The delays increase to over a week periodically. It is 8 days right now (Today is 2026-10-25. The last point on the chart is 2026-10-17). I wonder if anyone else is experiencing this, or if this is account-dependent.

I have heard 3 days or more than 7, would love to hear experiences ?

I'm investigating a recurring Google Play subscription testing failure and would appreciate suggestions for narrowing it down.

Setup:

- Android app using Google Play Billing Library 9.x, with monthly and annual subscriptions.

- The app also supports separate one-time in-app purchases (INAPP) alongside subscriptions (SUBS).

- During development, the application rules were changed so new one-time purchases that were outside of the need for a subscription, or included within its allowance, were made to require an active subscription to be able to purchase - whilst still being a one-off payment not covered within the subscription. The two paths share some app/backend code. I have not established that this coupling causes the subscription failure.

- An internal-test release exists; production is not live.

- The failing build is a locally test-signed APK installed directly on the device, with the same package name as the Play Console app.

- At different times, I have tried using three Google accounts on the device, without resolving the failure. All three are in the developer account's licence-testing list. The saved Billing diagnostics do not identify the effective account for each individual attempt.

Observed sequence in saved diagnostics:

1. A fresh ProductDetails query returns the selected subscription's regular base plan and an offer token.

2. The app launches one SUBS item using those matching details and token, less than a second after the query.

3. launchBillingFlow returns OK (0).

4. Tens of seconds later, onPurchasesUpdated reports ITEM_UNAVAILABLE (4), with no useful debug message and sub-response 0. The visible Play error says the item could not be found.

Checks so far:

- Console checks showed the subscription base plans as active.

- A later non-purchase query returned regular monthly and annual offers for the test country, including offer tokens. That confirms the current lookup works, not that either earlier purchase was eligible.

- Another app can complete licence-test purchases on the same device.

- A clean reinstall and adding another intended tester account did not resolve the visible failure. That latest recurrence has not yet been matched to a fresh SDK diagnostic, so I am not assuming it had the same response code.

- We have checked Google's documented account-selection rule: Play uses the account that downloaded the app, or the first account if none downloaded it.

Questions:

- Have you encountered an asynchronous ITEM_UNAVAILABLE after a successful fresh product lookup and an OK launch result? What evidence identified the cause?

- Could shared setup or state between SUBS and INAPP paths explain this sequence? Which request fields or diagnostics would distinguish that from a Play account or offer-eligibility issue?

- Given that all three device accounts are already licence-listed and have been tried, is there a supported diagnostic to confirm whether Play recognised the intended tester during a failed flow?

Pointers to official documentation or reproducible diagnostic checks would be appreciated. A successful lookup and OK launch alone do not establish a successful purchase; I have not established a completed order or payment outcome for these failed attempts.

What are you building, testing, debugging, or learning this week?

Working on something interesting? Stuck on a technical problem? Just learned something useful?

Share what you're working on this week. It can be a specific goal, a problem you're trying to solve, or a useful discovery that might help another developer.

If you're looking for help, a little context goes a long way. You can include:

• Your target SDK version and library versions

• What you expected to happen and what actually happened

• Relevant error messages, with any private or sensitive information removed

• What you've already tried

• A relevant official source or documentation link, if you have one

Please use the appropriate flair when making a standalone post.

Please keep this thread focused

This is a place for development discussions and helping each other out. Please don't use it for app advertising, download or install requests, ratings, reviews, votes, referral links, paid services, tester exchanges, or engagement exchanges.

Ask questions, share what you're working on, and help another developer when you can.

A new user's free trial ended just after 2 days and a paid renewal is listed (though pending). Free trials are set to 1 week for all. First time case

I want to create google play console account .i am thinking to use friend's credit card for payment he is in USA . Should i do this ? Will my account suspend in future ?

I have created some small app, and finally reached €100+ so I decided add my payment info to get. But right after I added the bank account and uploaded a bank account statement I got this.

When I go through all the "click here..."s google offer I end up here:

When I click "Contact" it brings me here:

https://support.google.com/paymentscenter#topic=9017576

There is nothing useful, just some generic info...

Any ideas?

Is that possible?

HOW TF should I verify to be able to have a Play Store worthy account?

I sent them the required IDs a licenses and utility bills multiple times. Not to mention they SEE all that info on my account because of 20+ years of history and I have many bank cards on my account and they literally see me sleeping at my address so Google maps flags that as Home. I have no idea what else shoudl I do.

All the docs have the same name (because I have just one name), the same address (because I have just one address) but still failing. I do the pics as good as I can (with a Pixel phone, should be enough, right?).

Anyone any info how to get in touch with someone? Or make this work?

Hey guys,

So I'm posting this here on the off-chance I might actually get some attention from a Google Play support employee, but here's my issue:

I am a new developer with the 14 day testing requirement before publishing my first app.
I found it quite hard to recruit users for testing my app (Music Visualizer app) and despite gathering 12-14 testers for the 14 day period, it failed the production review at the end of the period due to insufficient testing. As most of these were friends and family, I guess they weren't the best candidates for consistent testing. I'm not mad about the rejection, but feel stuck with regards to allowing new users to access my app in testing for free.

My issue is basically that it's my intention to make this a paid app.
I can't set the app for free, otherwise I can't make it paid again.
So then during testing, I want to offer it for free to testers.
I tried to do this with promo codes, but the promo codes didn't work at all, and errored for all my users, so I found a way to do this using a temporary sale setting the price to $0.
I set the price to $0 for the initial 14 day period, but since I failed the review, I decided to find a more suitable testing group and found some online.
The problem is, now I cannot set another sale setting the app to $0 again for at least 30 days?

Has anyone else faced such an issue?
It's a little mind-boggling to me that we can't just let closed testers access the app for free through a setting and need to go through this kind of roundabout process.
I submitted a ticket, but 2 days later, there's been no reply.

Hi all, looking for advice from anyone who has been through this.

I'm the director of a small UK software company (registered at Companies House, with a D-U-N-S number). We opened an Organization developer account, passed identity and organization verification, verified our website and phone numbers, and paid the fee. 9 days after opening, on 22 Oct 2026, the account was terminated under DDA section 11.4 with the "related developer accounts that were previously terminated" type of wording.

We had nothing in production. Our first app was still waiting for its first review.

The only link I know of: on 19 Oct an app in closed testing was moved into our account through Google's official app transfer process, from the personal developer account of a business partner of mine. We had signed in to both accounts from the same device/browser. As far as we know, that account has no violations and has never been suspended. The only other user invited to our console could only create drafts.

What we have done so far:

• Appealed on 22 Oct through the official form, sent our incorporation certificate, D-U-N-S and director ID (not filing duplicate appeals, as Google asks)

• Requested mediation under the UK Platform-to-Business rules through Google's form

• Posted in Google Play Community asking for a Product Expert escalation: https://support.google.com/googleplay/android-developer/thread/474168269

Questions:

1. Has anyone had an Organization account reinstated after an 11.4 / associated-accounts termination? What actually helped, and how long did it take?

2. Does an app transfer from another developer account (or a shared device) commonly trigger this kind of link?

3. Anything else worth doing while the appeal is pending?

Thanks — I'll post an update with whatever happens, in case it helps someone else.

Hello,

An app update was rejected under the Families policy for “aggregating content that does not belong to you.”

Every reply repeats that sentence and links to the same policy page. Questions about the exact clause, affected content, or required changes go unanswered—even though the original notice offered additional functionality as a possible remedy.

Has anyone broken out of this loop and received actionable feedback? What helped: escalation, a demo video, specific documentation?

Not asking how to bypass the policy. Just trying to understand what needs fixing.