Trying to develop, but add-on disabled when running jpm

Add-ons
1

Hi there apologies if this has been addressed before - if so - please just point me to the right docs.

I’m developing an add-on - and development has gone well for the last year or so - but I started working on it again after a bit of a break, and when I’m doing “jpm run” to test and debug the add-on, it’s not working. When I access the add-ons/Extensions section, FF is informing me that the add-on could not be verified for use in FF Developer (I’m using that) - and the add-on has been disabled.

I’ve seen documentation about signing - and this makes sense for generating the xpi, but what do I have to do to get my add-on to work when developing?

Is it still expected that I have to do signing for development? I ran jpm sign - using details of a key I created. I’m not sure whether it worked completely, not being familiar with the process.

Any advice, links or info on how to get things up and running so I can develop some tweaks to my add-on would really, really be appreciated.

Thank you for your time
Ryan

2

What version of Firefox are you running? If Fx 44 then you need to disable the preference xpinstall.signatures.required, need to set it to false.

In Fx45+ it should be loaded as a temporary addon, heres more info - https://blog.mozilla.org/addons/2015/12/23/loading-temporary-add-ons/

However if its not then you can sign it with jpm sign before testing - https://blog.mozilla.org/addons/2015/12/18/signing-firefox-add-ons-with-jpm-sign/

If you want to use jpm sign, make sure you use a fake id on your addon, otherwise it will use your actual id, and it will get it signed as an “Unlisted” addon. That will cause problems when it comes time for you to upload your addon as a “Listed” addon.

1 Like