I am trying to make a new extension using manifest V3, this is my first time and I'm getting an error when defining the background.js
here is the error:
image
I created the background js using Vue 3, and the manifest wasn't able to read it and apply it, that's why it failed
Related
I'm trying to migrate Change Colors to Manifest V3, since support for V2 is ending.
Now I'm get stucked against the error below, which is shown in inspect views when you load the extension.
background_page.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
background_page.js:1 Uncaught (in promise) Error: Cannot access contents of url "devtools://devtools/bundled/worker_app.html?remoteBase=https://chrome-devtools-frontend.appspot.com/serve_file/#3cf3e8c8a07d104b9e1260c910efb8f383285dc5/&browserConnection=true". Extension manifest must request permission to access this host.
Here is my Pull Request to show all changes I made.
I'm not sure this error must be resolved to work properly, or you can just ignore it.
But the extension isn't working with the current source.
How to resolve the error?
Or, if this error isn't crucial, how to make the extension to work?
hello I am trying to use the ffmpegwasm/ffmpeg.wasm library inside chrome extension
the library is loaded inside react component that is located inside an iframe
the problem is when I try to load I got an error that I cannot download the core files
I tried to use the example library for chrome extension but also got an error "Uncaught (in promise) ReferenceError: SharedArrayBuffer is not defined error. "
the files are web_accessible_resources inside the manifest
I am using manifest version 3
I am trying to deploy an open source project (https://github.com/LiteFarmOrg/LiteFarm) on local host through docker composer and i have followed the instructions provided in the link, the app is a node.js app with frontend in react.js i have provided the (google_api_key) for the map to work in the application in the ".env" file but i am getting the error of "invalidkey" yet i tried to provide another newly generated key same error i faced. the screenshot is as
invalid key error
also in the location text field the "icon of something went wrong is coming".
Describe the bug
migrating a chrome extension from manifest v2 to v3, content script static not working, dynamic also not working,
"chrome.scripting.registerContentScripts( " telling is not a function
To Reproduce
scenario1
Steps to reproduce the behavior:
1. create an extension with V3
2. mention in manifest one service worker and content script
3. then upload or refresh the extension
4. service worker working but not the content script ( static )
scenario2
Steps to reproduce the behavior:
1. create an extension with V3
2. mention in manifest one service worker
3. in service worker, the below event either execute or register the script is not working
chrome.tabs.onUpdated.addListener(async function (tabId, changeInfo, tab) {
chrome.scripting.executeScript({ target: {tabId: tabId},
or
chrome.scripting.registerContentScripts(options,function(et){});
4. then upload or refresh the extension
5. service worker working but not the content script ( dynamic )
Expected behavior
in v2 I am able to either static or programmatically injecting the content script in a page where as in v3 is not, so expecting the steps for same in V3 to work
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: Windows 10
Browser: Chrome
Version 89.0.4389.90 (Official Build) (64-bit)
Additional context
please help me to resolve or any alternative work around to proceed further for migration
I published a chrome extension to testers only. The app seems to work very well. I don't see any errors when inspecting the console for the popup or the background page. However, I get the following error when inspecting the console for any web page: "Uncaught Error: "getBackgroundPage" can only be used in extension processes. See the content scripts documentation for more extensions/schema_generated_bindings.js:418"
This app contains several JavaScript files, but each one includes the code within a self executing function. The "getBackgroundPage" calls are in the JavaScript files.
Could you please help? Isn't the app I built an isolated module independent from any web page? How can I prevent this error from happening?
I had the same error when I was trying to communicate with the background page from my content script. The correct way of doing it is via Message Passing. It is very well documented here : https://developer.chrome.com/extensions/messaging.html