Promise error The message port closed before a reponse was received

Question

I\'ve just started to get this error:

Uncaught (in promise) Objectmessage: \"The message port closed before a reponse was received.\"

at chrome-exte

Answer 1

this Helps me to overcome with this error by removing the Selenium (Chrome Extension)

Promise error:

The message port closed before a response was received

because you have installed Selenium (Chrome Extension)

Answer 2

Mine was due to the Google Publisher Toolbar extension. Disabled that and the error went away.

Answer 3

Using Chrome ^71.0 and this issue pops in multiple extensions. I comprised a list that caused trouble for me + all other reporters in this thread:

• Katalon Recorder
• PictureMate
• Pinterest Save Button
• Wappalyzer

Answer 4

If you are using live-server to auto refresh the browser, then this error was coming up. I stopped the live-server and then opened the index.html file on browser this error didn't come up.

Answer 5

Update:

As of the comment by morficus, the problem has been fixed in the version: 4.0.1

The plugin will auto-update or you could reinstall from here:

https://chrome.google.com/webstore/detail/wappalyzer/gppongmhjkpfnbhagpmjfkannfbllamg

If anyone is interested in the issue the pull request is here:

https://github.com/AliasIO/Wappalyzer/pull/1491

2019 Edit:

If that is not solving your issue. You could try disabling all the chrome extensions and check if that solve your issue.

To disable you could type the below code in chrome url:

chrome://extensions/

or could go on

Settings > Extensions

After that you could enable each extensions and check the culprit.

Older issue:

It is not the chrome's bug but the bug with the wappalyzer extension.

I am not sure you are using it but i have used it and was just updated and got the same issue.

Here is the proof of the issue:

https://github.com/AliasIO/Wappalyzer/issues/1487

We need to wait until there is any solution for the extension or use the older version of the extension until it gets resolved.

Answer 6

In my case was due to the extension 'Katalon recorder'. Probably the most generalistic solution is:

• Disable all all extensions in chrome://extensions
• Enable extensions one by one to detect which one is presenting de issue.