[Bug - Edge Addons] Unable to add language on store listing to have description on more than 1 language

[mailinblack-app]

Describe the bug I'm unable to add language on Store Listing to have more than 1 language although 6 languages are detected on package.

To Reproduce Steps to reproduce the behavior:

1. Go to "Store Listings"
2. Try to click on "Add a language"
3. It's disabled

Expected behavior Being able to add language on store listing to have description on 6 languages.

Screenshots

Desktop (please complete the following information):

• OS: Mac OS X
• Browser chrome and firefox
• Version firefox 127 / chrome 126

[ManikanthMSFT]

Hi @mailinblack-app

Thank you for reporting this. We are looking into this and will let you know as soon as we have an update.

[ghost]

Hi @mailinblack-app

Thank you for reporting this. We are looking into this and will let you know as soon as we have an update.

@ManikanthMSFT Any updates? It's been a couple months with no update so far. We're running into the same issue where the dropdown list is disabled but the package mentions mentions 6 languages, similar to @mailinblack-app's situation.

We've published our extension in both Chrome and Firefox stores and have no issues with localization.

Do we need to include the languages in the manifest.json file? We have only included the default_locale. The languages are added to the _locales folder as described in the i18n API documentation.

Thanks in advance :)

[ManikanthMSFT]

Hi @sjoerdspindle, thank you for your patience.

Our engineering team has confirmed that when a package contains multiple languages, the Listing page will automatically populate those languages. The “Add a language” button is intentionally disabled to prevent unnecessary additions. It will only become active if a language is deleted from the UI and needs to be added back.

Please let us know if you have any further questions or need additional assistance.

[ghost]

Hi @sjoerdspindle, thank you for your patience.

Our engineering team has confirmed that when a package contains multiple languages, the Listing page will automatically populate those languages. The “Add a language” button is intentionally disabled to prevent unnecessary additions. It will only become active if a language is deleted from the UI and needs to be added back.

Please let us know if you have any further questions or need additional assistance.

Thank you for getting back to me! I'm afraid my issue/bug report was misunderstood. I'm unable to change/update the extension name and description. We want to translate and localize the description for each language/country.

Please see the attached screenshots below. On the Packages page it mentions the languages as expected ("Languages in package: German, English, Spanish, French, Dutch, Portuguese (Portugal)"), but on the Listings page I am unable to change the description, nor does the dropdown menu to Add a language become available.

And yes, we did set a default_locale in the manifest.

I hope you can help out.

[ManikanthMSFT]

Hi @sjoerdspindle, thank you for your detailed response and the screenshots. I apologize for any misunderstanding.

To clarify, you are trying to update the extension name and description for each language/country on the Listings page, but you are unable to do so. Although the languages are correctly listed on the Packages page and you have set a default_locale in the manifest, the dropdown menu to add a language is not available, and you cannot change the description.

I will relay this information to our engineering team to investigate further. We appreciate your patience and will get back to you as soon as we have more information.

Thank you for your understanding.

[ghost]

Hi @sjoerdspindle, thank you for your detailed response and the screenshots. I apologize for any misunderstanding.

To clarify, you are trying to update the extension name and description for each language/country on the Listings page, but you are unable to do so. Although the languages are correctly listed on the Packages page and you have set a default_locale in the manifest, the dropdown menu to add a language is not available, and you cannot change the description.

I will relay this information to our engineering team to investigate further. We appreciate your patience and will get back to you as soon as we have more information.

Thank you for your understanding.

Indeed, your summary is totally correct. A couple weeks ago it did show the default_locale (which is Dutch in our case) and the description, but the other languages were not available or selectable. Now even Dutch, our default_locale, is not even visible.

We do use the Publish API to update packages, but even when I add the package as a .zip-file manually they are still not selectable unfortunately.

[ManikanthMSFT]

Hi @sjoerdspindle, could you please help us with your product ID and if possible, could you share us the package that you are facing issues with?

[ManikanthMSFT]

@sjoerdspindle, could you please provide us with your product ID? Additionally, if possible, could you share the package you are experiencing issues with?

Thank you for your cooperation.

[carlosjeurissen]

@sjoerdspindle from my experience, they will only show up when messages used in the manifest.json file show up in the specific messages.json files. They don't have to be different from your default_locale. However they need to be specified to be picked up by the Microsoft Edge Store.

[ManikanthMSFT]

@sjoerdspindle, we got an update from our team advising to follow the below doc for localization. Localization message formats | Chrome Extensions | Chrome for Developers

