Closed felixfbecker closed 2 years ago
Hey!! 👋
Yeah, I've gone through that as well a few times... Unfortunately, the error we print on the console is the exact same one we get out of the request from https://github.com/fregante/chrome-webstore-upload/blob/main/index.js#L36
But I agree that just that generic error is a bit confusing, so I opened #95 to try to build a better error message, with possible reasons for it to be happening. I'll probably merge that tomorrow, but feel free to also add more "possible reasons" there if you find any!
:tada: This issue has been resolved in version 2.0.1 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Issue
What you did and problem description
I'm sometimes seeing a generic 400 Bad Request error like this:
The last time I had this I figured I needed to update some things on the listing, but this time nothing is there. It looks like others have run into this issue before too: https://github.com/GabrielDuarteM/semantic-release-chrome/issues/7
Suggested solution
Is there any way the plugin could provide a better error message with more details? It looks like it currently just gives us the HTTP status code, but I would bet there is some more detail in the response body that is being omitted.