1196797 - Staged extension installs are thrown away when upgrading to a version that requires signing

Status: RESOLVED FIXED

(Toolkit :: Add-ons Manager, defect, P4)

Description

[Dave Townsend [:mossop]]

1. Run Firefox 39 or 40 which don't require signing by default.
2. Install an extension that is unsigned and requires a restart to install, don't restart when told to.
3. Exit Firefox and start Firefox 41 or later which does require signing by default.

The staged extension install is thrown away as it doesn't meet the signing requirements of the new build. This is a little different to what happens to unsigned add-ons that are already installed, they are left in place and can be updated later to signed versions.

Comment 1

[Dave Townsend [:mossop]]

Kev, I'd like to hear your thoughts on priority here. It seems like it should be a rare case but it probably will hit some people. They won't get the extension they'd installed previously (rightly because it is unsigned) but then won't get a signed version automatically when it comes along. The problem is I think the code here is attempting to stop sideloads from slipping unsigned add-ons in so it might be tricky to fix safely.

Comment 2

[Andy McKay]

It sounds like we might a little late to address this now?

Comment 3

[Andy McKay]

Based on the fact that we are about to release 44, I think we are too late to do anything here. Please re-open if I'm wrong.