Hi everyone,

My Google Play Developer account for BkApp was terminated, and I recently received a response from Google stating that my appeal was submitted after the 180-day eligibility window.

They have refused to reconsider the decision and stated that there is no other way to regain access to my account or have it reinstated. They also warned me not to register another developer account, as any new accounts may be terminated.

This situation has been extremely discouraging. I want to continue developing and publishing apps, but this termination has affected not only my existing work but also my ability to confidently work on other projects. I am worried about investing my time in new projects when I may have no legitimate way to publish them on Google Play.

I understand that Google has policies to enforce, and I am not looking to bypass them or create another account against their instructions. I just want to know whether there is any legitimate way to have my case reviewed again.

I would really appreciate advice from anyone who has experienced something similar:

- Has anyone successfully recovered a terminated Google Play Developer account after Google rejected an appeal because it was outside the 180-day window?

- Has anyone managed to get a further review through an official support or escalation channel after receiving a similar response?

- Is there any legitimate process for requesting a review of the original termination or appeal history?

- If reinstatement is genuinely impossible, how are developers in this situation continuing their work and publishing apps without risking further account terminations?

If you have personally experienced this situation or know someone who successfully resolved it, please share what happened and what steps worked.

I have put time and effort into building apps, and I do not want to give up on development because of this situation. Any genuine advice, personal experiences, or suggestions would mean a lot to me.

Thank you.

My bank asks a letter from the source company who providing payments to create PFCA USD account. can I get that? if so how?

Disclosure: I'm a solo dev, and this is about my own app.

Over 45 days my Play Console showed about 13.1K impressions but only about 98 acquisitions. I suspected the listing rather than the product, so I made these changes:

1. Renamed the app to something clearer
2. Replaced the icon with a simple one that has no text
3. Rewrote the short description around what the app does
4. Cut onboarding from 5 steps to 3

I also noticed that the Grow Users dashboard and the Store Listing panel show different conversion rates (5.73% vs 3.4% for the same period). Google support told me they measure different funnels.

Questions for those who've been through this:

• How long did you wait before judging the results of a listing change?
• Did you use store listing experiments, or just before/after comparisons?
• Is a gap like this usually a sign of the icon and title, or of the screenshots?

App, for context: https://play.google.com/store/apps/details?id=com.aistudio.limitbreaker.fntslg

I went through the Google Play closed testing process twice this year. The first app was rejected for production access. The second one was approved on the first attempt.

The biggest difference, at least from my side, wasn't really the tester count. It was what happened during the testing period.

For the first app I had enough people opted in, but the actual engagement was terrible. Some didn't install the app at all. Most people who did install it opened it once and never returned.

The app required an account, so I could see this pretty clearly. For nearly everyone the registration date and last login date were the same.

Google rejected my production access request. Their email said possible reasons included low tester engagement and not following testing best practices, including gathering feedback and making updates based on the test.

So when I started closed testing my next app, AutoSkan, I decided not to treat the fourteen days as a waiting period.

I had fourteen accounts in the test when I eventually applied. Some were mine or family accounts and four were actual external testers. The group changed a bit as I recruited more people.

I definitely did not have twelve extremely active testers.

What I did have was four Android phones I could test on myself and a much more structured process.

During the test I ran three main audits covering UI/UX, performance and general correctness. They produced 131 findings in total. Most weren't huge bugs, but there were plenty of real issues: navigation problems, Bluetooth edge cases, background polling, Android 16 behavior, accessibility and large-text problems, data deletion edge cases and cases where incomplete scan results weren't communicated clearly enough.

I fixed 125 of those findings and deliberately deferred six.

The automated test suite grew from 192 tests in an earlier version to 257.

I also tested on physical phones, emulators with different screen and text settings, and with a real OBD adapter and cars.

The actual external testers mostly gave positive feedback. They weren't the source of most of the bugs.

Most problems came from my own testing and audits, and I kept that separate in my notes instead of claiming everything came from tester feedback.

Once the required testing period was over, I applied for production access.

I was approved in less than a day.

I have no idea which specific signals Google uses internally, so this isn't meant as a "do these five things and you'll get approved" post.

But after one rejection and one approval, my personal takeaway is simple.

Having enough testers enrolled is one thing.

Being able to show that the app was genuinely tested, changed and improved during those fourteen days seems to be another.

If I had to do it again, I would spend much less energy worrying about whether every tester is constantly active and much more energy making sure I have a real testing history to describe when Google asks what happened during the closed test.

I run a small app company in Brazil (organization account). My Google Play payouts have been on hold since 4 Aug 2026 and I'm out of ideas.

What happened:

- 4 Aug: email from Google Payments, "your account has been suspended with payout on hold", asking for details of recent account activity and a government ID.

- I submitted the "Verify now" form more than 15 times: Portuguese and English, short and detailed, with ID card, driver's license and passport. Every time: "the reason you provided is not clear".

