1192438 - Signed Extension installed via external installer is disabled.

Status: RESOLVED INVALID

(Toolkit :: Add-ons Manager, defect)

Description

[badkins79]

User Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Firefox/31.0 Iceweasel/31.8.0
Build ID: 20150702233255

Steps to reproduce:

In Nightly as of Aug 5, 2015:

I have a signed extension. My extension is installed via its own installer (MSI). After installation, I start Nightly, but my extension is not active. 


Actual results:

If I look at the Add-ons, my extension is listed. It does NOT complain about my signature. My extension shows up as "(Disabled)", but there is no enable button. Also, when I start Nightly immeditately after the install, it does NOT show the page about the new extension to allow me to "Allow this installation".


Expected results:

After I install my extension via the MSI, and then starting Nightly, I should see a page alerting me about the new extension, and it should ask me if I want to allow it. After allowing it, it would make me restart, and then my extension should be active.

Comment 1

[badkins79]

Additional debugging details. I have found that if I then update the filetime of my extensions install.rdf file, the add-ons page will then have the button to Enable the extension. Clicking it does not ask me to restart though. It just makes the button disappear. If I restart manually, the extension finally gets activated.

However, if I run the installer, then update the filetime of install.rdf, and then start Nightly for the first time, it behaves as in the problem description. No Enable button.

Comment 2

[Dave Townsend [:mossop]]

I'll take a look at this. It might help if you could send me a copy of the extension in question, we have tests verifying that this should be working so it might be something specific to your add-on that is tripping us up.

Comment 3

[badkins79]

(In reply to Dave Townsend [:mossop] from comment #2)
> I'll take a look at this. It might help if you could send me a copy of the
> extension in question, we have tests verifying that this should be working
> so it might be something specific to your add-on that is tripping us up.

I'd be happy to. Is there a way to send a file privately to you. Also, note that it will be an MSI file, not an xpi.

Some extra details from my testing:
If I install the extension using the .xpi that was sent to me after it got signed, it works correctly. 

Also, if I disable the add-on signature enforcement, it will also work correctly.

Comment 4

[Dave Townsend [:mossop]]

(In reply to badkins79 from comment #3)
> (In reply to Dave Townsend [:mossop] from comment #2)
> > I'll take a look at this. It might help if you could send me a copy of the
> > extension in question, we have tests verifying that this should be working
> > so it might be something specific to your add-on that is tripping us up.
> 
> I'd be happy to. Is there a way to send a file privately to you. Also, note
> that it will be an MSI file, not an xpi.

My email address works

Comment 5

[badkins79]

(In reply to Dave Townsend [:mossop] from comment #4)
> (In reply to badkins79 from comment #3)
> > (In reply to Dave Townsend [:mossop] from comment #2)
> > > I'll take a look at this. It might help if you could send me a copy of the
> > > extension in question, we have tests verifying that this should be working
> > > so it might be something specific to your add-on that is tripping us up.
> > 
> > I'd be happy to. Is there a way to send a file privately to you. Also, note
> > that it will be an MSI file, not an xpi.
> 
> My email address works

Ok, I sent you an link. I should have said that this extension is not e10s compatible yet, so be sure to disable that before installing.

Comment 6

[Dave Townsend [:mossop]]

The problem is that the extension is only preliminarily reviewed. Sideloading requires the extension to be fully reviewed. You'll need to get the AMO folks to do a full review of your extension.