My previous app apk had a permission of SMS_RECEVIE which is now unpublished from production.
It was done by some other developer so I don't have any details about it.
Now I have uploaded a new apk on beta which do not have any SMS_RECEVIE permission which got rejected.
please suggest me what to do now.
Remove SMS permission from manifest if your app requires just reading OTP.
Use SMS retriever API
https://developers.google.com/identity/sms-retriever/overview
Google has sent a mail to you regarding this. you might need to submit that form once again.
wait for 24 hrs.
Or
Upload a new version of your APK and submit a permissions declaration form to enable further review.
Well, since you have already removed the SMS_RECIEVE from the app, there should be no more problem with publishing the app.
Just go to play console and publish your new app as a production release. It'll take some time to be published. Anyway if there is not any other violations or issues the app will be published. You can remove your beta release as well.
Related
How can I update my Android app on Google Play Console after it has been removed by Google for violating permission policies? Is there any way? I mistakenly ignored the emails sent by them for updating the app before the 9th of March.
Here are screenshots of my google play console
You can see the reason or policy violation in play console. I think it's under alert options in Play console. please check it, correct it in the app. then update your version code and version name, the sign your app, publish it again. Go to your app in play console, then select App releases under Release management then click manage in production -> create release or publish it as beta, after get approved from play console, publish it as production.
Hope this helps.
Recently, Few of my apps which were using SEND_SMS permissions have been removed from playstore. Now you can do two things:
If your app relies on SEND_SMS permission for it's working, then you need to submit a permission declaration form with relevant information. Find it here
Remove these permissions if are not very much needed, then simply upload your app to playstore.
You'll be guided for the same when you'll push a new update on Google play console.
We have removed the sms and call_log permissions. Here are the permissions we have on our app now
But still, we are getting the below interface on google play console
As 9th March is the deadline for this issue, we wanted to get this fixed immediately. Any help is appreciated
I had a Live chat with Google Play Support and resolved it.
The solution is as follows:
Create a new build (apk) and push it on to all visible sections to deactivate all the existing or old builds. I have pushed a new apk to below sections
Internal Testing
Alpha
Beta
Prod
Note: If you are not using sms or call log permissions, please select
"No, this release does not meet the SMS and Call Log permissions policy".
Otherwise select
"Yes, this release meets the SMS and Call Log permissions policy" and provide with all specific details.
If you are not using these permissions, you should not be seeing this warning after uploading new build.
This is an issue on the google play console.
If you sure that your final apk doesn't have any sensitive permission.
You must deactivate all previous apk that have sensitive permission on every track (internal, alpha, beta, production)
You can view all existing activate apk on the Artifact library on the left side menu
to deactivate previous apk, you must upload new apk and complete the permission form by ticking “No, this release does not meet the SMS and Call Log permissions policy” on the form.
** I known it doesn't make sense that we need to tick "No, this release ....". But this is the instruction from google support and I also use the same method to solve it recently.
When I uploaded a new .apk to the Google Play store, its uploaded but even after some time, it rejected my submission saying, "Your recent app submission was rejected for violating the Permissions policy. Before submitting your app for another review, read through the policy and make sure your app is in compliance".
After that, I have updated Apk file with the new version and attached with a video link and its shows your app is not meet with call and SMS permission. Please Help me out this issue how to live my app again. Mainly I have already filled up the google permission form.
enter image description here
We have encountered this problem, when uploaded a new .apk to the Google Play store. Our new apk is meet new Google Permissions Policy about SMS and CALL. We remove these permissions from app completely and provide a video link, but our app update was rejected according to these permissions.
Google support team sent an email to solve this issue as follow;
To solve this issue, you will have to discard the draft artifacts containing sensitive permissions and create a new release without those permissions.
Here is how to check within the Play Console:
Go to Release Management > Artifact Library
Expand Active APKs and Draft APKs
Expand Required Permissions for each APK
You may also want to review the Permissions policy and review the Use of SMS or Call Log permission groups help article, which describes intended uses, exceptions, invalid uses, and alternative implementation options for additional guidance.
In google play dashboard, this alert box is showing: Alert - this app will be impacted by a policy change. So I removed RECEIVED_SMS from manifest and use Google SMS retriever API to auto-detect SMS and upload app in play store 5 hrs ago and the app is published in play store. But the alert box is still showing. So do I need to do anything more except removing high risk or sensitive permissions?
Had the same issue
I also removed the sms receive permission from manifest, and published new version to production, but the alert was still there.
I removed all the active releases from alpha/beta/internal channels, as well as from the artifact library, waited 24 hours, and the alert was finally gone.
We had the same issue and I contacted google support. This was the answer:
you are trying to submit a new release that does not contain any
sensitive permissions, however the Play Console is still prompting you
to submit a Permissions Declaration Form. This is because one of your
active releases (across all tracks you are using) does declare one of
the sensitive permissions. To release a new compliant APK, please
follow these steps:
Go to your Play Console. Select an app. On the
left menu, select Release management > App releases. Next to the
release type you want to create, select Manage. To create a new
release, select Create release. Upload a new compliant APK. Fill out
the Permissions Declaration Form: For “Compliance status,” select “No,
this release does not meet the SMS and Call Log permissions policy”
Select Save > Review at the bottom of the page. Click Start Rollout.
Even if you choose “No, this release does not meet the SMS and Call
Log permissions policy” and get the notification email from us, your
app will not be removed after March 9th if your active APK(s) still
does NOT have sensitive or high-risk permissions until then. Also, the
Permissions policy warning message in your Play Console Dashboard will
disappear within one day if you don't have any active APK(s) with
sensitive or high-risk permissions.
We faced the same issue we did the following to get it resolved.
It was caused because of one build in Internal test section, that was not being suppressed by higher levels.
We removed all the sensitive permissions and uploaded the build on 'Internal Test Track'.
We moved that to Alpha then Beta and Production and then it didn't ask us to declare anything.
If you indeed have published an apk without these permissions (see below), I believe it's a bug in the Google Play console and you shouldn't worry.
I'm still having this warning after removing those permissions a week ago.
Thought the problem was having old apks in alpha & beta tracks, so I updated them also to the newer version, and it still warns me.
I even uploaded the same apk under a different package name just to make sure I follow the new rules - and voilà, the warning doesn't show for that app. This is why I think it's a bug and hopefully they'll use a better technique when needed to remove the non-compliant apps.
Steps to make sure your app's compliant:
Google didn't specify anywhere if these rules also apply on alpha/beta, or whether the use of these permissions on alpha/beta would affect the production, so just to make sure update these apks too.
Make sure you don't have a dependency for a library that requests/declares these permissions. You could verify it using 'analyze APK' in android studio, or inside the google play console, in the release info (where they specify all the declared permissions).
Make sure you have rolled out the updated apks to 100% of your users, in case you don't perform a full roll-out everytime.
I've uploaded my app to the Developer Console, but didn't publish it yet(it's still in draft mode).
Whenever a user who is not a test user tries to use the In App Biiling he receives the following error -
User is not eligible for this purchase
I've looked around and read some other question regarding the issue, and now I know that the reason for this error is because the user is not a test user and the app hasn't been published.But I still want to be sure of one thing -
When I publish my application, will the In-App Billing work and users will not receive these errors?
Thanks!
The best way to make sure it works like this would be to try it out by yourself.
You can create a new Google Play user account, register it as an alpha/beta tester and release a alpha/beta version of your app (look for "Testing with real transactions" section for more details). It's safe because only your beta tester user can see published application and nobody else. Then install this app to the beta tester's device and check in-app billing works. Then upload a new draft version and make sure beta tester is not impacted.
I had same concern before I published a first version of my application. From today's experience I can say, that normal Google Play users can only see a published version and they do not get any error messages when a new draft is uploaded. Hope this helps.