I'm locking this like I did in #851 because no new information is being added. We're aware and we're working on it.

[ethanhines]

I'm locking this like I did in #851 because no new information is being added. We're aware and we're working on it.
THIS IS A REALTIME 0 DAY BUG IN FIREFOX 66.0.3 RIGHT NOW AND you have the odcity to lock the thread because it was considered "SPAM"??. I demand the thread be reopened immediately!

#978

[ethanhines]

There's literally thousands of people freaking out right now on Reddit https://www.reddit.com/r/firefox/comments/bkfg00/also_had_all_my_addons_disabled_and_cant/?sort=new because all their addons have been disabled and the work around is to manually set the pc clock back two days!

[caitmuenster]

Hey there! We totally understand the concern. We don't really use Github for providing updates for this -- want to follow this thread over on our forums instead? https://discourse.mozilla.org/t/certificate-issue-causing-add-ons-to-be-disabled-or-fail-to-install/39047

[budlight]

Doubling down on mistakes by locking threads related to this, why piss off pissed of people more. Just leave them open for a few days and respond to them all with how to fix the issue. Its not like you are going to clear out all the open issues anytime soon, esp with this going on.

[Straborvsky]

Yeah, with so much confusion many people probably going to ask many things like me.
"When we able to expect the updates for the issues?"
"Do you have temporary solution like additional/changes script in Firefox config?"
"What exactly going on here?"
Because we common folks know nothing about script or programs, we trust our back to you but at least we want some problem clarification or what should we do right now!?
Thanks, and God speed developer!

[caitmuenster]

Yep I'll be leaving all of these threads open throughout the weekend so folks can ask questions. I agree that it can be tough to find information and I want to make sure folks are able to find out what's going on.

[AdrianoCahete]

Please, pin one issue (#978 ?) with Firefox team response.

[russmac]

Glad this isn't locked.

Because all my extensions are working in for one user / mozilla profile in Ubuntu 19.04 in Firefox Quantum.

The same user / different mozilla profile that Firefox developer uses , has the extensions gone. (without the warning messages)

This is distinctly different from my other user and Firefox profiles, Where the warning displaying the reason why the extensions are disabled is visible. In both Dev/Quantum. The only obvious answer is a bug in this profile has broken extension verification or some legacy setting has it disabled.

*Well according to the post below: https://github.com/mozilla/addons/issues#issuecomment-489316896, One profile must of had the automagic update.

[willdurand]

We've published a hotfix, it can take up to 6h to get installed but it should be automatic and should fix everything :)

[reloxx13]

what is "Normandy" ???

[reloxx13]

PS: locking = x new issues
not locking = spam but only in one issue...
clean up the issue list if its fixed not now.

use github pin feature.

[willdurand]

what is "Normandy" ???

This is a FF feature that allows to deploy simple changes to all users on the fly

[reloxx13]

disabled by default so this fix is useless?

[grahamperrin]

… what is "Normandy" ?

https://www.reddit.com/comments/bkjrst/-/emh62h8/?context=1 ▶ Firefox/Normandy/PreferenceRollout - MozillaWiki

[Enerccio]

Why isn't there MANUAL OVERRIDE IN NON DEV VERSION OF FIREFOX?! Give power user a way to override your mistakes ffs without forcing dev version.

[diox]

From discourse:

We rolled-out a fix for release, beta and nightly users on Desktop. The fix will be automatically applied in the background within the next few hours, you don’t need to take active steps.

In order to be able to provide this fix on short notice, we are using the Studies system. You can check if you have studies enabled by going to Firefox Preferences -> Privacy & Security -> Allow Firefox to install and run studies.

You can disable studies again after your add-ons have been re-enabled.

We are working on a general fix that doesn’t need to rely on this and will keep you updated.