Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Promise error The message port closed before a reponse was received

I've just started to get this error:

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

at chrome-extension://gppongmhjkpfnbhagpmjfkannfbllamg/js/browser-polyfill.js at this line:

const makeCallback = promise => {   return (...callbackArgs) => {     if (chrome.runtime.lastError) {       promise.reject(chrome.runtime.lastError); // uncaught in promise     } else if (callbackArgs.length === 1) {       promise.resolve(callbackArgs[0]);     } else {       promise.resolve(callbackArgs);     }   }; }; 

Do you know what can cause it?

Thanks

like image 906
Bomber Avatar asked Apr 01 '17 09:04

Bomber


People also ask

What is message port was closed before a response was received?

lasterror: the message port closed before a response was received error message can occur if there is any failure while communicating information (request and response) from background javascript and client script. You can see this error message in the browser's console window.

Why unchecked runtime lastError the message port closed before a response was received?

To Solve Unchecked runtime. lastError: The message port closed before a response was received Error This error Usually Occurs By various Chrome extensions so You Just need to disable all chrome extensions And then re-run your project and Your error will be solved.


2 Answers

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.

like image 115
PaladiN Avatar answered Oct 09 '22 16:10

PaladiN


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.
like image 26
jgpATs2w Avatar answered Oct 09 '22 18:10

jgpATs2w