Firefox 43 now enforces add-on signing. I don't understand how one is to test and debug an extension in these versions of Firefox prior to having the extension signed.
If I'm writing a new extension, how do I go about testing the unsigned version in the latest versions of Firefox? Is there an explicit way to disable the signing enforcement for developers?
Define 'latest version'?
xpinstall.signatures.required
to false in about:config
about:debugging
xpinstall.signatures.required
is removed. Mozilla was supposed to release an unofficial 'unbranded' versions that still has this preference but it does not seem like this is actually happening.
My suggestion:
xpinstall.signatures.required
;If it's with addon sdk, there is a jpm sign
command. There is also a signing API - http://olympia.readthedocs.org/en/latest/topics/api/signing.html
jpm sign --api-key KEY --api-secret SECRET
command. This will
create a signed xpi and upload it to AMO as an "unlisted" extension.
Then you'll find a ****.xpi
file in the current
directory. FF 43+
will allow it to be installed.To test it, you'll have to rely on dev/nightly channels. The unbranded builds I haven't seen yet. There is an ongoing discussion on how people can actually test their addon which has a bug in say release/beta channel, on the release/beta channel.
Also dogfooding typically is done by other users on release/beta channels. So its an ongoing discussion, but for dogfooding they recommend the jpm sign
or the signing api.
A possible useful topic - https://github.com/diegocr/GitHubExtIns/issues/19
This blog has all we need to know on jpm sign - https://blog.mozilla.org/addons/2015/12/18/signing-firefox-add-ons-with-jpm-sign/
With Firefox 48 Mozilla introduced "Unbranded Builds" which allow you to install unsigned extensions. See this blog post or download them directly at Add-ons/Extension Signing Wiki page.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With