microsoft / microsoft/MicrosoftEdge-Extensions

[Bug - Partner Center] Uploading a new extension package (.zip) in Partner Center fails

Open
#603 13 comments 0 reactions 1 assignee View on GitHub

@Rahul-Bauri is already working on this.

Since Jun 4, 2026.

Bug Partner Center Tracked
Dominant language
JavaScript
Stars
245
Forks
149
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

Uploading a new extension package (.zip) in Partner Center fails. The UI shows a generic "Something went wrong. Please check your network settings" banner. The browser console shows an HTTP 400 "The specified block list is invalid." response on the PUT ...blob.core.windows.net/...&comp=blocklist request, preceded by several failed Put Block requests to the same blob endpoint.

The connection is a stable, verified 1.1 Gbps. A previous version of the same extension uploaded successfully.

To Reproduce

  1. Go to Partner Center > Microsoft Edge program > the extension > Packages
  2. Click Update / upload and select the .zip package (~34 MB, 657 files, Manifest V3)
  3. Wait for the upload progress to complete
  4. See the error: "Something went wrong. Please check your network settings"
  5. Open browser DevTools > Network/Console and observe a 400 (The specified block list is invalid.) response on the PUT ...blob.core.windows.net/...&comp=blocklist request, preceded by several failed Put Block requests to the same blob endpoint

Expected behavior

The package upload completes and the new version is accepted for review/certification, as with previous uploads of this extension.

Screenshots

Image

Desktop (please complete the following information):

  • OS: macOS 15 (Sequoia)
  • Browser: Microsoft Edge (also reproduced in other browsers)
  • Version: 148.0.3967.96

Additional context

N/A

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.