7 ms·

Yes - see https://www.reddit.com/r/firefox/comments/bkcjoa/all_of_my_addons_got_disabled_and_they_are_all/ https://www.reddit.com/r/firefox/comments/bkcjoa/all_

Yes - see https://www.reddit.com/r/firefox/comments/bkcjoa/all_of_my_addons_got_disabled_and_they_are_all/ https://www.reddit.com/r/firefox/comments/bkcjoa/all_of_my_a... and https://www.reddit.com/r/firefox/comments/bk54mu/addonsextensions_broken/ https://www.reddit.com/r/firefox/comments/bk54mu/addonsexten... Cannot tell if it's related to https://www.reddit.com/r/firefox/comments/bjwz8n/addon_policy_and_process_updates/ https://www.reddit.com/r/firefox/comments/bjwz8n/addon_polic... (Says new Add-On Policy effective June 10th, 2019, so shouldn't be causing this. But...) As mentioned elsewhere, seems like when your clock hits 5/4 midnight UTC, you're done. I tried setting my clock in the past, but that did not fix the issue for me. (Clock was previously auto w/ daylight savings time enabled.) Super interesting to watch /r/firefox go from 3.8k active/online users to 5.6k over the past half hour... Edit: As mentioned below, there are GitHub/Bugzilla entries. They seem to be aware and starting to work towards a fix, though the explanation of the problem hasn't emerged yet. https://github.com/mozilla/addons/issues/978 https://github.com/mozilla/addons/issues/978

pedrocr 8y ago
The "fix" in the second link is amusing. The user had the clock wrong so the bug hit sooner. Adjusting the clock to the correct time "fixed" it but the issue is probably now back. Too bad there wasn't a root cause analysis of that failure. We wouldn't be having the widespread issue.
- dirtgrub 8y ago
  Somebody somewhere is going to feel silly and shamefully flip the 'more magic' switch back, or so I suspect. Clearly resetting your date is a "fix" in the temporal sense that it works until you apparently hit the magic deadline again, but I'm curious why this only hit one of my machines. Pretty sure I was running the same FF version on both, but not certain. Again wondering if it's due to a difference in the configs, since I've 'modified' those at different times with different lists of needless crap to disable.
KeenFox 8y ago
Over 10,000 now.

pedrocr 8y ago

The "fix" in the second link is amusing. The user had the clock wrong so the bug hit sooner. Adjusting the clock to the correct time "fixed" it but the issue is probably now back. Too bad there wasn't a root cause analysis of that failure. We wouldn't be having the widespread issue.

dirtgrub 8y ago
Somebody somewhere is going to feel silly and shamefully flip the 'more magic' switch back, or so I suspect. Clearly resetting your date is a "fix" in the temporal sense that it works until you apparently hit the magic deadline again, but I'm curious why this only hit one of my machines. Pretty sure I was running the same FF version on both, but not certain. Again wondering if it's due to a difference in the configs, since I've 'modified' those at different times with different lists of needless crap to disable.

KeenFox 8y ago

Over 10,000 now.