This (if completely correct) further compounds the (unknown) delay issue as those who try to get it installed and working are going to be removing/uninstalling it from avast, restarting avast/firefox and rebooting ,etc.
Which will further frustrate users, who no fault of their own in trying to get it to work, if it subsequently stops them ever installing it.
Totally bloody crazy.
I completely agree with you. What I’ve stated is correct and confirmed for Chrome, I’ll need to ask about Firefox to be 100% sure on that.
Well, the 12 hours delay is the decision of Avast.
Regarding AOS not installing on Chrome/Firefox after a user has removed/declined in past - we can’t really blame Avast. That’s a setting of the web browsers and that’s not under Avast control.
Well I really can’t say avast are blameless, if it is known to avast about uninstalling/rejecting the AOS extension. This would really impact beta testers who are frequently going to be running tests and may well uninstall many components.
This is the first time I have ever heard of this potential blockage if having declined or removed AOS and I have never experienced this issue. So why now is my question, what has changed.
I’ve had the AOS extension on Firefox since I installed the latest stable version of Avast on Feb. 7