Open ghost opened 1 year ago
@jslawler we currently only support this experimental extension in Chrome
happens on chrome too.
this issue happens when the extension is updated to a new version (tested on chrome and edge) restarting the browser fixes the error.
Disabling/enabling the extension also solves it. Saving closing the browser.
Hello, any news on this issue? Recently you started updating the extension more often, and it's quite annoying to see this error each time. Please can you raise the priority? Thanks.
I also see this in Chrome. It seems to only happen after a browser restart. It may indeed have to do with the extension updating.
It would be nice if it would just detect that it loaded improperly and reset itself.
There is a bug in chromium which they are trying to reproduce - https://issues.chromium.org/issues/40285683
Hello AdGuard friends!
At eyeo we've seen this error happening very consistently when updating an already running MV3 extension through the store. Especially when rules in rulesets have changed.
We've seen these two effects: 1) A big error in the user's browser that says an extension is faulty. A message saying "The extension failed to load properly. It might not be able to intercept network requests." on the MV3 extension. 2) We've also seen that calling updateEnabledRulesets results in "Internal Error" and no blocking.
We were able to recreate the problem using the Extension Update Testing Tool provided by Chrome Extensions DevRel team. I can definitely recommend trying it out if you haven't already!
The gist is that this issue will should be solved in Chrome 124 (stable mid April). If you've seen this happen before, you should see it fixed in Chrome Canary 125.0.6368.0 and Beta 124.0.6367.14.
See here for the fix.
On my end, Chromium 124 actually completely broken the extension; I went from a restart fixing the extension to it just never initializing successfully, even after full browser restart or disabling/enabling it. Reinstalling it completely did fix it, however, so if anyone here was already running into this issue and now can't get it to load at all, that might do the trick.
Worth noting at this point the MV3 extension is now integrated into the AdGuard Browser Extension making this essentially redundant.
Occasionally when I open MS Edge, I will get the error message on the AdGuard MV3 extensions saying "The extension failed to load properly. It might not be able to intercept network requests.".
The console logs are below, no errors or warnings were listed.
I do not know how to reproduce this.