If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Installing new version of XPI from same location doesn't install properly

NEW
Unassigned

Status

()

Toolkit
Add-ons Manager
P3
normal
4 months ago
4 months ago

People

(Reporter: mkaply, Unassigned, Mentored)

Tracking

({good-first-bug})

Trunk
good-first-bug
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: triaged)

(Reporter)

Description

4 months ago
It appears that some sort of aggressive caching is keeping XPI files from being installed even if the file contents are changed.

To reproduce:

Set xpinstall.signatures.required to false.

Create a XPI file with a basic manifest.json:

{
    "manifest_version": 2,
    "name": "Test",
    "version": "0.1",
    "chrome_settings_overrides": {
        "homepage": "https://mike.kaply.com"
    },
   "applications": {
       "gecko": {
           "id": "test@kaply.com"
       }
   }
}

Zip the file into a XPI "test.xpi" and install it into Firefox

Go to about:addons and verify that it is installed.

Bump the version to 0.2 and then rezip the XPI file. Install again.

After install, go to about:addons.

The version is still 0.1.

If you move the XPI file to a different physical location on disk, it installs properly.

Comment 1

4 months ago
This sounds like a relatively simple matter of flushing the zip reader cache after completing an install from a local file (and adding an appropriate test of course)
Mentor: aswan@mozilla.com
Keywords: good-first-bug

Updated

4 months ago
Priority: -- → P3
Whiteboard: triaged
You need to log in before you can comment on or make changes to this bug.