Closed Osmose closed 8 years ago
I claim unbranded 48 should work.
npm install -g get-firefox
get-firefox -cb unbranded-release
This is also working for me, using this unbranded build, which came from https://wiki.mozilla.org/Add-ons/Extension_Signing
Closing since we can't seem to reproduce.
Weird, Benton was able to reproduce the issue as well when I first noticed it.
I have since discovered that my unbranded copy of Firefox was replaced by a branded copy of Firefox, potentially due to this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1290548
Either way, I re-downloaded a new unbranded copy and things worked fine. Sorry for the confusion!
I have the same problem with Firefox 49.0.1, before the update everything worked fine. How can overcome this issue?
I am having the same problem in Firefox 49.0.1, and previous add-on worked fine. Any ideas will be appreciated.
@Christos-Papoulas @sentryone: Since upgrades from unbranded versions of Firefox 48 to 49 for a while was converting them to branded versions, can you try and download a fresh, unbranded version of Firefox from here and trying again?
Actually just got a tip from someone and if I downloaded Firefox Nightly it worked:
jpm run -b Nightly
Thank you for your input!
Thank "mythmon"
jpm -b "C:\Program Files (x86)\Mozilla Developer Preview\firefox.exe" run
I cannot test the add-on via
jpm run
on Firefox 48, branded or unbranded. Firefox launches with the following error: