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 meet the same problem today. In my case, my app still has an alpha release which declared sensitive permissions, so I manage alpha release, and click RELEASE TO PRODUCTION button.In the PREPARE RELEASE page, "Declare sensitive permissions" session appears.

After finish the form and save the release, I just discard it and manager the PRODUCTION TRACK again.

hope this helps.

Answer 2

This is the list of sensitive permissions that google wants us to include in app before publishing it.

Also, We got an extension until March 9 2019 from Google about the SMS permissions.

android.permission.INTERNET

android.permission.ACCESS_NETWORK_STATE

android.permission.BLUETOOTH

android.permission.CAMERA

android.permission.RECEIVE_SMS

android.permission.SEND_SMS

android.permission.READ_SMS

android.permission.VIBRATE

android.permission.WRITE_EXTERNAL_STORAGE

android.permission.READ_EXTERNAL_STORAGE

android.permission.READ_CONTACTS

android.permission.READ_PHONE_STATE

android.permission.USE_CREDENTIALS

android.permission.WRITE_CONTACTS

android.permission.WRITE_SYNC_SETTINGS

android.permission.READ_SYNC_SETTINGS

android.permission.READ_SYNC_STATS

android.permission.AUTHENTICATE_ACCOUNTS

android.permission.GET_ACCOUNTS

android.permission.MANAGE_ACCOUNTS

android.permission.INSTALL_SHORTCUT

android.permission.UNINSTALL_SHORTCUT

android.permission.RECORD_AUDIO

android.permission.MODIFY_AUDIO_SETTINGS

com.android.vending.BILLING

Answer 3

These instructions tell you what to do if you can't see the form: http://support.google.com/googleplay/android-developer/answer/9214102

You could also have more complicated issues if you have testing and production track whose APKs/Bundles require different permissions. You need all the permissions from the different release tracks to be in a single release (in one release track).

Answer 4

Google restricts apps from using access permission via SMS, callsGoogle has now restricted the use of high-risk and sensitive permissions via SMS and phone calls for apps on PlayStore as part of its recent policy change that now requires apps to be verified manually by the search engine giant.

The company has declared March 9 as the deadline for developers whose apps already include these permissions to either file a declaration confirming their app requires these permissions for core functionality, submit a request application for more time allotment to bring their app into compliance, or remove the permissions from their apps immediately.

"Apps that fail to meet policy requirements or submit a declaration form may be removed from Google Play," the company wrote in a post late on Monday.

While cases where Google is allowing access to these permissions include an app being the default handler for calls, SMS, Google Assistant queries, the other use cases are expected to request a temporary extension and work to find an alternative way.

please check on this: https://play.google.com/intl/en-US/about/privacy-security-deception/permissions/

If you believe your app meets the policy requirements for acceptable use or is eligible for an exception, you should declare any Call Log or SMS permissions directly through the Play Console at here: https://support.google.com/googleplay/android-developer/answer/9214102

Answer 5

Google’s restrictions on SMS/Call Log permissions policy

You need to implement the :

SMS Retriver API

in order to remove those permission and leave them only in the needed time. Follow as stated here : Sms Retriver API . If you need more help let me know, i have implemented it already.

Answer 6

This is the correct answer. The prompt one went away once I published updates to all channels.

From play support email exchange...

You'll just need to assure you release a compliant APK to each track that has the sensitive permissions, as this likely happened because the Permissions form in the Play Console saw multiple APKs.

However, please be assured our engineers are looking into streamlining this process, and I apologize for any inconvenience.

Support's instructions are...

To upload a new APK, you need to submit the declaration form for all the permissions that you’re currently using in your app. Please see the following instructions to submit the form:

1. Go to the Console > App release > Click ‘Create a release’ > Upload a new APK that you want to release

2. Retain the current version of APK

3. Click ‘Add from library’ > Upload all active APKs to cover all permissions across the tracks in your app

4. You can find active APK in Release management > Artifact library

5. Fill out the Declaration Form > Click "Save" at the bottom of the page

After that, please stay on the same page and follow the next steps:

1. Deactivate and remove ONLY the old APKs which you do not want to release.

2. Click "Save" again then select "Review"

3. Then, you'll be able to release a new version of APK by clicking "Start Roll Out" button.

Also, if you do not want to use an APK (with sensitive or high-risk permission) under other track, please do not forget to replace them to a new APK.