Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API for submitting to the edge store has changed #1418

Closed
5 tasks done
GorvGoyl opened this issue Feb 11, 2025 · 2 comments
Closed
5 tasks done

API for submitting to the edge store has changed #1418

GorvGoyl opened this issue Feb 11, 2025 · 2 comments
Labels
pending-triage Someone (usually a maintainer) needs to look into this to see if it's a bug

Comments

@GorvGoyl
Copy link
Contributor

Describe the bug

It seems that the old API is no longer working, and MS is suggesting using the new API format for publishing extensions.

https://blogs.windows.com/msedgedev/2024/09/30/enhanced-security-for-extensions-with-new-publish-api/

https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/publish/api/using-addons-api?tabs=v1-1

Could you please update it in the wxt submit command?

Reproduction

Error: Command failed: wxt submit --edge-zip build/CGW_edge_production.zip

 ERROR  [POST] "https://api.addons.microsoftedge.microsoft.com/v1/products/286a6164-6562-4a8e-a779-a449ad869ff8/submissions/draft/package": 410 Gone

  at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
  at async EdgeApi.uploadDraft (node_modules/.pnpm/publish-browser-extension@2.2.2/node_modules/publish-browser-extension/dist/cli.cjs:3066:17)
  at async EdgeAddonStore.uploadAndPollValidation (node_modules/.pnpm/publish-browser-extension@2.2.2/node_modules/publish-browser-extension/dist/cli.cjs:3166:29)
  at async EdgeAddonStore.submit (node_modules/.pnpm/publish-browser-extension@2.2.2/node_modules/publish-browser-extension/dist/cli.cjs:3153:5)
  at async Task.task [as taskFn] (node_modules/.pnpm/publish-browser-extension@2.2.2/node_modules/publish-browser-extension/dist/cli.cjs:3511:11)
  at async Task.run (node_modules/.pnpm/listr2@8.2.4/node_modules/listr2/dist/index.cjs:2143:11)

✖ Edge Addon Store [FAILED: [POST] "https://api.addons.microsoftedge.microsoft.com/v1/products/286a6164-6562-4a8e-a779-a449ad869ff8/submissions/draft/package": 410 Gone]

 ERROR  Submissions failed: 1

  at submit (node_modules/.pnpm/publish-browser-extension@2.2.2/node_modules/publish-browser-extension/dist/cli.cjs:3531:11)
  at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
  at async CAC.<anonymous> (node_modules/.pnpm/publish-browser-extension@2.2.2/node_modules/publish-browser-extension/dist/cli.cjs:3921:5)

Steps to reproduce

No response

System Info

N.A.

Used Package Manager

pnpm

Validations

@GorvGoyl GorvGoyl added the pending-triage Someone (usually a maintainer) needs to look into this to see if it's a bug label Feb 11, 2025
@aklinker1
Copy link
Collaborator

@aklinker1
Copy link
Collaborator

I've just released v3.0.0 of publish-browser-extension, which drops support for v1.0 auth, and WXT v0.19.27, which adds support for this new version to WXT. You should be able to upgrade via:

# Update the subdependency
npm upgrade publish-browser-extension

Or by deleting your lockfile and running npm i again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-triage Someone (usually a maintainer) needs to look into this to see if it's a bug
Projects
None yet
Development

No branches or pull requests

2 participants