First, Plasmo is awesome and definitely making the Chrome extension dev experience better.
My extension was already in the Chrome Web Store, but I made some changes that required additional permissions. When I ran the bpp action, all I got in the output was:
I tried the verbose option and setting chrome.verbose = true in the keys, to no avail.
I was able to fork the action and increase the detail of the error logging (which involved vendoring bms, as it actually swallows the useful information when it does getVerboseError).
Eventually I was able to see in the response body:
Publish condition not met: To publish your item, you must provide mandatory privacy information in the new Developer Dashboard: https://chrome.google.com/webstore/devconsole. Click on your item from the home page and enter this information on the Privacy practices tab.
Once I saw this it was easy to make the change in the web store and then the action was able to submit it successfully.
Could we get the 4xx responses from the extension stores displayed here? I think it will be very helpful for debugging issues.
I only tried Chrome though I have a feeling the issue exists for other stores.
If you want me to open this in bms instead I can, I think changes may be required in both. We could get away with only changes in bms if we put the response body into the error message though.
Which browsers are you seeing the problem on?
Chrome
Relevant log output
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.
What happened?
First, Plasmo is awesome and definitely making the Chrome extension dev experience better.
My extension was already in the Chrome Web Store, but I made some changes that required additional permissions. When I ran the bpp action, all I got in the output was:
I tried the
verboseoption and settingchrome.verbose = truein the keys, to no avail.I was able to fork the action and increase the detail of the error logging (which involved vendoring
bms, as it actually swallows the useful information when it doesgetVerboseError).Eventually I was able to see in the response body:
Once I saw this it was easy to make the change in the web store and then the action was able to submit it successfully.
Could we get the 4xx responses from the extension stores displayed here? I think it will be very helpful for debugging issues.
I only tried Chrome though I have a feeling the issue exists for other stores.
If you want me to open this in
bmsinstead I can, I think changes may be required in both. We could get away with only changes inbmsif we put the response body into the error message though.Which browsers are you seeing the problem on?
Chrome
Relevant log output
No response
Code of Conduct