Installing unsigned/unverified add-ons from file in Nightly 43 *fails*

Add-ons addons.mozilla.org
#1

Hi there,

Mozilla has said that it will ban installation of unsigned add-ons in release versions of new browsers, but not in Nightly.

However, when I choose “Install Add-on From File…” in Nightly (43a1), I get “This add-on could not be installed because it has not been verified” error.

But of course this add-on is not verified (nor signed) – this is a new version of my add-on (which is verified and signed), but I work on it locally, and there has to be way for me to install new test version of my extension.

How do I force Nightly to accept test version of my extension?

#2

https://wiki.mozilla.org/Addons/Extension_Signing

#3

Thanks, Andreas, but I have read that article before and I know that there is a way to upload and sign an extension to AMO without making it public.

My question was different: why, despite Mozilla’s claims, Nightly (43a1) does not allow installation of unsigned extensions?

Uploading and signing every little change is not a viable solution for me; I want exactly local installation of unsigned/unverified extensions.

You are saying that Mozilla took back its claim that Nightly builds allow installation of unsigned extensions, and now it is impossible?

I could not find such announcement, though.

#4

That page explains how to enable unsigned add-ons in Nightly and Developer Edition.

#5

It does not, this is why I had to ask here.

It says “Firefox will have a setting to disable signature enforcement” – but there is no mention of this setting. Future tense (“will”) might mean that it did not exist – at least yet – at the time of the writing of that article.

If the promised future has already came, then where is this option, how it is activated?

Thanks in advance.

#6

Weird, I can see it just fine on that page.

#7

And what do you see? Where?

#8

See the Timeline section…

1 Like
#9

Thanks; truly weird place for option that is promised (but not named) in future tense in the part that is actually related to the matter.

#10

I’m pretty sure you need to set this option in about:config

xpinstall.signatures.required

@TheOne
I don’t know if you can edit that page.
But the setting probably should be mentioned in the FAQ’s

1 Like
#11

Agree with Martin; current writing makes no sense.

Andreas, could you please update that article?