Issue with Microsoft Edge Add-ons API - Status Not Updating After Publishing

Anonymous
2023-05-26T14:33:24+00:00

I am facing an issue with the Microsoft Edge Add-ons API while attempting to publish my Edge extension using GitHub Actions' Ubuntu runners. Despite receiving a successful HTTP 202 response after publishing the app, the status of the submission does not update in the UI as expected.

So far:

  1. I can successfully fetch the authentication token using the API.
  2. I can update the zip files of the existing draft submission using the API, and I can observe the changes in the UI.
  3. However, when I use the API to publish the app for review, the status in the UI remains unchanged even though I receive a HTTP 202 response.

I can see that my package has been verified. I can also publish my extension using the UI button and I can see the status change from "in draft" to "in review", which is what I expect to see when I publish with the API.
My API request :

response=$(curl \

    -H "Authorization: Bearer ${{ steps.token.outputs.token }}" \

    -H "Content-Length: 0" \

    -X POST \

    -i \

    https://api.addons.microsoftedge.microsoft.com/v1/products/${{secrets.DWL_EDGE_PRODUCT_ID}}/submissions)

This is the value of response :

HTTP/1.1 202 Accepted

Content-Length: 0

Location: <value>

Request-Context: appId=<value>

Strict-Transport-Security: max-age=31536000; includeSubDomains

Date: Fri, 26 May 2023 13:50:39 GMT

Microsoft Edge | Browser extensions | Android

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes
Answer accepted by question author
  1. Anonymous
    2023-05-26T15:05:31+00:00

    Hi Romano

    I am Dave, I will help you with this.

    I apologize, Community is just a consumer forum, due to the scope of your question can you please post this question to our sister forum on Microsoft Q&A (The Developers Forum)

    Over there you will have access to a host of developers and API experts and will get a knowledgeable and quick answer to this question.

    https://docs.microsoft.com/en-us/answers/index....

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful