13

For a couple of months, I tried updating an app. The thing is I wanted to use the SMS permissions.

To do I had to fill the sensitive permission form in google play console.

After doing that, my app was rejected.

Fast forward, I decided to take my app project a different route. I don't need the Sms functionality anymore.

I have removed the permissions from my android manifest, bump my app version. Uploaded a new version and only for it to be rejected for the same permission reason. enter image description here

Which I thought was weird because I am not seeking the permissions anymore for my app.

I checked the App Content tab, and I could see that there is some permission stuff still going on with my app. enter image description here

Unfortunately, for some unknown reason, Google isn't offering any means of deactivating or removing the permissions from the play console.

I am unable to update my app for this reason. I have tried to make contact with the play team, but they haven't gotten back to me for some reason.

I am wondering if there is a fix for this? I have tried all that I could find online on the permission problem but nothing has seemed to work out. enter image description here

LearnToday
  • 2,762
  • 9
  • 38
  • 67

3 Answers3

14

I was having the same issue. It turns out, it's because I had an old APK that still used that permission in another release track. The trick is to upload new APKs to all release tracks that have old APKs in them.

Here's the article that provides more details: Dear Google’s Permissions Declaration Form, Can We Break Up?

Scott J. Swindell
  • 149
  • 1
  • 3
2

This issue can be resolved by removing sms, call permissions from manifest and create signed apk/bundle again for uploading to playstore.

Try to examine Artifact library in your play console. Click on version code's down arrow of apk/bundle file and check for required permissions section, are still able to see call,sms permissions? If yes, you need to check manifest file again and remove sensitive permissions.

Priyanka
  • 1,791
  • 1
  • 7
  • 12
  • 1
    So, I have gone through my libraries, I realized the SMS library was requesting the permission. I removed that from the SMS package. let me try again, fingers crossed. – LearnToday Oct 12 '20 at 12:34
  • All the best, just go through the steps I have shared, before publish your app. If it does not contain sms or call permissions there you can submit it without any fear. – Priyanka Oct 12 '20 at 12:42
  • Is it possible that the read and write contacts are sensitive permissions too? – LearnToday Oct 12 '20 at 12:45
  • 1
    No read write do not comes under sensitive permissions – Priyanka Oct 12 '20 at 12:49
  • Does location permission lies under critical permissions? or background location? – K_Chandio Nov 22 '22 at 10:32
0

You also can get your app approved without uploading a new APK/AAB, just go to App content scroll down and find Sensitive permissions and APIs and change your declaritions and submit your app for review and Google will send it in production.

Savvy Turtle
  • 11
  • 3