Closed Bug 610740 Opened 14 years ago Closed 6 years ago

If an app-bundled extension gets new compatibility info and not a new version with an application upgrade and we also perform a DB schema update then the updated compatibility info is lost

Categories

(Toolkit :: Add-ons Manager, defect)

Product:
Toolkit
Component:
Add-ons Manager
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INACTIVE

People

(Reporter: mossop, Unassigned)

References

Details

If an application version 1 ships extension foo with compatibility range 1-1 and then application version 2 ships extension foo with compatibility range 1-2 without changing foo's version, and if the application upgrade requires a DB schema update for extensions.sqlite then the new compatibility range will not be applied, instead the old range will be migrated to the new database.
FYI, discovered while running update checks for 4.0b7 on betatest channel.  This was mostly reproducible with 4.0b5->4.0b7 updates on WinXP.
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.