-
-
Save manishpatelgt/224a330a5d4c7eaf783ca3ff5d522274 to your computer and use it in GitHub Desktop.
Cross check all of your apps and verified that which of fllowing app contain the SMS and Call_Log Permissions. Whether you app active in Beta, Alpha OR | |
in Production | |
Below steps for update right apk in track | |
For the active app, please follow the steps bellow. Please make sure you do this process in Beta track: | |
1. Create a release | |
2. Click Retain for the old APK | |
3. Then, you'll see the Declaration Form regarding the retained (old APK) | |
4. On the form, for the Compliance status, please choose "No, this release does not meet the SMS and Call Log permissions policy" | |
5. Go to "Declarations" section in the end and check the four boxes. | |
6. Click "Save" to save the changes. | |
7. Click create a release again | |
8. Then, deactivate the old APK (retained APK) again. | |
9. Save your changes again. Then, click on Review. | |
10. You'll be able to click on the "Start Roll Out" button. | |
After this process, you would be able to update your app on the desired track. |
I have removed all the permissions several release ago, but still today I can see the problem..
Even I checked the merged AndroidManifest file, there is no policy violating permission.
Even when I am trying to upload new apk, the declaration is not getting removed.
Couldn't understand, what to do..
@Dan-ru Did you solve the problem?
I suggestion who are not seeing declaration form or step 4. Please reach google play support team asap.
Go to https://support.google.com/googleplay/android-developer/answer/7218994?hl=en
ok. So you have to find out all the builds related to alpha, bita , production and have to update with the new build(removed permission) on all tracks. It will be solved.
I too cannot find the option mentioned in step 4 as of today.
I removed permissions like this:
<uses-permission android:name="android.permission.READ_PHONE_STATE" tools:node="remove" />
<uses-permission android:name="android.permission.READ_SMS" tools:node="remove" />
Even if your app's AndroidManifest.xml
does not use these permissions, some of the libraries you include can use these permissions.
Then I created a new release in Internal Test Track
and generated a new release apk with removed permissions and uploaded this apk to the newly created release. Permission declaration form was there from the old apk and I just checked an arbitrary option just to be able to save the form. After saving the form I review and rollout the release.
I repeated the same steps with the same apk with removed permissions for Alpha
and Beta
test tracks and rollout releases for both.
In the last track (Beta), the permission declaration form was not there.
Same problem.
All those permissions has been removed several releases ago.
I have Alpha and Beta tracks. In any tracks it asking me to fill "Declare sensitive permissions". I can't find way to get rid of it.
Such option doesn't exist anymore.