claude-code - 💡(How to fix) Fix Extension v1.0.69 (clean install on fresh Chrome profile). Service worker console errors [1 comments, 2 participants]

mcpPermissions-BSnCI2j1.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist. After full extension reinstall + Chrome force-quit, only Debugger is not attached remains. After full Chrome uninstall + profile reset (mv ~/Library/Application\ Support/Google/Chrome ...backup) + fresh Chrome install + fresh extension install + Claude account sign-in, same Debugger is not attached error persists.

TL;DR

The issue is likely related to a permission or connection problem between the Chrome extension and the service worker, and a potential workaround could involve re-examining the extension's permission settings and the Approved Sites list.

Guidance

• Verify that the extension's permission state is correctly set to "On all sites" and that the Approved Sites list is properly configured, as the issue might be related to permission inconsistencies.
• Check if the chrome:// URL access error is related to the extension's functionality and if there are any specific requirements for accessing these URLs.
• Investigate the "Debugger is not attached" error, as it might be a red herring or a symptom of a deeper issue with the extension's communication with the service worker.
• Test the extension on a different Chrome profile or a different machine to rule out any environment-specific issues.

Example

No code snippet is provided as the issue seems to be related to the extension's configuration and permissions rather than a specific code problem.

Notes

The issue seems to be specific to the Chrome extension and its interaction with the service worker, and the fact that it persists after a full reinstall and profile reset suggests that it might be a problem with the extension itself rather than a user-side issue.

Recommendation

Apply workaround: Re-examine the extension's permission settings and the Approved Sites list to ensure that they are correctly configured, and test the extension on a different Chrome profile or machine to rule out any environment-specific issues. This is recommended because the issue seems to be related to the extension's configuration and permissions, and a workaround might be possible without requiring an upgrade to a fixed version.