Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unchecked runtime.lastError: Could not establish connection #6817

Closed
travisdmathis opened this issue Jul 6, 2019 · 6 comments
Closed

Unchecked runtime.lastError: Could not establish connection #6817

travisdmathis opened this issue Jul 6, 2019 · 6 comments

Comments

@travisdmathis
Copy link

travisdmathis commented Jul 6, 2019

Describe the bug
A clear and concise description of what the bug is.

When a dapp is open in a tab and user closes the browser and later reopens it, when the tab is reopened metamask fails to connect to the browser.

Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
contentscript.js:1 MetamaskContentscript - lost connection to MetaMask Background Multiplex
H @ contentscript.js:1
contentscript.js:1 MetamaskContentscript - lost connection to MetaMask muxed traffic for channel "provider" failed.
H @ contentscript.js:1
contentscript.js:1 MetamaskContentscript - lost connection to MetaMask muxed traffic for channel "publicConfig" failed.

To Reproduce
Steps to reproduce the behavior:

  1. Open a dapp enabled website and login / connect
  2. close the browser completely
  3. reopen it and browse to your console on the tab connected to a web3 page.

Expected behavior
A clear description of what you expected to happen.

metamask to work w/o refreshing the page

Screenshots
If applicable, add screenshots to help explain your problem.
metamaskerrors

Browser details (please complete the following information):

  • Brave Version 0.61.52 Chromium: 73.0.3683.86 (Official Build) (64-bit)
  • MetaMask 6.7.2

Additional context
Add any other context about the problem here.

@tjayrush
Copy link

I'm seeing this same issue under

Google Chrome
Version 80.0.3987.100 (Official Build) (64-bit)

@tmashuang
Copy link
Contributor

Closing due to inability reproduce behavior on Chrome and Brave. I was unable to access the dapp in the screen capture due to my region, but I used a few other ones without issues, Idex/CryptoKitties/etc. There must be something specific to reproduce the issue that I am missing. Please fill out the reproduction steps thoroughly in a new issue.

@jamesmorgan
Copy link

I have also seen this issue occurring in Chrome, Windows. Not sure on how to reproduce it tbh but I see this for some web3 contract calls. Unchecked runtime.lastError: The message port closed before a response was received.

@cliffhall
Copy link

One of our users is seeing this issue as well:
metamask-issue

@TimDaub
Copy link

TimDaub commented Jun 24, 2021

I've seen this as part of #9196

@Mattijah
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants