---
title: "Comment by Ross on \"Nothing has ever angered me more than The Google Play Team\" | Hashnode"
description: "I just finished my own exhausting battle with the Android Play Store review process. This morning my app update was finally accepted after much guessing on my p"
url: "https://hashnode.com/posts/nothing-has-ever-angered-me-more-than-the-google-play-team/63755c5d596f6a73ee539534/comment/63764df7dc823473f485b2ad"
---

[Discussion](https://hashnode.com/posts/nothing-has-ever-angered-me-more-than-the-google-play-team/63755c5d596f6a73ee539534)

Comment [Nothing has ever angered me more than The Google Play Team](https://hashnode.com/posts/nothing-has-ever-angered-me-more-than-the-google-play-team/63755c5d596f6a73ee539534)

[Ross](https://hashnode.com/@rossrs)

[Nov 17, 2022](https://hashnode.com/posts/nothing-has-ever-angered-me-more-than-the-google-play-team/63755c5d596f6a73ee539534/comment/63764df7dc823473f485b2ad)

I just finished my own exhausting battle with the Android Play Store review process. This morning my app update was finally accepted after much guessing on my part.

Like you, I believed that the stated reason for my rejection was erroneous. The email was warning me that I was making a permission request that I was certainly _not_ making. My emails and appeals were ignored.

**IMPORTANT: The eventual solution might be relevant to your situation.**

It turns out that builds in every release track are scanned at the time of review. This includes Open Testing, Closed Testing, etc.

I had an old APK in the "Closed Testing" track that did indeed make the permission request mentioned in the rejection email. Once I updated the APK in that track and resubmitted - my app was accepted.

Crazy that I had to guess that for myself, after two weeks of begging Android for answers.

I hope this helps. At the very least, please know that I feel your pain. If you want to form a pitchfork mob and storm Google HQ I will join in.

[Vishnu Haridas](https://hashnode.com/@vishnuharidas)

[Nov 17, 2022](https://hashnode.com/posts/nothing-has-ever-angered-me-more-than-the-google-play-team/63755c5d596f6a73ee539534/comment/63764df7dc823473f485b2ad#reply-63767c02f0820773cfb15d18)

I created a new account to comment here; and found that [Ross](https://hashnode.com/@rossrs) explained the exact same experience that I wanted to add.

Recently I faced a situation where an app update was rejected for an issue that didn't even exist in that build. Tried pushing another build, tried appealing, no use, the response was the same.

Later I realized that there was an old APK file in the "Open Beta" channel which was uploaded 2 years ago, which had the mentioned problem. The beta channel was still open, but nobody knew that. I deleted the Open Beta and then resubmitted, it got accepted.

The problem is, they never mentioned anything about which specific APK in which track has this problem. Just like Ross said, they must be combing all the latest APKs published in all active channels.

[Daniel Read](https://hashnode.com/@danFitdegree)

[Nov 17, 2022](https://hashnode.com/posts/nothing-has-ever-angered-me-more-than-the-google-play-team/63755c5d596f6a73ee539534/comment/63764df7dc823473f485b2ad#reply-6376bdbbf0820773cfb1606a)

Wow, I don't think this is the issue I am currently experiencing, but this is VERY valuable information to have in my back pocket. Thank you for sharing your experience! Hopefully if enough developers talk about this process more, we can all figure out how to navigate this easily without it being so much of our time. Same to you [Vishnu Haridas](https://hashnode.com/@vishnuharidas)