-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using service account #15
Comments
I would love to know if you ever found a solution for this. I'm struggling with the same problem. I want to publish my extension in an automated way and see no other solution than using a service account. |
I didn't try service account, but we've configured automated publishing with
You only need to get |
@c301 You should remove your client secret and refresh token from the comment, it's sensitive information. Thanks for your reply. |
@waltertamboer, yeah, that's why I've deleted 70% of it :D |
Have the same issue. Do you have any solution for this now? @PavelVanecek , @c301 and @waltertamboer please? |
I can't remember what I did but I had something working. You can take a look here:
Can't tell you anything more than this since it's been too long ago. |
Hi,
I would like to update my extension using an OAuth2 Service account. My request however fails on
Not a valid developer. Please make sure you have accepted the developer agreement: https://chrome.google.com/webstore/developer/terms.
Have your ever expertimented with using Service accounts? I want to avoid the browser altogether, configure CI server and forget about everything; namely dealing with expiring tokens.
I also posted similar question on StackOverflow.
The text was updated successfully, but these errors were encountered: