Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Unable to deploy signed addons

  • 1 Mbohovái
  • 1 oguereko ko apañuái
  • 1 Hecha
  • Mbohovái ipaháva cor-el

more options

Hello,

I'm having the exact same situation as https://discourse.mozilla-community.org/t/unable-to-deploy-signed-add-ons-to-firefox-52-0-2-on-macos/14820, but on Windows systems. I have unpacked the .xpi file and distributed it using our Enterprise tool with activation of the extension through registry values. The extension seems to register well, but won't be activated / enable due to signature verification issues. When I install this extension manually using the same .xpi file (drag and drop), the extension gets activated, but of course is only installed and activated for that particular user. We are using the "release" update channel of Mozilla Firefox.

Please help!

Hello, I'm having the exact same situation as https://discourse.mozilla-community.org/t/unable-to-deploy-signed-add-ons-to-firefox-52-0-2-on-macos/14820, but on Windows systems. I have unpacked the .xpi file and distributed it using our Enterprise tool with activation of the extension through registry values. The extension seems to register well, but won't be activated / enable due to signature verification issues. When I install this extension manually using the same .xpi file (drag and drop), the extension gets activated, but of course is only installed and activated for that particular user. We are using the "release" update channel of Mozilla Firefox. Please help!

Opaite Mbohovái (1)

more options