Repository navigation
[Bug - Partner Center] Localized listing descriptions report success but do not persist #740
Description
Describe the bug
When editing localized Microsoft Edge Add-ons listings in Partner Center, Save draft can display “Draft saved successfully” even though the description was not persisted. After closing the editor and reloading the page, the language row is still marked Incomplete and the description is Empty.
The previous success notification can also remain visible after opening another locale, making an unsuccessful save look successful.
To Reproduce
- Open an Edge extension in Partner Center that contains many localized listings.
- Go to Store listings and edit a language.
- Enter a valid localized description of more than 250 characters and below the advertised 10,000-character limit.
- Click Save draft and observe “Draft saved successfully”.
- Close the editor and reload the Store listings page.
- Observe that the language may still be marked Incomplete and its description is Empty.
- Repeat with multiple locales and observe that an earlier success notification can remain visible on the next locale page.
In one reproducible case, a Japanese description of 480 characters (approximately 1,246 UTF-8 bytes) did not persist. A shorter version of 330 characters (approximately 830 UTF-8 bytes) did persist. This suggests an undocumented byte-size limit, serialization issue, or backend validation failure.
Expected behavior
- “Draft saved successfully” should only appear after the server has persisted the description.
- Any payload or byte-size limit should be documented and validated before saving.
- A failed save should display a clear error.
- Notifications and form state should not carry over between locales.
- The listing row should reliably reflect the saved server state.
Additional observed problems
- The locale form sometimes took 10–15 seconds to become usable.
- Returning to the Store listings table sometimes took more than 20 seconds.
- Hidden or stale form elements remained present during navigation.
- An Action Center panel unexpectedly covered the listings table. Edit buttons remained visible and appeared enabled but did not respond.
- Browser console errors included
Failed to fetch. - Partner Center also logged a JSON parsing error resembling
Unexpected token ... PNG ... is not valid JSONwhile processing an extension logo duplicated across languages. - The mandatory certification-notes field only became visible after clicking Publish.
Impact
While preparing 51 localized listings, many descriptions had to be entered and saved repeatedly. This creates a serious risk of unknowingly submitting incomplete listings. All 51 languages were eventually completed only by shortening affected descriptions, waiting between operations, and verifying every row after a full reload.
Desktop
- OS: macOS
- Browser: Chromium-based desktop browser
- Partner Center date tested: 28 August 2026
- Extension package version: 1.23.0
Additional context
The extension was ultimately submitted successfully. This report concerns the reliability and validation of the Partner Center listing workflow, not the extension’s runtime behavior.
Activity
Rahul-Bauri commentedon Aug 31, 2026
Hi Dries De Schepper (@DriesDeSchepper)
Thank you for taking the time to report this issue and for providing such a detailed analysis of your findings.
We understand your concern regarding the Partner Center Store Listings workflow, where the "Draft saved successfully" notification is displayed even though the localized description is not persisted after reloading the page. We also appreciate the additional observations regarding save reliability, page performance delays, stale UI elements, console errors, and inconsistent validation behavior.
To help our engineering team investigate this issue further, could you please provide the following:
A HAR (network trace) file captured while reproducing the issue from start to finish, including the moment when Save draft reports success and the subsequent page reload where the description is missing. HAR traces are commonly used to identify failed API calls, validation errors, or backend responses that may not be visible in the UI.
A screen recording showing the complete reproduction flow, including:
Any relevant browser console logs/errors captured during reproduction, particularly the reported "Failed to fetch" and JSON parsing errors.
For the HAR capture, please start recording immediately before reproducing the issue and stop the capture once the failure is observed. This will help ensure the trace contains the relevant network activity needed for investigation.
Once we receive the requested information, we will review the data and coordinate with the appropriate team for further analysis.
Thank you for your cooperation, and we look forward to your response.
DriesDeSchepper commentedon Aug 31, 2026
Additional Partner Center UI inconsistency observed on August 31, 2026:
Expected: the visible completion indicator should always match the stored
Step Completedstatus.Actual: the underlying status is complete, but the green checkmark is missing or inconsistent. This does not currently block the live extension, but it creates uncertainty about whether the privacy submission was saved correctly.
I have omitted extension identifiers and personal information from this report.
DriesDeSchepper commentedon Aug 31, 2026
Hi Rahul,
Thank you for the response and for tracking the issue.
I cannot safely attach an unredacted HAR file to a public GitHub issue. A Partner Center trace may contain authentication cookies, tokens, account information, tenant data, and internal extension identifiers. If Microsoft requires a HAR, please provide a secure private upload channel and instructions for removing sensitive information.
The extension is now live and all localized listings were eventually saved after repeated attempts. Re-editing the production listing solely to reproduce the failure could affect live metadata, so I do not consider that a safe reproduction environment.
The engineering team should also be able to reproduce this independently using an internal test publisher account:
A second inconsistency is now documented as well: Partner Center reports
Privacy — Step Completed, while the visible green completion indicator can be missing.Please keep this issue open until the engineering team has reproduced or ruled out the persistence and status-synchronization problems. I am willing to provide additional sanitized evidence if the problem recurs and a private channel is available.
carlosjeurissen commentedon Sep 3, 2026
Rahul-Bauri I can confirm the process of adding localized listing descriptions is very unreliable on Partner Center, as mentioned in previous issues:
#397
#40
#293