Could not establish connection. Receiving end does not exist.

[sesh92]

Two messages in inspector it looks like poor permissions in manifest
Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
index.html:1 Error handling response: TypeError: Cannot read properties of undefined (reading 'title') at chrome-extension://ifcfhbddddobmpgimkjjehbbdcbbefnk/static/js/main.js:1:2809

[faraazahmad]

Has anyone been able to resolve this?

[ZeroPie]

Tutorial and repo don't work @faraazahmad

[faraazahmad]

@ZeroPie I'd reached out to @bajcmartinez on Twitter and he was looking into the issue

[ZeroPie]

@faraazahmad
While the article was very informative, wasting time on broken examples is not cool:

Maybe give this a chance, it has also hot reloading for the extension out of the box.
https://github.com/lxieyang/chrome-extension-boilerplate-react

[bajcmartinez]

Hi all, sorry for the late response, I have been having some trouble reproducing the error, and I got also messages from other people that all works as expected. Could you please share some additional information, like browser and OS?

I've tried on both Linux and MacOS, using the latest version of Google Chrome without issues.

Thanks

[lenniecottrell]

The extension works fine for me on fresh pages - any tabs that were already open throw the error, but if the tabs are refreshed or new tabs are opened then it works fine.

Based on this thread I believe the issue here is just that the content script (DOMEvaluator.ts) isn't available on a stale tab, so the background process can't communicate with the content script.

[lenniecottrell]

@bajcmartinez this is a great little tutorial, but could definitely use a couple of updates for clarity! I am brand new to TS and didn't know I needed a types folder with .ts files in it, and I needed to downgrade react-scripts to 4.0.3 to get craco to work - it doesn't work with react-scripts 5.0

[mhlv]

Same issue wit me, MacOS, latest chrome

[AlanChen4]

I (Windows 10, Microsoft Edge) was able to fix this error doing the following:

• Going to extensions and disabling each extension one by one
• Restarting the browser
• Try the extension on a fresh tab, as suggested by @lenniecottrell