Permission issue Google Play
Solution 1
Problem solved adding user service account email address [email protected] as administrator user in google play settings.
Solution 2
From Google Play Console go to (with admin access):
- Setting (Left Panel)
- Developer Account (Left Panel)
- Users & permissions (Left Panel)
- Click on the Invite New User button.
- Enter the service account email (the same you have in the json file you are using and that google generated when you created the service account)
- Select Administrator in the Role DropDown menu.
- Click on SEND INVITATION
That's it. No one can stop you now! :)
Solution 3
Unfortunately, the accepted answer did not work for us. For verifying a receipt you would need an Access Token. The Access token is being generated by RefreshToken. RefreshToken has an association to a Google account. That Google account should have View financial information
In Google Play console.
- Get Redirect Url using
Android Client ID
- Use Redirect URL with a
Financial Access Enabled Account
to get Refresh Token - Get
Access Token
with that Refresh Token - Use
Access Token
to verify IAP receipts
Solution 4
For those of you that run into this issue and the above solutions don't work and your service account has sufficient permission in Google Cloud and Google Play Console, it can take ~24 hours+ for permissions to propagate (according to other users).
But there's a hack to fix this: update/change/create an in-app purchase in the Google Play Console under the YOUR_APP > Products
section.
Related videos on Youtube
![stebetko](https://i.stack.imgur.com/pHd4T.jpg?s=256&g=1)
Comments
-
stebetko about 2 years
I'm having trouble with
androidpublisher.inapppurchases.get
My project is just according to https://code.google.com/p/google-api-java-client/wiki/OAuth2#Service_Accounts and it worked fine until I migrated to new Google Play Account. So now when I execute request Server-to-Server I am receiving this response.
{ "code" : 401, "errors" : [ { "domain" : "androidpublisher", "message" : "The current user has insufficient permissions to perform the requested operation.", "reason" : "permissionDenied" } ], "message" : "The current user has insufficient permissions to perform the requested operation." }
Anybody is familiar with this response because in google documentation there is no clue about this.
-
ZX12R over 7 yearsRequests without a "person" param also result in the above error. Fix suggested in this related post stackoverflow.com/questions/24306678/…
-
-
user987760 over 9 yearsi am having the same issue, but i didn't understand, where to put it . which settings ? my request is : googleapis.com/androidpublisher/v1/...?access_token=...
-
stebetko over 9 yearsGo to google play console and add service acount email adress from google developer console to settings -> permissions or something like that. I can't tell you exactly the path 'cause I have no longer access as administrator to this app. Hope this help.
-
Erick Engelhardt over 8 yearsThanks! Great! Worked!
-
Deven about 6 yearsYes fixes, but only for "Purchases.subscriptions: get" . when i calling "Purchases.subscriptions: cancel" getting same permission permissionDenied issue (i already give Administrator permission) ?
-
Captain Dashenka almost 6 yearsFor me adding the specific app as a new column in the Users and Permissions page in Google Play Console did the trick - afterwards I didn't have to set the service account to Admin, it worked with just a few relevant check boxes checked.
-
Chirag Purohit almost 6 yearsActually not in google play settings , but at play.google.com->settings->API access -> service accounts -> grant permission
-
SangminKim over 5 yearsDoesn't
administrator user
containView financial information
? -
Roozbeh Zabihollahi over 5 yearsI am not sure. At the time we had this problem, we had one user that has this access, so I wanted to make sure I bold that access name here.
-
Nency almost 5 yearsCreated a new service account in play console with Administrator permission but still getting same error. Any other suggestions ?
-
nating over 2 yearsUpdating the Main Store Listing (e.g. the app title or description as shown in the Play Store) also seems to make the changes take immediate effect rather than having to wait.