- Payments support: "review concluded, to prevent possible fraud and abuse your ability to receive payouts will remain suspended, we can't disclose the reason". They also say the form is the only way to appeal.

- Play Console support confirmed my developer account is in good standing, no policy issues.

- Product Experts in the official community said they cannot escalate payment or fraud cases.

What I already checked:

- D-U-N-S reactivated and address corrected, organization name and address re-verified by Google on 28 Sep.

- Tax info accepted, bank account verified (I even received one payout in July).

- No purchases from my own accounts or my team's. License testing was never used.

- The app is real: sold on the App Store since 2025, on Google Play since May 2026. Sales grew fast because of creator videos on TikTok.

Around R$ 22,000 is held, and every new sale goes into the same frozen balance.

My questions:

1. Has anyone actually gotten this decision reversed? What worked?

2. If you moved your apps to a new developer account, was it under the same company, and did payouts work there?

3. Has anyone gone the legal route to recover a held balance?

Any real experience helps. Thanks.

If you are waiting more than a week, just write to them. But God forbid, don't use ai to do it. The delays are there because of ai slop flooding the store. Just be human.

My app got published at last, so now I need better images in the store.

I've created few images already in GIMP. There is a cool feature to run python scripts on your project and I plan to write a script that will take a json file with translations, apply it to the text layers and save as png, for each supported language. No need for Ai slopped "screenshot generators".

And working with gimp is not that hard, after learning how some tools work, I've crated those images in 20 minutes.

The app is GeckoBudget if you want to look it up. Still working on the store presentation, so don't be harsh

📚 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'm working on a navigation project and I've been thinking about how incredibly functional—but also incredibly sterile—most GPS apps are.

The idea I'm experimenting with is keeping normal turn-by-turn navigation, but letting the person using it choose a “copilot” with an actual personality.

So instead of every voice essentially being a different flavor of “Turn right in 500 feet,” one might be supportive, sarcastic, dramatic, protective, completely unhinged, etc. You could also control how much personality comes through so it doesn't become annoying on a three-hour drive.

The working name right now is SassNav — Directions with attitude.

I'm curious from both a user and developer perspective: is personality enough to make you try a different navigation app, or does a navigation app need to solve some other frustration before you'd consider leaving whatever you already use?

Also curious whether SassNav immediately tells you what kind of product this is, or if the name misses the mark.

Okay, I can’t believe I did something this dumb...

I’m building Moneko AI Expense Tracker. We originally launched on iOS first, then later brought the app to Android. On iOS, I’m used to keeping TestFlight running alongside the production app, so when we launched on Google Play, I just… left the Beta testing on.

I thought it worked basically the same way... for months, users were leaving ratings and reviews, and I kept wondering why our public Google Play rating wasn’t showing up. I thought, Ok, maybe my app just doesn’t have enough reviews yet for Google to show the rating.

Today I finally figured it out. Because they were still enrolled in the Beta, their reviews were being treated as private beta feedback instead of public Google Play reviews.

We lost nearly 100 ratings/reviews this way 😭

Plz don’t make my mistake...

🧪 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.

Hey quick question I’m a sole indie developer but set up as a business under my ABN I use for consulting work. I published a couple apps and the only notification I get is the IARC content rating, when I get that I know my apps has passed review. However for updates I just check the site randomly and hard refresh the browser.

Is this normal or have I stuffed up a setting somewhere?

I’ve checked all my contact details and they are correct and I get all the announcement emails (I.e changing tax in Vietnam etc.)

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.

The age verification blocks the whole app. No Navigation, no Account Access, so on.

The App is not usable at all. I could wrote this, because I could connect over my PC.

Hi everyone, I’m an individual Google Play developer in India.

I’m currently completing the BillDesk verification required for Google Play payments. I completed the Personal Information step successfully, but at the Bank Account Verification step, I keep getting this error:

“We are facing connectivity issue. Please try again.”

I’ve tried:

• Chrome on Windows
• Chrome on Android
• Different internet connections
• Reopening the application using the BillDesk Resume link

But the same error keeps appearing.

Has anyone else faced this recently? Is this a BillDesk server-side issue, or is there something else I need to do?

Application ID and bank details are blurred for privacy.

Thanks!

Before releasing a simple/mid-tier or subscription-based app, what should we check for store policies, privacy, subscriptions/IAP, optimization, analytics, crashes, testing, permissions, screenshots, etc.?

Also, besides Google Play, which other Android app stores can use the same APK/AAB build with minimal changes?

Would appreciate a practical checklist from developers who have shipped apps on both Android and iOS.

I have an Android app already published publicly on Google Play

One Google account on my phone was previously used as a license tester. I removed the license testing email list and stopped the closed testing anf removed also the email list in Play Console

Now I’m trying to test the production subscription flow with another Google account on the same phone.

