Steps for uploading apk which is not contain SMS & CALL permissions

gistfile1.txt

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.

Not able to see 4th option in my google console.
4. On the form, for the Compliance status, please choose "No, this release does not meet the SMS and Call Log permissions policy"

Why not ? Are you sure you're trying this approach in older version apk ?

@manishpatelgt @MayankAtulkar please i have the same issue i can't see 4th option

Ok let me check wait

@ahmedespritien did you upload new apk ?

@manishpatelgt yes i uploaded new apk with new version name and version code without any permission mentionned
{
android.permission.READ_SMS

android.permission.RECEIVE_SMS`)
} and please take in consideration that the old apk contains those permissions

You need to do above steps in older apk. That's the point.

And remember do you know which mode contains apk that has CALL and SMS permission? You need to perform above steps only for that mode.

Like I have apk in beta mode and that's include SMS and CALL permission So i can processed for that only.

After uploading new apk do process from steps 2

2. Click Retain for the old APK

so do you mean that i should click retain for the old apk that already published on store and already exist on active artifacts ?

Yes exactly for which that has SMS and CALL permissions.

:( so my brother this is what i did but i still receive the same list

Are you getting this screen after clicked on retain apk ?

yes :(

I think you need to contact google play console support team as soon as possible because today is 26 March and my solution might not work for that.

ok thank you for support

I have the same problem. Not able to see 4th step.

I think i resolve it.
You MUST update ALL versions of your app (alpha, beta etc.) and remove SMS/CALL permissions from them.
Then the field "previously declared permissions" will be deactivated.

Glad to hear that

Still m getting same issue no step no. 4th let me know if you find any solutions.

Can you first check which mode has older apk that contains SMS & CALL permissions ? You need to upload apk in that mode first and then need to perform retain steps.

same issue :(

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.

4. On the form, for the Compliance status, please choose "No, this release does not meet the SMS and Call Log permissions policy"

Such option doesn't exist anymore.

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.