[carlosjeurissen]

@ManikanthMSFT Does Microsoft want to reconsider their current approach? Especially for webExtensions with partially translated languages (which is what most of us deal with), the current setup is problematic.

For some of the webExtensions, some messages from message.json have to be removed to prevent the Edge store from picking up the locale and force to include a full store description for that specific locale. Dropping this requirement and allow a fallback to the default_locale would be very welcome. As would be the edge store actually looking for the list of locales in _locale files instead of just relying on the manifest.json.

[ManikanthMSFT]

Hi @carlosjeurissen, we are currently reviewing this, and we will get back to you with an update.

[ManikanthMSFT]

Hi @carlosjeurissen,

@ManikanthMSFT Does Microsoft want to reconsider their current approach? Especially for webExtensions with partially translated languages (which is what most of us deal with), the current setup is problematic.

For some of the webExtensions, some messages from message.json have to be removed to prevent the Edge store from picking up the locale and force to include a full store description for that specific locale. Dropping this requirement and allow a fallback to the default_locale would be very welcome. As would be the edge store actually looking for the list of locales in _locale files instead of just relying on the manifest.json.

Hi @carlosjeurissen, could you please elaborate on this query a bit so that we can assist you better.

[carlosjeurissen]

@ManikanthMSFT As far as I know the Partner Center uses the i18n message ids from the manifest.json to determine which languages to include for your extensions listing. It will check if the message.json files include those messages. If non are found, the language is skipped. Thus the workaround for extensions is to remove those message ids in the message.json in case they do not have enough information for the extension listing. This is very counter intuitive. Having those messages translated is valuable even without a store description.

[ManikanthMSFT]

Hi @carlosjeurissen, thank you for providing additional details regarding the issues you're facing with the current locale handling approach for Microsoft Edge extensions.

We understand that the current setup, which requires removing certain message IDs from the message.json files to prevent incomplete locales from being picked up, is counterintuitive and problematic. Your suggestion to allow a fallback to the default_locale and for the Edge store to look for locales in the _locale files instead of just relying on the manifest.json is valuable.

We will forward your feedback to the relevant team for consideration. In the meantime, if you have any further questions or need additional assistance, please do not hesitate to reach out.

Thank you for your patience and understanding.

[carlosjeurissen]

@ManikanthMSFT Just to clarify. With the fallback to default_locale, I am referring to the extension store description.

[purplestone]

Hi @ManikanthMSFT :

Hi @sjoerdspindle, thank you for your detailed response and the screenshots. I apologize for any misunderstanding.

To clarify, you are trying to update the extension name and description for each language/country on the Listings page, but you are unable to do so. Although the languages are correctly listed on the Packages page and you have set a default_locale in the manifest, the dropdown menu to add a language is not available, and you cannot change the description.

I will relay this information to our engineering team to investigate further. We appreciate your patience and will get back to you as soon as we have more information.

Thank you for your understanding.

What is the current progress on fixing this bug? This is a long-standing and very critical bug that has been preventing me from adding multi-language listing pages.

Let me describe the specific details of this bug again:

On the page partner.microsoft.com/dashboard/microsoftedge/packages, after uploading the extension package, it successfully shows that multiple languages are recognized in the package (as seen in the provided screenshot 1 of mailinblack-app, where 6 languages were detected in the extension package).

Screenshots1 packages page

However, when navigating to partner.microsoft.com/dashboard/microsoftedge/listings, the dropdown button 【Add a language】 at the top is unresponsive,(There was no response when the button was clicked) making it impossible to add listing content for each of the 6 recognized languages.

Screenshots2 listings page

======

Expected:
There should be a way to create a details page for each of the recognized languages.

Current issue: Microsoft Partner Center detects the multiple languages in the extension package but does not allow adding listing content for each language.

====== Given the severity and long-standing nature of this bug, please expedite its resolution.

Thank you for your attention and response.

[purplestone]

@ManikanthMSFT And I think this bug belongs to the partner.microsoft.com/dashboard/microsoftedge platform, not an issue with 【Edge Addons】 development techniques, Labels to【 Partner Center】

[venkatasai5171]

Hello,

I'm Venkat from the Microsoft Extension Developer Support team.

Thank you for your suggestion regarding adding descriptions for all languages at once. Currently, we have a backlog for implementing this feature, but we truly appreciate your feedback and have noted it for future improvements.

As of now, we are proceeding to close this issue. If you encounter any further concerns or need assistance, please feel free to reach out or raise a new issue.

Best regards, Venkat