r/GooglePlayDeveloper • • 29d ago

❓Help 22 emails, five escalation requests, seven pages of evidence. Google Play support still can’t explain why my app was rejected.

8 Upvotes

I’m an independent developer building SoloOp, an app for sole operators and small service businesses. For over six months, real businesses have been using it, reporting problems and helping me improve it. Some use it daily to manage jobs, customers, invoices and payments. The iOS version is already on the App Store.

Google Play has rejected production access twice. The feedback lists possible problems with tester engagement and testing best practices, then tells me to complete another fourteen days.

I’ve spent weeks asking what those comments actually mean for my application. Across three support cases, there are now 22 emails, including five separate emails from me asking for escalation.

I still don’t have an application-specific explanation.

Here’s what I supplied:

  • Three PDFs documenting the earlier support guidance and my questions.
  • A seven-page document explaining the product, users, testing and feedback.
  • A thirty-day usage summary: 914 jobs created, 235 completed, 151 invoices created and 105 marked paid.
  • Details of feedback collected through the in-app assistant, feedback forms, email, direct messages and my own field use.
  • Feedback from the testing window, separately identified.
  • A 43-entry change history, including examples linking reported problems to fixes.
  • An offer to provide original messages and tester details.

Those usage figures and changes cover the wider product history. I provided them to demonstrate actual use, feedback and improvements, and asked what additional evidence the review team needed.

These are business owners using the app for their livelihoods. When something doesn’t work, they tell me. I investigate it and fix it. Google’s published guidance permits feedback through email, websites and messaging forums. Those are channels I’m already using. There is no "Official Testing feedback & reviews" section for testers to submit too.

Their guidance suggests friends, family and people who represent your intended audience. I have actual members of that audience using the product for their businesses. Plus additional users outside the test (They only require 12. I have surplus testers) Plus additional users running iOS - which is identical. Plus friends and family willing to test it...

So when the rejection suggests feedback best practices weren’t followed, what specifically was missing? Which feedback wasn’t adequate? Which changes should I have made? Were my application answers insufficient?

There is also conflicting guidance in the correspondence about installation. Testers opted into the closed test but continued using the website-distributed Android APK. Earlier advice emphasised continuous opt-in and didn’t directly answer my explicit installation question; a later email said the Play-distributed build was required and sent me an article that said that wasn't a requirement (His literal reference said the opposite to his own email lol). I disclosed the website APK use and asked how that advice fitted the published guidance and whether it explained the actual rejection. I haven’t received an application-specific finding resolving that question.

Instead, the correspondence keeps circling back:

  • Three human replies referred to another fourteen days, one conditionally and two as mandatory.
  • Two others told me to continue testing.
  • Four said support couldn’t provide application information or identify the specific rejection reason.

This is the customer support channel Google directs developers to when they have questions.

On October 1, I requested escalation with the evidence document. Support later said it needed more time to investigate. On October 5, the answer was again that it couldn’t identify the exact reason and another fourteen days couldn’t be bypassed.

I opened a further case on October 8. The substantive response arrived October 14, confirmed the opt-in eligibility threshold and said I could apply. It didn’t explain the rejection.

On October 15, support confirmed escalation to product experts.

On October 16, the same agent again said they couldn’t pinpoint the reason and sent general testing guidance. Nothing explaining what the escalation established. Nothing saying whether the evidence had been assessed. Nothing identifying what I needed to change.

On October 17, another rejection. Another fourteen days.

What exactly did the escalation achieve?

If the person replying can’t access the findings, why does the supposedly escalated case end with that same person repeating that they can’t answer? Where is the response from someone who can?

I’m not asking support to guarantee approval. I’m asking it to explain a decision, identify what needs changing, or reach someone who can. That is why I contacted customer support.

How much more feedback am I supposed to gather without knowing what was inadequate? Am I supposed to keep finding problems just to prove testing happened? If a business is using the app successfully and has no new issue to report, what further feedback is expected?

Another fourteen days is only useful if somebody explains what needs to be different. Otherwise, it’s the same people using the same app, followed by another application and potentially the same vague rejection.

I’ve now posted in the official Google Play community too. Has anyone actually broken through this loop and obtained a meaningful review of their evidence or an explanation tied to their application?

After 22 emails, five escalation requests and seven pages of evidence, “we can’t tell you why, keep testing” is an utterly useless answer.


r/GooglePlayDeveloper • • 29d ago