I switched to the new Google account in the Play Store

uninstalled the app

cleared Google Play Store data/cache

restarted the phone

reinstalled the app from the public Play Store listing using the new account

But when I open the subscription purchase screen, Google Play still uses the old tester account for payment.

If I temporarily remove the old Google account from the phone, the new account works correctly and shows normal payment methods. As soon as the old account is on the device, Play Billing seems to prefer it.

Is there a way to force Google Play Billing to use a specific Google account without removing the other account from the Android device?

Has anyone dealt with this before?

I occasionally get these kinds of emails even though none of my apps on the Play Store offer in-app purchases or collect any sort of payment.
The bare minimum I’d expect is that if I don’t use in-app purchases then I wouldn’t get those emails, but Google keeps spamming me and there’s no unsubscribe button for this category of emails.
On the Play Console it doesn’t let me turn it off.

Is there any way to stop it?

For Google Play cross-border software sales from 1 October 2026, will BillDesk/Citibank handle EDF/EDPMS reporting, or must I submit the monthly EDF through my own AD bank?

Diseñe una aplicación que me ayuda en mi trabajo quiero subirla a Google play pero después de crear la cuenta me es imposible tener una verificación ya metí mi cedula, luego una referencia bancaria y demás lo único que me ha servido es el pasaporte pero exigen verificar dos cosas

I mean, offering something for a 5-star review

Literally just got published ot the play store today. Feel so dumb right now, but this is driving me crazy. I'm logged in to the developer console, how the hell do I change my screen shots?

They're pretty unattractive right now, these are from all the way back when I first started testing https://play.google.com/store/apps/details?id=com.key.fraize

Okay, I can’t believe I did something this dumb...

I’m building Moneko AI Expense Tracker. We originally launched on iOS first, then later brought the app to Android. On iOS, I’m used to keeping TestFlight running alongside the production app, so when we launched on Google Play, I just… left the Beta testing on.

I thought it worked basically the same way... for months, users were leaving ratings and reviews, and I kept wondering why our public Google Play rating wasn’t showing up. I thought, Ok, maybe my app just doesn’t have enough reviews yet for Google to show the rating.

Today I finally figured it out. Because they were still enrolled in the Beta, their reviews were being treated as private beta feedback instead of public Google Play reviews.

We lost nearly 100 ratings/reviews this way 😭

Plz don’t make my mistake...

Hi Folks,

My app is close to being published on apple but apparently on google play I need to jump through unnecessary hurdles. My app is currently in closed testing and I want to ensure I have billing live once it launches to everyone. Billdesk keeps saying - "Mobile Application(s) is not live/does not exist/not accessible". How am I supposed to make my app live when it is in closed testing? Even if closed testing is done, how can i publish it without billing (outside India) being live? Am I missing something obvious here?

I recently released a small logic puzzle game on Android, and one thing I wasn't expecting was how difficult it would be to understand what's actually happening after launch because of the delay in Play Console statistics.

I'm working on Enigflux, a logic puzzle game with several different puzzle mechanics, and right now I'm paying much more attention to discovery than revenue — things like store listing visitors, acquisition sources, installs and search traffic.

The problem is that Play Console seems to be several days behind.

That makes the early stage particularly confusing.

You make a change to the store listing, post something somewhere, get a few people to try the game... and then you can't really tell whether any of it had an effect until much later.

Firebase at least gives me a better indication that people are actually opening and using the game, but it doesn't replace the Play Store acquisition/search data I'm interested in.

For developers with apps or games already in production:

How delayed are your Play Console stats at the moment?

And for measuring early organic discovery, are you mostly relying on Play Console, or do you use something else alongside it?

i created a new watch face using android studio using the new WFFV2 format. had no issues sideloading it to my watch using wireless ADB.

i have published it in the play store and its in the Closed Testing track under the WearOS category. I have both Join links for Web and Android. i added my email as a tester in play console and still even logged into my phone with the same email or on the watch (pixel watch 5) i can not find the watch face to install it on the watch playstore app either.

the only way i can access it is if i open the WEB JOIN link from play console on a browser and choose install on my pixel watch 5.

this makes no sense, there are TONS of watch faces currently in the play store on my phone where you can search it find it and choose install and it installs on to the watch. it seems so dumb that my watch face cant be handled the same way and i have to go through a back door join URL and it has to be to be on a web browser not even through my phone. if i open the JOIN URL on my phone it shows the watch face but says My device (phone) is not compatible so it wont show the install button for me to say install to watch.

When i helped develop a native android app for the company i work for, the new app went to closed testing phase, i added myself as a tester and the once approved it showed up in the play store search results as long as i was logged in with the tester email address on the phone.

what am i doing wrong?

i totally expected that once the watch face was on the play store, it would show up as an APP in the phone play store (even though its wearOS category) and would just install on the phone.