Repository navigation
[Bug - Partner Center] Unable to publish revised extension metadata #743
Description
Describe the bug
I cannot publish a draft with revised extension metadata. It is always rejected by saying that the extension version must be larger than the current one.
To Reproduce
Steps to reproduce the behavior:
- Go to the [store list] tab of my extension and update the privacy info and description of my extension in all languages.
- Save and publish the draft.
- See error saying that the extension version must be larger than the current one.
Expected behavior
A draft with revised extension metadata should be publishable.
Desktop (please complete the following information):
- OS: Windows 10 SP1
- Browser: Firefox 154
Activity
danny0838 commentedon Sep 1, 2026
Under further investigation I suspect it's related to an accidental "duplicated" upload.
More info:
The reject for the draft extension with same version is understandable. However, since there is NO WAY to remove the draft or the uploaded extension in the draft, I am stuck and cannot update the extension metadata without releasing a new version.
Rahul-Bauri commentedon Sep 2, 2026
Hi Danny Lin (@danny0838)
Could you please provide a HAR file and any relevant screenshots of the error? These will help us better understand the issue and reproduce it in our environment. The additional details will also assist the engineering team in investigating the problem more effectively and identifying a resolution. Thank you.
danny0838 commentedon Sep 2, 2026
What is HAR file?
Unfortunately I cannot do the same thing again since it's totally stuck currently. Even if I upload another extension for testing, it would require a review with an indefinite work time (and will probably be rejected since it's a duplicate or a non-functional dummy).
danny0838 commentedon Sep 2, 2026
Simplified steps:
1. (Possibly related) Upload a package with same version (same code but different metadata such as mtime):
2. Edit privacy and/or description in each language:
3. Save and submit the draft
4. Get rejected due to "version number needs to be higher than previous version"
Rahul-Bauri commentedon Sep 2, 2026
Hi Danny Lin (@danny0838)
Thanks for providing the detailed repro steps.
Based on the information shared, the behavior appears to be expected. In step 1, a new extension package (ZIP) is uploaded with the same extension version as the currently published version. Once a package is included in the draft submission, Partner Center treats it as an extension/package update and validates the version number in the package manifest.
Because the uploaded package still has version 2.27.1, and the currently published extension version is also 2.27.1, the submission is rejected with the message:
"The Zip version number needs to be higher than previous version: 2.27.1"
If your goal is only to update Store Listing information (for example, privacy information, descriptions, or localized metadata), there is no need to upload a new package. You can update the Store Listing fields and submit those metadata changes directly.
If you do need to upload a new package, the extension version in the package manifest must be incremented to a value higher than the currently published version (for example, 2.27.2).
Could you please confirm whether:
If this is a metadata-only update, we recommend creating the draft without uploading a new package.
Thanks. Hope This helps.
danny0838 commentedon Sep 2, 2026
As above mentioned, the issue is that if the package with same version has been uploaded by accident, THERE IS NO WAY TO REMOVE THE UPLOADED PACKAGE for publishing a metadata-only change, except for uploading a new package with incremented version.
There should be a way to either remove the uploaded package or remove the draft. (I recall that it used to be, and thus this is also a REGRESSION).
Rahul-Bauri commentedon Sep 30, 2026
closing this issue here as we see that the updated version is now visible in the store.