Skip to content
Discussion options

You must be logged in to vote

This issue typically occurs when the extension’s manifest.json uses hardcoded strings instead of i18n message references. Partner Center detects supported languages based on the message references used in the manifest—not just the presence of language folders.

When message references are missing, Partner Center assumes the extension supports only one default locale and ignores the others.

To ensure that all supported locales are detected:

Update your manifest.json file by replacing the name and description fields with i18n placeholders:

{
    "manifest_version": 3,
    "name": "__MSG_extensionName__",
    "description": "__MSG_extensionDescription__"
}

Include a default_locale in your ma…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by G-u-r-j-e-e-t
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
Partner Center Label to filter all items related to Partner Center FAQs Frequently asked questions along with answers to help Microsoft Edge Extension Developers Manifest Issues or questions related to manifest.json, schema, validation, or compliance, MV3 migration
1 participant