-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The extension failed to load properly. It might not be able to intercept network requests. #109
Comments
I see this regularly when uBO Lite updates, and when looking into it the browser says "internal error" -- it appears the issue is in the browser's own API framework. Restarting the extension always solve the issue. Seems related: https://bugs.chromium.org/p/chromium/issues/detail?id=1271154#c127 |
What's your exact browser/version? |
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36 |
Yes, you are right. The error is gone. |
Hello, uBlock Origin friends! I know this issue is closed but I'm sharing this in case you find it interesting. 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:
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. Thanks! |
The ladder menu show an Error. Click into it open the Extension page with Ublock Origin Lite being reported as such.
The text was updated successfully, but these errors were encountered: