Replies: 2 comments
-
this is more of a question than a bug? I'm gonna convert this to a discussion. |
Beta Was this translation helpful? Give feedback.
0 replies
-
WXT doesn't do this automatically for you, since it requires additional permissions. See this stack overflow answer instead: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
i know 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 but i don't know how to do it in wxt
my background.ts
Reproduction
Could not establish connection. Receiving end does not exist when extension updated on store
Steps to reproduce
No response
System Info
Used Package Manager
npm
Validations
Beta Was this translation helpful? Give feedback.
All reactions