Version 1.6 not working for some Chrome users

[proginosko]

I've received some reports that version 1.6 is not working (at all!) for some Chrome users. I'm creating this issue as a central point for tracking the problem, collecting reports and further info, and generally trying to figure out what's going on.

Background: Version 1.6 updated LeechBlock to use Manifest V3. This was necessary because support for Manifest V2 will be phased out eventually. But it's likely that this update is behind the reported problem. It can probably be fixed, once I figure out exactly what's causing it. However, since I'm not able to reproduce the issue (LeechBlock is working fine on my system: Chrome 119.0.6045.200 on Windows 10) I'm relying on other users to provide information and to test some potential fixes.

If you're experiencing this problem, first make sure that you are using the latest version of Chrome. It is known that there have been problems with the implementation of Manifest V3 in earlier versions of Chrome.

If you're still experiencing the problem with the latest version of Chrome, please post an initial report here. Specify which OS you're using (Windows, MacOS, Linux, etc.). Also, please do the following:

• Go to the Extensions page in your Chrome browser: chrome://extensions
• Activate Developer mode.
• Click on "Details" under LeechBlock NG.
• Ensure that the option "Collect errors" is enabled.
• Click on the "service worker" link under "Inspect views".
• If you see any error messages in the DevTools console, post them here.

[proginosko]

If you need a temporary workaround, you can revert to an earlier version of LeechBlock (e.g., 1.5.8) by following these steps:

• Export your LeechBlock options to a file as a backup (Options > General > Export Options to File).
• Disable the LeechBlock extension on the Extensions page: chrome://extensions
• Locate and download the CRX file for the earlier version of LeechBlock (e.g., from this archive).
• Unzip the CRX file to a folder somewhere on your hard drive. (You might need to change the file extension from CRX to ZIP.)
• On the Extensions page, activate Developer mode, and click "Load unpacked" to load it as an unpacked extension from that folder.
• Import the options from your backup file.

[v-ko]

Interestingly the problem went away on my machine (I'd posted the bug above). I believe it wasn't even after a restart or update or anything. Now in the console i have just

background.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
background.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
background.js:1 Uncaught (in promise) Error: No tab with id: 0.
background.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
background.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
background.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
background.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.

for both the service worker and ticketer. Which is fine I guess, since the messages do not stack every second and the extension is working.

[smayer97]

Errors posted for #69.

[LtFrankDrebin]

Hello. I have the same issue as the posters above (on the latest Chrome version):

Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist. Context background.js Stack Trace background.js:0 (anonymous function)

It doesn't work in Incognito Mode either. In fact, none of the options function properly as activating the lockdown mode did nothing. Strangely enough, this happens only on my desktop computer with Windows 10. On my laptop with Windows 11, everything is normal, the extension blocks everything as it should.

[v-ko]

For me the problem went away on its own shortly (don't know what fixed it exactly). So maybe try some restarts (extension/bowser/computer), idk