[Microsoft Edge Extensions] Partner Center enrollment completely broken for 3+ weeks - "Accept and continue" button never submits due to JavaScript syntax error on the registration page

Tiago Henrique França Baroni 0 Pontos de reputação
2026-06-08T13:24:32.6733333+00:00

Summary

Developer registration for the Microsoft Edge Add-ons program has been completely broken for at least three weeks. The "Accept and continue" button on the enrollment page at partner.microsoft.com is permanently disabled and, even when manually enabled via DevTools, clicking it has no effect. New developer accounts cannot be created through any known workaround.

This issue is tracked in the official MicrosoftEdge-Extensions GitHub repository as Issue #566, where multiple independent developers from different countries have confirmed the same behavior.


Root cause (identified by the community)

Browser console output reveals a critical syntax error in the enrollment page's own JavaScript:


enrollnow?programName=msedgeaddons:121

Uncaught SyntaxError: Unexpected identifier 'ViewBage'

This appears to be a typo in the server-side rendered script (ViewBage instead of ViewBag), which crashes the entire JavaScript execution context on page load. As a result, the button's click handler is never registered — which is why enabling the button via DevTools still produces no effect.

Additional errors observed across Chrome, Edge, and Firefox:

  • ERR_CERT_DATE_INVALID on assets.onestore.ms (expired CDN certificate)
  • ERR_NAME_NOT_RESOLVED on jsll-4.3.1.js
  • Uncaught ReferenceError: define is not defined in common-nav.min.js
  • Multiple Invalid regular expression errors due to pattern attributes that are incompatible with Chromium's /v (unicode sets) regex flag, introduced in recent browser versions

Firefox independently confirms the same crash point:


Uncaught SyntaxError: missing ) in parenthetical at enrollnow:121:1101


Workarounds attempted (none successful)

  • Incognito/Private mode with all extensions disabled
  • Multiple browsers (Chrome, Edge, Firefox), devices, and network providers
  • Manually removing the disabled attribute from the button via DevTools
  • Removing all pattern attributes via MutationObserver in the console
  • Dispatching a submit event directly on the form (returns true but has no effect, as the form uses React-controlled components — FormData returns an empty object)

The issue is entirely server-side. There is no client-side fix available.


Current status

The bug was reported on May 7, 2026 (Issue #566). The Microsoft collaborator assigned to the issue (@Rahul-Bauri) acknowledged it and stated it had been forwarded to the engineering team. The last update from the team was on May 18, 2026 — three weeks ago — with no further communication since then, despite continued confirmations from new affected developers.


Impact

This regression is blocking all new developer onboarding to the Microsoft Edge Add-ons program globally. Developers and companies that have built extensions ready for publication cannot register, cannot publish, and have no workaround or estimated resolution date.

My specific situation: I am an independent developer with an extension already published on the Chrome Web Store, ready for submission to the Edge Add-ons store. I have been completely blocked from registering for over three weeks.


Request

Could the Microsoft Edge team please provide:

  1. Confirmation that the ViewBage syntax error on line 121 of the enrollment script has been identified internally as the root cause?
  2. A status update on whether a fix is currently in progress?
  3. An estimated deployment timeline for the patch?
  4. In the interim, is there any manual enrollment process or alternative onboarding path available for affected developers?

Thank you.

Microsoft Edge | Extensões do navegador | Windows 11
0 comentários Sem comentários

1 resposta

Classificar por: Mais útil
  1. Dio Xavier 298.3K Pontos de reputação Moderador Voluntário
    2026-06-08T22:16:06.3233333+00:00

    Olá

    Bem vindo á Comunidade Microsoft Edge.

    Em relação ao Bug, ele já foi escalonado, como nossos fóruns são voltados à questões técnicas, portanto é necessário aguardar uma solução pelo Equipe de enganharia da Microsoft. Caso ainda tenha questões sobre este problema é necessário abrir um ticket de suporte na página oficial do Desenvolvedor:

    https://developer.microsoft.com/pt-br/microsoft-edge/support?form=MA13LH

    Se a resposta tiver ajudado a resolver o problema, por gentileza marque-a como Resposta Útil. Essa ação encerra a thread, sinaliza a solução correta e ajuda outras pessoas com a mesma dúvida a encontrarem a resposta com mais facilidade. Caso ainda precise de suporte ou tenha novas perguntas, fique à vontade para utilizar este mesmo post.

    Esta resposta foi útil?

    0 comentários Sem comentários

Sua resposta

As respostas podem ser marcadas como ‘Aceitas’ pelo autor da pergunta e ‘Recomendadas’ pelos moderadores, o que ajuda os usuários a saber a resposta que resolveu o problema do autor.