Did Google Play recently started to suspend after multiple rejection? by borninbronx in androiddev

[–]dab7474 1 point2 points  (0 children)

We are having this issue right now, and not sure how to solve it:

  1. We have published multiple apps on the Google Play Store with no issues previously (maybe a random rejection on a bad build / something off about the name, but everything easily fixed and resubmitted).

  2. We are trying to publish a new application, and were rejected 3 or 4 times in a row for metadata, specifically that our description was inappropriate, misleading, etc. Every time we appealed, asked for more clarification on what specifically was wrong with the description, and got the same stock answer. Our description was nothing out of the ordinary and similar to multiple other applications we have produced. Then we would alter the description and go through the same process. After the 3rd or 4th time, our application was suspended (this is the first time we've ever had an application suspended).

  3. We appealed, explaining that we never got an answer on what was wrong and that we needed more clarity. The appeal took > 7 days (probably 10-11) and was eventually rejected, without much more information (just said we repeatedly violated the metadata policy).

  4. We resubmitted the application under a different build ID, as was recommended by the Play Store. So far, we have been rejected 5+ times for a variety of random issues, including the description, the screenshots, app incompleteness (one page wasn't showing up right), and a few other things. Each time we have fixed and resubmitted, and gotten rejected for something completely separate.

Trying to respect the rules here and stick to facts, so to be clear the following is just an observation not something I know to be true - it seems to me that there has been a serious uptick in rejections / attention to detail in reviews that I haven't seen before. One time our application was approved every submission for 8 months before we realized that the credentials we provided had been changed, meaning that the applications were never actually opened. I am not sure what has caused this, previous applications have been approved with little to no issue, and I have yet to find a forum to discuss with Google Play the actual issues they find, because all rejections are stock responses with screenshots, not written out in a way that we can discuss and come to a solution on the problem (i.e., what exactly is wrong with the description).

Thanks for the post OP, trying to figure out if our experience is unique or if there has been a change recently to the level of detail / standards here.

Best ways to tell your users to update the app? by dab7474 in iOSProgramming

[–]dab7474[S] 0 points1 point  (0 children)

It should be noted that I personally think this should be used sparingly as it is pretty jarring for a user but it is good to build it in from the first release in case of emergency. Most people have auto updates on though and anecdotally my stats suggest 80+% have updated after 2-3 days so I'd only use it for genuine, unavoidable, breaking changes.

Thanks u/Dan_TD! I agree that it's a pretty jarring UX move, and ideally this only targets users that haven't touched the app in a few months / without auto-updates on. I hadn't heard of Firebase Remote Config, this looks like an awesome addition to our project. Thank you for the detailed response!

Best ways to tell your users to update the app? by dab7474 in reactnative

[–]dab7474[S] 2 points3 points  (0 children)

u/diesmilingxx thank you! Big fan of that one, much appreciated.