Account Service Roles & Permissions
See original GitHub issueHello,
I am trying to use this action and I am unable to determine which role I need to set for my account service to authorize the deployment. I know that I have a role or permission with Android because I always get the ##[error]The caller does not have permission
. Even with all the roles set below:
My permission is set to the Release Manager. I am unable to upload anything to the Play Store.
Any help would be appreciated. Here is my workflow:
- name: Upload
uses: r0adkll/upload-google-play@v1.0.4
with:
serviceAccountJsonPlainText: ${{ secrets.SERVICE_ACCOUNT }}
packageName: com.app
releaseFile: app.apk
track: beta
userFraction: 0.15
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
Service accounts | IAM Documentation
This role's permissions include the iam.serviceAccounts.actAs permission. As a result, users granted the Service Account User role on a service account can ...
Read more >Using service-linked roles - AWS Documentation - Amazon.com
Service -linked roles are predefined by the service and include all the permissions that the service requires to call other AWS services on...
Read more >IAM roles
With platform management roles, users can be assigned varying levels of permission for performing platform actions within the account and on a service....
Read more >Creating a role to delegate permissions to an IAM user
After you create the trust relationship, an IAM user or an application from the trusted account can use the Amazon Security Token Service...
Read more >IAM Roles for Service Accounts
Once an IAM Role is created, a service account should include the ARN of that role as an annotation ( eks.amazonaws.com/role-arn ). By...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I fixed it with a missing role.
@codewithtushar yes I added that one. Also, I needed to upload a release manually before being able to upload with this action. The action has to see that your project has a release already uploaded. I’ll try to think of other alternatives I tried but it worked perfectly after a while.