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.

Sign up for GitHub

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

Jump to bottom

[Bug]: MV3: "Could not establish connection. Receiving end does not exist." error #15970

Closed
digiwand opened this issue Sep 26, 2022 · 3 comments
Closed

[Bug]: MV3: "Could not establish connection. Receiving end does not exist." error #15970

digiwand opened this issue Sep 26, 2022 · 3 comments
Assignees
@digiwand
Labels
MV3 type-bug Something isn't working
Milestone
MV3 Implementation

Comments

@digiwand
Copy link
Contributor

digiwand commented Sep 26, 2022 •
edited
Loading

Describe the bug

There have been various causes for this error. There will be multiple tickets that will fix this issue for our MV3 beta launch.

1 of numerous causes for this error (Fixed by #16075):
Currently, when the service worker terminates it produces this error, Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist., numerous times. Even 100+ times from a single service worker restart.

image

image

Steps to reproduce

  1. Start the extension using MV3
  2. View dapp page
  3. Inspect app-init.js service worker and terminate service worker
  4. Observe error in console

Error messages or log output

`Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.`

Version

10.19.0

Build type

No response

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response
@digiwand digiwand added the MV3 label Sep 26, 2022
@digiwand digiwand added this to the MV3 Implementation milestone Sep 26, 2022
@digiwand digiwand self-assigned this Sep 26, 2022
@digiwand digiwand mentioned this issue Sep 26, 2022
Closed
6 tasks
@digiwand digiwand changed the title MV3: "Could not establish connection. Receiving end does not exist." error [Bug]: MV3: "Could not establish connection. Receiving end does not exist." error Sep 26, 2022
@digiwand digiwand added PR - P1 identifies PRs deemed priority for Extension team type-bug Something isn't working and removed PR - P1 identifies PRs deemed priority for Extension team labels Sep 26, 2022
@digiwand digiwand changed the title [Bug]: MV3: "Could not establish connection. Receiving end does not exist." error [Bug non-blocking]: MV3: "Could not establish connection. Receiving end does not exist." error Sep 28, 2022
@digiwand digiwand changed the title [Bug non-blocking]: MV3: "Could not establish connection. Receiving end does not exist." error [Bug]: MV3: "Could not establish connection. Receiving end does not exist." error Oct 4, 2022
@digiwand
Copy link
Contributor Author

digiwand commented Oct 4, 2022 •
edited
Loading

This may be fixed by:
#15986
#15052

@jpuri
Copy link
Contributor

jpuri commented Oct 12, 2022

This should be fixed after the PR is merged #16075

@digiwand
Copy link
Contributor Author

I believe we have merged in the fixes for this issue

@gauthierpetetin gauthierpetetin mentioned this issue Aug 20, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@digiwand digiwand

Labels
MV3 type-bug Something isn't working
Projects
None yet
Milestone
MV3 Implementation
Development

No branches or pull requests
2 participants
@jpuri @digiwand