Closed tanmayrajani closed 1 month ago
Releases are done via the actions tab, not by creating releases manually. The release and tag should be deleted and then done via the Release action.
thanks @fregante, I forgot 🤦♂️
also, getting "{\n \"error\": \"invalid_grant\",\n \"error_description\": \"Bad Request\"\n}"
in chrome, whereas firefox succeeded after first error (needed to accept ToC)
however, chrome upload succeeded despite getting that error :)
it shows updated ~version~ date in chrome developer dashboard.. but on the webstore, it's still old version 😐
@fregante should we renew client ID, secret etc as mentioned in https://github.com/fregante/chrome-webstore-upload-cli/issues/36 for the time being?
Both stores may require you to update some details on the developer dashboard. Make sure there's a privacy policy on Google's dashboard and a verified email.
As for the key, it's up to you. Just remember to update the workflow too because it's using an older version of the uploader.
But that's strange, invalid grant means that the token is wrong, so yes, it's probably best to follow the guide again.
Once you follow the guide to update the Chrome token, please release a new version via the Actions tab as described. It'd be great to merge https://github.com/tanmayrajani/notifications-preview-github/pull/125 before then as well.
@fregante sure, I'll take a look at this soonish
Also, Firefox asked for source-code upload (you might be getting emails too I guess). I provided it manually.. but I was wondering whether this is something that can be done via github action too
you might be getting emails too I guess
Yes, AMO is really annoying.
I was wondering whether this is something that can be done via github action too
Blocked by:
Technically there's an API endpoint now but no libraries for it
Ping @tanmayrajani could you generate new keys with the guide at:
https://github.com/fregante/chrome-webstore-upload-keys#how-to-generate-google-api-keys
I published a release yesterday with a fix for #130 but it doesn't seem to have reached chrome/firefox stores. Not sure what's wrong..
cc @fregante if you have any idea, could you please look into?