Release error is coming Check for errors on the Permissions Declaration Form (play store error)

A

6

29

It is showing this error

here is my permissions

<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.GET_ACCOUNTS" />
<uses-permission android:name="android.permission.READ_PROFILE" />
<uses-permission android:name="android.permission.READ_CONTACTS" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />

And I have done the dynamic permission thing. Still, I am getting this error.

Aguste answered 24/1, 2019 at 18:3 Comment(14)

do you had ask permission at runtime – Arthritis 24/1, 2019 at 18:12

Yes, I have released the build 5 days back with same permission. That is available at play store right now but today I am getting this. I do not know why. – Aguste 24/1, 2019 at 18:23

I'm having the same problem today. – Accomplice 24/1, 2019 at 18:33

Did you resolve this issue @NateNiemi – Aguste 24/1, 2019 at 18:34

@PiyushUpadhyay Nope, not sure what happened. No changes to manifest. It worked yesterday. Odd coincidence we both just noticed this problem today. – Accomplice 24/1, 2019 at 18:37

I'm having the same problem no changes in permission, maybe some bug in Play Console? – Coopery 24/1, 2019 at 19:24

Same problem here. – Coriolanus 24/1, 2019 at 21:6

Glad I'm not alone. I put in a support request to google. We will see what they say. – Accomplice 24/1, 2019 at 21:40

i have same error here and in my app i did not add any permission ... – Bandaid 24/1, 2019 at 23:13

I'm experiencing exactly the same error right now... incremented build and untouched permissions.. – Kenner 25/1, 2019 at 3:11

Glad I am not alone. – Nostomania 25/1, 2019 at 10:8

Same here... at first I thought it was because today was my first time submitting the app using their API, but after that failed (with a similar message) I tried to submit it manually through the Google Play Console website and I'm seeing the same error. Don't see the permissions form though, not even after retrying to submit. – Wishbone 25/1, 2019 at 11:28

Everything is now working for me. I made no changes to anything. I think this confirms it was a bug on Google's end. – Accomplice 25/1, 2019 at 18:44

Guys. I solved the problem. First check if you have your APK in beta or alpha with the non-permitted permissions. If you do, create a new release and upload to alpha then beta and finally production. – Pithos 25/1, 2019 at 23:32

K

1

I can now confirm this issue is fixed as of Jan 26, 2019 Asia Pacific Time.

Kenner answered 25/1, 2019 at 3:8 Comment(2)

Same here. No changes, just created a new build (to increment the version code) and submitted that successfully on Jan 28 2019. – Wishbone 28/1, 2019 at 12:9

Just received a response from Google. Hi there, Thanks for contacting Google Play Developer Support. I understand your Play Console wants you to fill out a permissions form, though you haven't added any new permissions. This issue was affecting a number of developers, but I have received word this morning that the issue was corrected. You should be able to upload an update APK as normal (please note you may need to first discard any existing drafts). I hope that helps! Please let me know if you have other questions. Regards, Pete Google Play Developer Support – Kenner 29/1, 2019 at 3:32

P

3

I solved the problem this way. You might have an APK (alpha, beta or prod) with the non-permitted permissions.

Step1: create a new release without the non-permitted permissions
Step2: roll it over to Alpha
Step3: roll it over to Beta
Step4: roll it over to Production

Greetings!

Pithos answered 25/1, 2019 at 23:38 Comment(1)

I tried everything but this, and this is the only working solution. If I try to publish to beta without publishing to alpha, I get the error. – Synthesis 8/2, 2019 at 8:20

K

1

I can now confirm this issue is fixed as of Jan 26, 2019 Asia Pacific Time.

Kenner answered 25/1, 2019 at 3:8 Comment(2)

Same here. No changes, just created a new build (to increment the version code) and submitted that successfully on Jan 28 2019. – Wishbone 28/1, 2019 at 12:9

Just received a response from Google. Hi there, Thanks for contacting Google Play Developer Support. I understand your Play Console wants you to fill out a permissions form, though you haven't added any new permissions. This issue was affecting a number of developers, but I have received word this morning that the issue was corrected. You should be able to upload an update APK as normal (please note you may need to first discard any existing drafts). I hope that helps! Please let me know if you have other questions. Regards, Pete Google Play Developer Support – Kenner 29/1, 2019 at 3:32

L

1

Looks like the problem is currently affecting users who removed SMS and CALL_LOG from their app due to the new policy and also submitted the form. From yesterday these apps fails to update for the above error without giving any solution within the UI due to the fact that the app doesnt have those permissions anymore. Its clearly a bug in the store. I've tried via API and off course getting the same result:

{
  "code" : 403,
  "errors" : [ {
    "domain" : "androidpublisher",
    "message" : "Permission declaration is invalid because the declaration has not been accepted in the Play Console.",
    "reason" : "permissionDeclarationNotAccepted"
  } ],
  "message" : "Permission declaration is invalid because the declaration has not been     accepted in the Play Console."
}

I have a pipeline currently triggering each hour to see if this goes away. Its already more than 24 hours.

Leupold answered 25/1, 2019 at 14:39 Comment(0)

H

0

I too am getting this Error message. Submitted a build this morning, no issues. No permissions added, and no strange permissions. I suggest everyone impacted submit feedback to Google via the link below!

https://support.google.com/googleplay/android-developer/contact/publishing

Handmaiden answered 24/1, 2019 at 23:38 Comment(2)

I have actually heard from my google rep - they are aware and on the issue ASAP! – Handmaiden 25/1, 2019 at 11:56

Great news... I did not yet hear from them after submitting the yesterday.. – Coopery 25/1, 2019 at 13:1

S

0

I'm getting the same error.

My app has quite ordinary permissions:

<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
<uses-permission android:name="android.permission.VIBRATE" />

Seems like an issue from Google's side. Submitted yesterday with no issue. Starting facing this issue today only.

Salmons answered 25/1, 2019 at 16:19 Comment(0)

C

0

It's already well answered by FrankMonza in https://mcmap.net/q/485719/-release-error-is-coming-check-for-errors-on-the-permissions-declaration-form-play-store-error.

For some still having a problem with this issue, try to update the APK(s) which currently resides on another channel. We have an outdated APK in the Alpha channel. After we updated it to the latest APK, we are then able to propagate it through Beta, then Production.

Cannonade answered 28/1, 2019 at 1:51 Comment(0)

Recommended topics

Hot tags