CODEWITHSUNDEEP
javaandroidgoogle-play-console
Oleg V.
Oleg V.

Reputation: 329

Permissions Declaration Form still showing in Google Play Console even with updated APK uploaded without READ_CALL_LOG

TL;DR

Google Play Console forces to show Permissions Declaration Form (see below) as soon as "Create Release" button clicked even if updated APK uploaded without READ_CALL_LOG which caused the warning email from Google before.

Question

How to avoid the Permissions Declaration Form which looks irrelevant if releasing updated APK without sensitive permissions?

Problem in details

  1. PRODUCTION and ALPHA releases were submitted with READ_CALL_LOG permission before Google emailed about prohibit to use it.

  2. Now, during creating new release and once clicking "Create release" button -- it disappears in favor to "Edit release" button, however, there is no release behind (e.g. in BETA track). The only message "You have a release in production/beta/alpha that hasn't been rolled out" within the respective track section is showing.

  3. There is also warning in App Release menu item "You can't edit this app until you create a new app release declaring sensitive permissions.". So, it would be nice to create release which doesn't use sensitive permissions at all.

Could you please advice.

Not appropriate Permissions Declaration Form

Permissions Declaration Form

enter image description here

Upvotes: 16

Views: 16309

Answers (5)

future23
future23

Reputation: 1

I also encountered the same situation. Even though I uploaded the APK without permission, the sensitive permission form was still active. But I sent it for review as is and it was approved.

Upvotes: 0

NeoTechni
NeoTechni

Reputation: 179

How do you even find this form? The dev console is a mess

Upvotes: 8

Yannick Schuchmann
Yannick Schuchmann

Reputation: 502

As stated in comments there isn't a "No" option anymore since mid March 2019.

AFAIC that's because "Google" scans all APKs for included permissions which in fact should make the whole process simpler instead of more confusing.

The solution for me was to check all releases if they contain old APKs and remove/update them first.

In my case it was a very old release down in the internal test track (below Alpha release track). To fix that I had to create a new internal test release with the new APK (the one without the permissions) and deactivate the old APK.

Remember to check that for all stale releases. For me it was just the internal one.

After that you can create a new production release and the permission form should be gone.

Upvotes: 2

CHIRANJIT BARDHAN
CHIRANJIT BARDHAN

Reputation: 151

I have also found same issue. Finally i got a solution.

Solution:

  1. Remove the SMS related permission and generate signed APK
  2. Upload APK in beta and try to publish it from beta.
  3. Once beta upload success that SMS compliance form will not display on production realese more.
  4. If you can publish it from beta then fine else upload another APK incrementing version code from manage production
  5. Now you can publish it successfully.

Upvotes: 2

Oleg V.
Oleg V.

Reputation: 329

Disclaimer

  • "No" option was removed since mid March (see details in comments), so the suggested solution doesn't work anymore.

Solution (does NOT work since mid March)

  • Upload app binary without sensitive permissions inside, i.e. remove their usage from the app.
  • Submit this version with "No" selected for Compliance Status at "Permissions Declaration Form". Note: at this stage you will see the warning "You must meet the permissions policy..."
  • For the next version all warnings will disappear as soon as app will be submitted. Hence, on the next app upload -- no warning and forms will be appread.

P.S. Unfortunately, there was no options found how to avoid the form at all without app version release.

Upvotes: 5

Related Questions