i have an app on play store and when i submitted an update i got an email that it has been rejected due to policy violation because of an issue with the ads of the app. I fixed the issue and uploaded a new update yet after 8 days both versions are showing "in review".There is not a mention of the issue on the google play console or a way to cancel that version and keep only the new one from what i see. Any ideas how to solve this issue? Its an app bundle made with flutter.
In review means that google is checking it for something, maybe malware, maybe breaking the google policy etc. Its best if you contact google and ask why.
Related
i'm trying to publish my new app on google play. but i'm confused about app status... in dashboard pages, app status showing DRAFT but why? is that a problem? what i have to do for fix this issue? please let me know about the app status. i thing it need to show Production, but it's showing draft. i already fixed all violation from store listing but it's not fixed. please see the screenshot below.
There is no need to worry if the application adheres to the terms and standards of Google developers
And now the application is under review, just wait and the response will come with acceptance and publication, or a response to problems in your application and what must be modified
No need to worry about status being Draft after you making sure that you completed all the required information. It is all about waiting game. Sometimes it takes weeks if they are short of reviewers. I just published mine right now, it says Draft. I have to give it sometime until it changes to Live.
No need to worry application will be publish when it meet all google policy and verified by google after it shown on play store.
Before covid 2020 it takes maximum 48 hours after covid google take 7 days time to verify it.
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.
I have uploaded an application in google play console. They rejected my application due to Violation of Impersonation policy. Then I changed my logo and uploaded it again. Then they publish it on play store. When I uploaded the application in play console I Upload both new apk and play console logo. When I am installing the application in the phone then I see they updated only play store logo, not my new apk. How do I solve the problem?
Sometimes it takes more than 24 hrs to publish the app and become available for download from the google play store. Don't worry.
However, I would like to recommend you check if you have chosen the Full Rollout option while publishing your application. Sometimes, the app is updated and people forget to click on the Full rollout button.
Was questioning the same thing yesterday. I violated the privacy policy and needed to add a policy into the url needed. And clicked "Resubmitted", at the side you will see "processing request" or something like that? Yes, you have to wait to let Google Play Store review your app to make sure you have fixed what they pointed out the first time.
So don't worry, give it some time.
We started seeing this error from the play store when clicking on purchase -
We could not find a way to reproduce this error but users started seeing them recently. I could not find it on the list of known errors.
There are similar error codes like 'DF-DFERH-01' or 'DF-SA-01' which are solved by clearing the play services cache data or by removing the store account and adding it back. These methods did not solve the issue in the case of 'DF-AA-09' error.
We started seeing this error starting June 8th on the new version of google play store (11.0.55 or 11.0.56).
Anyone know what 'DF-AA-09' error means and how to reproduce and solve it?
You may refer with this General Fix for Google Play Services Error Message.
Empty Cache
Reset the App Preference
Add your Google Account Once Again
Reinstall Google Play Services
Clear the Cache under Google Framework Services
If none of this works, you should consider filing a report.
I asked about it in google play forum and this is the answer I got -
Your app users might encounter such errors when there is an issue with the purchase flow or the payment methods they are using. Forcing the Play Store app to stop and clearing the cache/data of Play Store app should help in such instances.
However, if their payment is declined, can't be processed, or is listed as "not eligible," trying the troubleshooting steps from the following help center article could help them fix payment issues on their accounts.
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.