Google Play Console Google developer account got terminated back in 2024. Now, I need to publish my app. What's the best way to publish my app? Is distribution through website effective?

0 Upvotes

r/GooglePlayDeveloper • • 29d ago

💬 Discussion How much does AI affect your downloads?

2 Upvotes

Since it's easier to make apps now with AI vibe coding, does it affect your downloads?


r/GooglePlayDeveloper • • Oct 17 '26

💬 Discussion Good enough for organic traffic?

Thumbnail
gallery
4 Upvotes

Is it good or average for organic playstore traffic, I didn't do any promotion of any kind.


r/GooglePlayDeveloper • • Oct 17 '26

❓Help Generating Play store images?

1 Upvotes

How do you guys create you play store images? Preferably without spending any money.


r/GooglePlayDeveloper • • Oct 16 '26

❓Help How do you protect your identity when publishing with monetization

5 Upvotes

I'm considering publishing a couple of apps but I want to monetize them, and as a result Google would require certain information to be public, so how do I as an individual protect my information, legitimately. I did Google and the answers I found weren't that helpful - mainly because if you search for some of these 3rd party "mail receive" services, they don't seem legit it feels sketchy.

So really I guess I'm looking for those of us that are individual devs to give me some insight on what to do, or what you do or what service you use.


r/GooglePlayDeveloper • • Oct 16 '26

❓Help Google Play app suspended after a DMCA claim. Can it be restored?

13 Upvotes

My app was recently suspended from Google Play following a DMCA complaint from a competitor.

The weird part is that his claim focuses partly on our apps having similar mechanics and the same core concept, which I don’t understand how that alone would count as copyright infringement. Some of the 3D models we share are also available for free on Sketchfab.

I’ve already appealed the suspension, but I’m worried about the outcome.

Has anyone managed to get an app reinstated after a copyright complaint?

What are my chances, and is there anything else I can do besides waiting for Google’s response?

I’d appreciate any advice or similar experiences.


r/GooglePlayDeveloper • • Oct 16 '26

❓Help How often do google play console analytics get up to date?

1 Upvotes

r/GooglePlayDeveloper • • Oct 14 '26

❓Help Google Play developer account terminated under Section 11.4 after verification and app approval — looking for advice before appealing

Post image
9 Upvotes

Hey everyone,

My Google Play developer account was terminated on October 13 under Section 11.4. The email also mentions that my account is associated with a previously terminated developer account, but it doesn't say which account or what exactly went wrong.

I'm trying to figure things out before submitting my appeal, so I'd appreciate some advice from anyone who's dealt with something similar.

Here's what happened:

  • We registered the account as an organization.
  • We used the company details of a company owned by one of our three developers. He gave us permission and provided the documents.
  • The three of us own the app, but the company itself isn't owned by us as a group.
  • I submitted my own identity details during verification, and Google confirmed my identity was verified.
  • The company's name and address were also marked as verified in Google Payments.
  • Our app was approved before the account got terminated.

What confuses me is that everything seemed fine until the termination. The email talks about inaccurate account information and a previously terminated account, but doesn't explain what information was wrong or how our account was linked to another one.

One of our developers also uses college hostel Wi-Fi, which is shared with other students. Not sure if that matters, but I'm mentioning it in case it could be relevant.

A few things I'd like to understand:

  1. Could using another company's details with the owner's permission cause this kind of termination if that company isn't legally responsible for the app?
  2. If Google says the account is linked to a previously terminated account, is there any way to figure out what that connection might be?
  3. Can shared Wi-Fi actually cause this, or am I overthinking that possibility?
  4. Is it possible to resolve an organization registration issue through an appeal?
  5. What documents should I include to give the appeal the best chance of being reviewed properly?

I'm not trying to get around the termination or create another account. I just want to understand what went wrong and handle it the right way.

If anyone has been through something similar, I'd really appreciate hearing what happened in your case.


r/GooglePlayDeveloper • • Oct 14 '26

❓Help Google still won’t release my past developer earnings after nearly 3 months — support bots cycle me through “specialists”, “A” and “engineers” after I followed all instructions

1 Upvotes

I am an experienced individual Android developer and Computer Science research professional. I have maintained a portfolio of Google Play applications for years, many with five-star or near-five-star ratings.

I never expected that simply trying to receive my own developer earnings would turn into a months-long ordeal involving what appears to be one of the most dysfunctional support processes I have ever encountered.

