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

RomanoFafar 0 Reputation points

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:

I can successfully fetch the authentication token using the API.

I can update the zip files of the existing draft submission using the API, and I can observe the changes in the UI.

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 :

curl \
	-H "Authorization: Bearer ${{ steps.token.outputs.token }}" \
	-H "Content-Length: 0" \
	-X POST \
	-i \${{ secrets.DWL_EDGE_PRODUCT_ID }}/submissions

This is the 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
Microsoft Edge
A Microsoft cross-platform web browser that provides privacy, learning, and accessibility tools.
2,233 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. ShiJieLi-MSFT 8,726 Reputation points Microsoft Vendor

    Hi @RomanoFafar ,

    Welcome to Microsoft Q&A.

    It looks like an API-related issue. You can share issues of Microsoft Edge Add-ons API in the dedicated GitHub forum via Issue about the Add-ons API. And then you'll be answered by relevant Microsoft developers there.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Best Regards,

    Shijie Li

    0 comments No comments