Bugzilla

This bug does not only happen when `mtime` is changed. It is also triggered when I use a profile from Firefox 66.0.3 (where the add-on was disabled by the signature bug) in Firefox Beta 64.

To reproduce, follow the STR, but run `fixtime.py` after the `faketime` command to fix up the profile.
And in the second Firefox run, force the signature verification check with `XPIDatabase.verifySignatures()`
Then finally start the profile with Firefox beta, and the add-on disappears from the profile, with the same stack trace.

`XPIDB_startup_load_reasons = [appChanged, directoryState, schemaChanged]`


This bug could affect more people than described in comment 9, but it is still **not a blocker for a dot release**.

This bug does not only happen when `mtime` is changed. It is also triggered when I use a profile from Firefox 66.0.3 (where the add-on was disabled by the signature bug) in Firefox Beta 67.0b14.

To reproduce, follow the STR, but run `fixtime.py` after the `faketime` command to fix up the profile.
And in the second Firefox run, force the signature verification check with `XPIDatabase.verifySignatures()`
Then finally start the profile with Firefox beta, and the add-on disappears from the profile, with the same stack trace.

`XPIDB_startup_load_reasons = [appChanged, directoryState, schemaChanged]`


This bug could affect more people than described in comment 9, but it is still **not a blocker for a dot release**.

EDIT: Disregard this comment. The issue described below is observed because there are two addon databases, and neglecting to update an add-on's `updateTime` in `extensions.json` to match the `mtime` [triggers](https://searchfox.org/mozilla-central/rev/06578bfadb5bdc5faee81f7e9b3c3fed21e616e0/toolkit/mozapps/extensions/internal/XPIDatabase.jsm#2687) the code path from comment 0. So comment 9 is still 100% accurate.


This bug does not only happen when `mtime` is changed. It is also triggered when I use a profile from Firefox 66.0.3 (where the add-on was disabled by the signature bug) in Firefox Beta 67.0b14.

To reproduce, follow the STR, but run `fixtime.py` after the `faketime` command to fix up the profile.
And in the second Firefox run, force the signature verification check with `XPIDatabase.verifySignatures()`
Then finally start the profile with Firefox beta, and the add-on disappears from the profile, with the same stack trace.

`XPIDB_startup_load_reasons = [appChanged, directoryState, schemaChanged]`


This bug could affect more people than described in comment 9, but it is still **not a blocker for a dot release**.