Closed valenvb-ag closed 1 month ago
Same here!
Tried with @plasmohq/edge-addons-api
or manually with fetch
in Node.js (on macOS) carefully following the documentation and it's giving me the same error
We had the issue since July 12th on our end, and it's been blocking our automated release pipeline
@valenvb-ag @MaximeHeckel Can you guys confirm whether you are still seeing this issue?
@yvsubhash just tried now and was able to push a draft using the API
Thank you for the quick fix!
Confirmed, we're able to push up packages via API again as well! Thanks for getting this resolved!
I have also encountered this problem. The draft was uploaded and verified successfully, but the publish failed, with the same response result and error message as yours.
However, it can be published manually and successfully with just one click on the Publish
button in the dashboard page.
I was able to publish just fine not long ago, so what happened?
Edit: A few days passed. I could now publish packages via the API.
Describe the bug Since at least July 17, 2024, the package upload status endpoint (/v1/products/$productID/submissions/draft/package/operations/$operationID) described in the documentation has been returning a
Failed
status, with no error code or errors. Eg:We have seen this across multiple extensions. Manually uploading via the Partner Center is still functional.
To Reproduce Follow the steps to upload an extension package using the API outlined at https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/publish/api/using-addons-api
/v1/products/$productID/submissions/draft/package/operations/$operationID
"status":"Failed"
, but with noerrorCode
orerrors
listed.Expected behavior A response containing
"status":"InProgress"
or"status":"Suceeded"
, or at very least some information about the errors encountered.Desktop (please complete the following information):
curl
ornodejs
for the APIAdditional context We have seen this across two different
$productID
values.