Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.

22,447 views
Skip to first unread message

Treesa P Poulose

unread,
Mar 7, 2023, 5:42:33 PM3/7/23
to Chromium Extensions
Getting this error while creating a chrome extension "Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist."

Simeon Velichkov

unread,
Mar 7, 2023, 7:20:31 PM3/7/23
to Chromium Extensions, Treesa P Poulose
That's basically mv3 for you, I know it's not a very useful answer, but that's what comes to mind when I see it.

wOxxOm

unread,
Mar 7, 2023, 7:57:35 PM3/7/23
to Chromium Extensions, Simeon Velichkov, Treesa P Poulose
This error has always been around and it's often caused by an architectural deficiency in Chrome - the lack of automatic re-injection of the content scripts in the currently open tabs after the extension is updated/installed/reloaded like Firefox does it. The solution for Chrome is to inject the scripts explicitly in chrome.runtime.onInstalled, see https://stackoverflow.com/q/10994324.

cue886

unread,
Mar 7, 2023, 8:55:33 PM3/7/23
to wOxxOm, Chromium Extensions, Simeon Velichkov, Treesa P Poulose



從我的 Samsung Galaxy 智慧型手機傳送。

-------- 原始訊息 --------
自: wOxxOm <wox...@gmail.com>
日期: 2023/3/8 03:57 (GMT+08:00)
至: Chromium Extensions <chromium-...@chromium.org>
副本: Simeon Velichkov <simeonv...@gmail.com>, Treesa P Poulose <treesapp...@gmail.com>
主旨: [crx] Re: Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/1c54ee1f-a413-4c42-9b4e-b73fc28477cen%40chromium.org.

Simeon Velichkov

unread,
Mar 8, 2023, 11:53:18 AM3/8/23
to Chromium Extensions, Simeon Velichkov, Treesa P Poulose, wOxxOm
I think that makes sense, I had a really bad day yesterday. I have an extension that calls the underlying service worker every second in some cases so that could explain why am I seeing it while developing and restarting the extension.

Viet Ta

unread,
Mar 8, 2023, 9:37:32 PM3/8/23
to Chromium Extensions, Simeon Velichkov, Treesa P Poulose, wOxxOm
Reply all
Reply to author
Forward
0 new messages