search

NeverDecaf / chromium-web-store

Allows adding extensions from chrome web store on ungoogled-chromium. Also adds semi-automatic extension updating.
MIT License
2.3k stars 76 forks source link

Error: "All extensions are up to date!" / "CWS Extensions Update Failed" #152

Closed ylluminate closed 3 months ago

ylluminate commented 4 months ago

Just started seeing the following after updating some extensions today (restarting is not resolving the issue): image

I had updated three extensions, but a final one that said it needed to update had not yet been updated.

NeverDecaf commented 4 months ago

There should be error output in the console, right click the icon and select "inspect popup" to view it. If there isn't anything there then check the service worker by visiting chrome://extensions and clicking the Inspect views service worker link under the extension.

Gajus84 commented 4 months ago

Could be the newest Version of Privacy Badger that causes it (if you have it installed).

ylluminate commented 4 months ago

Wow, @Gajus84 is right. Disabling Privacy Badger caused it to work again.

graphixillusion commented 4 months ago

I confirm: disabling Privacy Badger it works again. Is there any way to make an exception to make it works without disabling it?

Gajus84 commented 4 months ago

PB had a bug fix update related to it's ability to read from the extension storage. I'm not to deep in how chromium-web-store works, but figured that this could be the reason for the CWS "fetch"-error.

util.js:308 Error updating extension [CWS Extensions]: TypeError: Failed to fetch at util.js:210:25 at new Promise (<anonymous>) at update_extension (util.js:209:28) at util.js:337:33 at Array.map (<anonymous>) at util.js:336:30

So I would wait for the PB update to land.

https://github.com/EFForg/privacybadger/releases/tag/release-2024.5.31

NeverDecaf commented 4 months ago

It appears that Privacy Badger is blocking the chrome update url (https://clients2.google.com/service/update2/crx) which will inevitably cause update checking to fail. I was able to "fix" this by going to Privacy Badger options => Tracking Domains and allowing google.com. This is obviously not ideal but adding clients2.google.com to Disabled Sites had no effect. (I don't use Privacy Badger myself so there may be some options I'm unaware of.)

ghostwords commented 4 months ago

Hello! Privacy Badger developer here. Privacy Badger for Chrome recently switched to Manifest V3 and Declarative Net Request for blocking and modifying requests. I believe this is the reason we are suddenly blocking requests that were not blocked before.

If that is the case, this isn't limited to Privacy Badger. Then, Ungoogled Chromium and other Chromium forks (?) have the same problem with any (MV3?) extension that uses DNR to block requests and is configured to block google.com.

NeverDecaf commented 4 months ago

Thanks for stopping by! I'll leave a comment on the Privacy Badger issue with this info as I think it makes more sense to discuss this there.

ghostwords commented 4 months ago

OK, I just added clients2.google.com to Privacy Badger's workaround list of domains that should be allowed to load (although w/o access to storage). This change will take up to 24 hours to propagate to all Privacy Badgers.

This should take care of the conflict between Privacy Badger and your extension, but I believe this conflict is only a small part of a larger new problem where Declarative Net Request content blockers in Chrome can now break other extensions.