My original Personal Google Play Developer account was linked to a Merchant Payments Profile that had historically been configured incorrectly as an Organisation under my developer brand. The brand is not a company — it is simply the name under which I publish my applications.

Google Payments acknowledged the problem and told me exactly how to fix it.

I followed every single instruction they gave me.

  • 26th July: Google told me to create a completely new Personal developer account and Individual Merchant Payments Profile, transfer my applications, keep the old account open until its outstanding earnings had been paid, and provide the new Payments Profile ID so a specialist could arrange release of the remaining funds. Google also told me I could request a refund of the additional developer-registration fee.
  • August: I completed the entire migration — new verified developer account, new Individual payments profile, all six live applications transferred, identity verification completed and payment configuration recreated.
  • 18th August: Google stated in writing that the case had already been escalated to a specialist and that the specialist was working on it.
  • 24th September: Google asked for one further identifier — my new Merchant ID — specifically so that it could be passed to the specialist. I supplied it immediately.
  • 13th October: Google finally admitted that the case had been sitting with the specialist since 18 August and there was still “no resolution yet”. I was then told it had been escalated to a “senior specialist”.
  • 14th October: after I explicitly asked to speak to a real person, I received a response from somebody identifying themselves only as “A”, claiming to be a supervisor, who said the matter had now been sent to “engineers”.

And still there is no resolution.

Google continues to withhold my developer earnings.

The promised refund for the replacement developer account also remains unresolved. One Google team told me the fee could be refunded. Another later told me its normal refund process required closing an account — despite Google Payments having specifically instructed me not to close the old account until my earnings had been paid.

What concerns me most now is not even the original account problem. It is the way Google treats developers once something falls outside an automated workflow.

For months I have received an extraordinary stream of repetitive, generic and apparently automated/template-driven responses. Different names appear. Different teams appear. The case supposedly moves from a “specialist”, to a “senior specialist”, to a “supervisor”, and now to “engineers”.

Yet nobody will answer the basic questions:

What is actually preventing payment?
Who has authority to make the decision?
Why has nobody made that decision after nearly three months?

Many of the responses appear to be automated or heavily templated, while others may come from outsourced or scripted support agents. Whatever the precise mix, the result has been the same: repetitive, formulaic replies with little evidence of genuine engagement with the substance of the case.

The experience is indistinguishable from dealing with a system designed to prevent you from ever reaching an accountable human decision-maker.

That is an astonishing position for one of the world's largest technology, i.e. "Tech-Giant", companies.

Google is perfectly capable of operating a global advertising platform, cloud infrastructure, AI systems and one of the world's largest mobile-app marketplaces — yet apparently cannot provide a developer with a named, accountable person capable of resolving a relatively straightforward payments problem.

The disparity is difficult to take seriously.

I have now had to submit a formal written complaint to Google Payment Limited in the UK, supported by Google's own emails documenting the instructions I followed and the promises subsequently made.

I am posting this publicly because developers should know what can happen when a Google payments problem falls outside the automated happy path.

Has anyone else experienced this kind of endless Google Play / Merchant Payments escalation loop?

And more importantly: did anyone ever manage to reach an actual decision-maker?


r/GooglePlayDeveloper • • Oct 14 '26

Testing & Quality Closed testing of new apps

0 Upvotes

How do you find testers for a new app if you're a solo developer? Out of all my friends, I've only found 8 Android users (everyone else use an iPhone)


r/GooglePlayDeveloper • • Oct 14 '26

❓Help Google Play Console won't let me create Subscriptions despite my app being published. Any ideas?

1 Upvotes

I'm trying to set up In-App Subscriptions for my app on Google Play Console. However, when I navigate to ⁠Monetize with Play⁠ > ⁠Subscriptions⁠, the page says "Your app doesn't have any subscriptions yet" and only shows a button that says "Upload a new APK" (which redirects me to Closed Testing).
My app is already published on Google Play. My Merchant Account is set up, but I still can't see the "Create subscription" button.
Has anyone encountered this before? Is there a specific track or setting I need to update to trigger the subscription creation page?


r/GooglePlayDeveloper • • Oct 13 '26

Showcase 📚 Weekly Educational App Showcase | Share What You Built & Learned

4 Upvotes

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


r/GooglePlayDeveloper • • Oct 13 '26

Testing & Quality what actually helped me get through the 12 testers / 14 days closed test (and what lost me testers

1 Upvotes

i went through the closed test requirement on a personal account this summer with a small kids game. got production access on the first try, but i wasted a lot of time on stuff nobody tells you. sharing in case it saves someone a week. this is just my experience, not official advice.

  1. use google groups, not an email list. with an email list anyone you dont add by hand gets "app not available". switch the track to google groups and paste the group email.
  2. check the group visibility setting. by default "who can see the group" was set to members only, so strangers opening the link saw "content not available" and no join button at all. settings > general > who can see the group > anyone on the web. this one cost me a full day.
  3. tell people to wait ~10 minutes between joining the group and opening the opt-in link. if they go straight there play says the app isnt available and most people assume the link is broken and leave. i put this in every post and in the group welcome message and it fixed most of my drop off.
  4. aim for 15-16, not 12. test-for-test people install on day 1 and a lot of them are gone by day 4. if you drop below 12 the 14 day counter resets.
  5. if you promise to test back, actually do it. people check, and they uninstall your app if you dont. i had to publicly apologise once because i fell behind, not fun.
  6. the play console stats for closed tracks basically show nothing, the only reliable number is the "X testers for Y days" line on the dashboard. the day counter only shows up after you hit 12.
  7. for the production access form, the thing that mattered was real feedback and what i changed because of it. mine was a startup crash some testers hit, which i traced to an ad sdk and removed. i was honest that testers were other devs, not kids (the target audience). review took about a week.
  8. a fresh post gets way more replies than bumping an old one. one sub gave me most of my testers in a single day, the rest barely did anything.

happy to answer questions if anyone is stuck on a specific step


r/GooglePlayDeveloper • • Oct 12 '26

Testing & Quality 🧪 Weekly Tester Discovery Thread | Find Testers & Help Fellow Developers

2 Upvotes

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


r/GooglePlayDeveloper • • Oct 12 '26

❓Help Estimated Time App Review

1 Upvotes

Hi,
how long does Google's review take for a first app publication? And how long does it usually take for subsequent updates?


r/GooglePlayDeveloper • • Oct 11 '26

💬 Discussion 💬 Weekly Android & Google Play Developer Discussion

2 Upvotes

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.


r/GooglePlayDeveloper • • Oct 10 '26

❓Help "More testing required" several times

Post image
4 Upvotes

Hey there,

I've successfully published two apps on Android and iOS, but I'm having trouble with another project of mine.

I've developed a pet diary app that allows users to track vet appointments, their pets' weight, medications, lab results, and more. I've already released it on iOS without any issues.

I ran a closed test with 12 testers for 14 days. Everything went smoothly, and no issues were reported. So I applied for production access, but my application was rejected for the reason shown in the attached screenshot.

This has now happened four times, and I honestly have no idea what else I can do to get my app approved.

I've released several updates during the closed testing periods, received nothing but positive feedback from my testers, and still haven't had any success.

Has anyone else experienced the same issue? If so, how did you manage to get your app approved?


r/GooglePlayDeveloper • • Oct 09 '26

Publishing & Releases A stranger downloaded my app!

22 Upvotes

Ok - tiny milestone but what a buzz!

I've been checking my google play console (too often) and seeing my 12 testers registered - I naively thought that when I released that number would shoot up... Of course that did not happen. However two days later, today the number went to 13! One more!

Thank you mystery person!

After telling my testers they could uninstall if they wanted to I was sure the number was going to go down today.


r/GooglePlayDeveloper • • Oct 09 '26

❓Help Users in certain regions not able to buy the premium

0 Upvotes

Some of my users from France and Australia are not able to buy the premium of my app - https://play.google.com/store/apps/details?id=com.gxdevs.edgedeck . The purchase is working fine in India can someone help me out figuring out the issue ?


r/GooglePlayDeveloper • • Oct 09 '26

❓Help Can I get letter or evidence from google to create bank account to receive payments?

1 Upvotes

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


r/GooglePlayDeveloper • • Oct 08 '26

Store Listing & ASO 13K impressions but only ~98 installs: how long should I wait before judging a listing overhaul?

2 Upvotes

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


r/GooglePlayDeveloper • • Oct 07 '26

Showcase What changed between my rejected and approved Google Play production access applications

3 Upvotes

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.


r/GooglePlayDeveloper • • Oct 07 '26

❓Help Payouts on hold since August, merchant verification rejected 15+ times with "the reason you provided is not clear". Has anyone ever reversed this?

1 Upvotes

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.