Currently our update getting rejected because of Intent Redirection Vulnerability. Support Link
Google Support is not giving us any method/class or package name to address our issue.
So we did try their answer with very little information, but update kept getting rejected.
Google states (one of their email);
"This rejection doesn't Impact the standing of your Google Play Developer Account, but repeated violations can result in the suspension of this app or your Google Play Developer account."
First Question; I am wondering, getting rejects counts as violation? If it is, i would like know is there a way to send my app to the review process without any negative consequence.
Second Question; I looked up about rejections and suspensions in Interntal Test Track(or related to internal test track) but couldn't find a solid information.
Should we keep trying to solve the issue without expecting to get suspended by Google.
About this;
I couldn't find an answer to my questions but we found out how Google Play Tracks works. Maybe this would help to a hopeless android developer who suffers from google play console polices
Currently;
If you have issued or non-compliant apk/aab in one of your Track(Internal/Alpha/Beta or Production), your new versions will be rejected until you fix the issued track.
For example; Lets assume your current Production version, lets say versionCode=1, violates one of the Google Play policy, and lets assume you have a fix in your versionCode=2. If you try send versionCode=2 update to Internal/Alpha or Beta, that update will most likely get rejected(or it appears like that on Console). Actually it is not rejected, it is just bad UX. Google Play Support states the issued apk versionCodes in their Notification Mail. Why this is happening? Because Google Play checks all the tracks, not the track you just sent your update. It seems like all tracks depended to each other so if you got rejected or have violating version on any track, that will most likely block your other tracks.
This becomes an issue if you are using other distribution tracks, In our case we don't want to send our new versions directly to release track.
Related
Background
Our app had a write up in SALT magazine today (https://www.saltmagazine.com.au/feature/listen-up) which is an exciting moment.
The iOS version is being featured in the App Store later this year.
However, the Android version has been unavailable for the past 2 weeks despite every attempt I have made to get it back in the Google Play Store.
The app had been in the store for 8 years, but it was recently removed.
It was initially rejected saying the background permission was not required, but we have actioned that in numerous ways - including explaining why it is needed, and eventually actually removing it, reducing the functionality of the app in an attempt to get it back in the store.
We are continuously being rejected in the Google Play Store, without any coherent explanation as to why being provided.
What is said is that the app doesn't need location permission, or that we need a particular message - the app clearly needs location access, and the message has been provided - making these changes doesn't seem to have any effect on the rejection at the Google Play Store end.
I've sent this message in the most recent appeal :
You have failed to provide any coherent feedback at all about why the
request for location permission is being denied -- the
pre-permission-request has been put there, in exactly the wording you
requested. We have removed the location request to order the stories.
We have removed the background location permission. Each of these
diminishes the functionality of the app. But now I can't conceive of
how this app can be rejected. Each time you send a rejection it is
randomly different. I feel we must be being targeted by some
disgruntled employee at Google Play.
This is a good solid app, that has been enjoyed by many for many
years. I'll send this out to the other Google departments. We do need
to get this app out there again.
Google Play is not providing any clear information, nothing that is actionable.
There is no reason the app should not be in the store -- as I said, we have even complied with things that don't make sense and reduce the functionality of the Android version of the app, in an attempt to comply with what seems to be being requested.
I don't see a pathway to reinstatement of our app via the channels made available via Google Play, those being :
The permissions declaration form (https://play.google.com/console/u/0/developers/[our dev id]/app/[our app id]/app-content/permission-declarations)
The permissions appeal form (https://support.google.com/googleplay/android-developer/contact/permissions)
This email address (googleplay-developer-support#google.com)
The google contact form (https://support.google.com/accounts)
Context
I know this question might look like it doesn't quite belong here.
But this is a situation that many app developers are going to face, and there needs to be a solution.
For iOS apps it is so easy - When Apple iTunes has a rejection of an app, they send screenshots of exactly where the problem is and identify exactly what policy has resulted in the rejection.
It's also really really easy to talk with people at Apple - either directly via iTunes Connect interface, or else via multiple support options where you can actually talk to a person.
Android app developers need a pathway to communicate with Google in the case of an app rejection. Please, if you have found any that work, share them here for the benefit of all app developers.
Question(s)
Has anyone found a way to talk directly with someone at Google Play Console?
What other path is there when Google Play is rejecting an app without any clear, coherent, or actionable information included?
Just my 2 cents from rejections in the last years:
There is no talking to humans on Google Play Store. It's automated answers all the time.
Appealing never works. Like you, I've always just received the same automated answer again and again.
Rejections seem random. You can try uploading slightly different variants of the same app, and sometimes it comes through
Try removing all functionality that is somehow linked to the rejection (like location permission), even if it makes the app useless. Submit it, then create an update re-introducing all those features. Sometimes that works. Might want to warn your users in advance though.
The Google Play Store bots also sporadically suspend apps - which will quickly result in a termination of the developer account. Try to keep your apps in separate accounts to not get your complete portfolio killed once an app is suspended.
Good luck!
2 years ago, I have received 2 email from google in the same day ( check below ). How many violations/strikes does my account need now to get suspended indefinitely ?
This is a notification that your application submission, xxx,
for package ID com.xxx.xxx.xxx, has been rejected. If
this submission was an update to an existing app, the version
published prior to this update is still available on Google Play.
Please address the issue described below, then submit an update with
your changes.
REASON FOR REJECTION:Violation of the Google Play content rating
policy.
These guidelines apply to all content in your app, including user
generated content, in-app products, and advertisements.
After a regular review, we’ve determined that your app has an
inaccurate content rating. Please retake the content rating
questionnaire for your app and resubmit your app for publishing.
All submission rejections are tracked. Repeated rejections due to
policy violations will result in app suspension, at which point this
app will count as a strike against the good standing of your developer
account and no longer be available on Google Play.
If you feel we have made this determination in error, you can submit
an appeal on the Google Play Help Center.
The Google Play Team
We’re always looking for ways to improve. Please share your feedback
on Play policy notification emails by completing this brief survey.
This is a notification that your application, xxx,
with package ID com.xxx.xxx.xxx, has been
suspended from the Google Play Store.
REASON FOR SUSPENSION:Violation of the impersonation or deceptive
behavior provisions of the Content Policy. Please refer to the
impersonation policy help article for more information.
If you are authorized to publish on behalf of the original content or
brand owner, please contact us via the Google Play Help Center and
attach verifiable and accepted proof of permission.
This particular app has been disabled as a policy strike. If your
developer account is still in good standing, you may revise and upload
a policy compliant version of this application as a new package name.
This notification also serves as notice for other apps in your
catalog. You can avoid further app suspensions by immediately ensuring
that no other apps in your catalog are in violation of (but not
limited to) the above policy. Please also ensure your apps’ compliance
with the Developer Distribution Agreement and Content Policy.
All violations are tracked. Additional suspensions of any nature may
result in the termination of your developer account, and investigation
and possible termination of related Google accounts. If your account
is terminated, payments will cease and Google may recover the proceeds
of any past sales and/or the cost of any associated fees (such as
chargebacks and transaction fees) from you.
If you feel we have made this determination in error, you can visit
this Google Play Help Center article.
Only a suspension counts as a strike on your account. Right now you have one suspension. If you get two more suspension your account will be terminated.
Variant of this question have been asked before. But from the current Google documentation it seems things have changed and many answers are obsolete.
I'm completing an App that will be sold on the Google Play Store. The last thing to implement and test is license verification using LVL. The licensing server will only respond with ERROR_NOT_MARKET_MANAGED.
https://developer.android.com/google/play/licensing/setting-up.html says "Using the Google Play Developer Console, you can debug and test an application's licensing implementation, prior to publishing the application". Then Table 1 on this webpage clearly states a publisher account "Can check license before upload".
I interpret this to mean that, when logged in to my test device using my publisher account I should be able to get a licensing server response for my App without uploading an APK.
Am I mistaken? I ask because other related stackoverflow questions state an APK must be uploaded. That was the case in the past but doesn't appear to be true now if I am interpreting the documentation correctly.
My app is removed from Google Play store and got the reason as:
After review, "My App", has
been suspended and removed from Google Play as a policy strike because
it violates the impersonation policy.
Is there any other way to check whether the app is obeying all Google's policies (like impersonation) before release. So that the app can be saved from suspension. And more than 3 suspension may cause account termination. So please tell me how can I check the app before release?
I think no one had faced such problem??
For me, I totally agree with the author of this post. Really Nice suggestions.
This is not a proper solution for my question. But this is what we can do to sort out this issue from my experience.
I just published another app in the Google Play Store and got rejected. But I didn't published it, it was put for alpha test. This time I got the message that my app is rejected because it violates the impersonation policy, not suspended. And this time there is an option to correct the APK and resubmit the app. Last time when the app was rejected the app got suspended and I need to change the apps package name. This time the fault was in my side and the part of joy was that in the mail from play store it mentioned that one of the image that I call from JSON to show in the app used image of superman.This was the mail:
Read through the Unauthorized Use of Copyrighted Content article for more details and examples. Your app contain images of Superman in its activity.
I am very much glad that play store mentioned the real cause of violation this time. Not a simple recorded message.
When we are publishing the app for alpha testing then we get a chance to correct the error and resubmit the apk again. So everyone please try to upload your apk in alpha testing if the app is accepted there then you can transfer it to beta or directly to publish.
Please respond to this answer if anyone have any better or worst experience.
Thanks
i had the same problem a few days ago. My app was suspended due to violation of impersonation policy. I got the fixed e-mail and I wondered what things got wrong. I got a try, and sent an official signed letter which mentioned that I had the authority and right to use the company's logo - name and assets for which I made the app. Here you can find the form: https://support.google.com/googleplay/android-developer/troubleshooter/2993242?visit_id=1-636145321498752102-1429228295&rd=1 My appeal was accepted and my app was reinsteted. From now on, I'll upload first to alpha testing, although I cannot configure yet, if the rejected uploads at alpha testing are calculated against my developer acount cretibility, or because it's alpha testing it has no effect on me. Anyway, the problem remains the same: Many of us don't know the reason what part of our app violated the policy.
I gather from other postings that it is near impossible to my check licensing code until i publish a new app for the first time in the google play store?
I have uploaded my apk to the Play dev console, (promoted to prod, but unpublished), tested with account owner ID, and still come up with "ERROR_NOT_MARKET_MANAGED" as the license response.
If true what is a good strategy for not making it available to anyone else who might purchase and then complain that it fails licensing checks before i test licensing and fix any related coding problems? Can I make it available in "no countries" at first? Should I put a ridiculously high price in a single country (and does that have to include my own country)?
I would hope there are better solutions to this dilema.
Assuming you are using Google Play Licensing, they write:
Note: Previously you could test an app by uploading an unpublished "draft" version. This functionality is no longer supported; instead, you must publish it to the alpha or beta distribution channel. For more information, see Draft Apps are No Longer Supported.