Google play console said “You can't edit this app until you create a new app release declaring sensitive permissions” how to fix it?

Question

I couldn\'t publish my new released on google play console this morning. It has shown,

\"You can\'t edit this app until you create a new

Answer 1

I'm also faced same issue. After a long research i have fixed this.

First make sure you have removed the permission which is mention by Google' Polices.

First need to Deactivate Old App.

Follow the below instruction. Please make sure you do this process in Beta track:

1. Create a release
2. Don't select or drop the new APK now.
3. Give any name which is your old app name into the Release Name section.
4. Save the changes(Hope it not ask any error).
5. Press Review and then Start Rollout to production.(Don't worry it will only deactivate the Old App.)

Now can't see your old apk in beta section. Then you can do your as usual beta release.It will not ask the Declaration Form.

hope this will help for your headache.

Answer 2

In my case Google removed my app from production, to be able to submit a new release without using the sms i had to:

• Retain the previous release (where i was using sms),
• Because of the first step the permission form appeared,
• I filled the form
• Added the new apk (without sms)
• Deactivated the old apk
• Only then i was able to roll to production.

This is not the intended behavior based on the email i received from google when my app was removed:

Option 1) If your app does not require access to Call Log or SMS permissions:

Remove the specified permissions from your app’s manifest, or migrate to an alternative implementation, then publish the updated version of your app using the standard release process.

So adding the apk that do not have sms in it should work but it did not until i retained the old one, filled the form, and deactivated the old apk.

Answer 3

You have to take run time permission from user as you have some sensitive permission in the app like read or write external storage or something else. So take run time permission from user and rebuild the app and release.

Answer 4

Was facing issue same kinda issue. It was from Google side in my case.
Solution:
If you have production apk(even with no sms permission used) with v225 &
Internal test track with v900(even with no sms permission used) , then

You should submit higher version

i.e. v900+ apk(with no sms permission used ofcourse) to production, this error will be dissappeared and you'll be able to rollout.
Google should have ignored Internal test track apk in first place but nevertheless this thing worked for me.