im building an extension in chrome but it's always inactive if i dont open debug mode of plugin, it lead to the plugin does not working when i enter to target pages, eg: dms.mydomain-inc.com
How to make it's active permanent when i access to page registering in manifest.json?
Here is my manifest.json
{
"name": "Tool for test",
"description": "Build an Extension!",
"version": "1.0",
"manifest_version": 3,
"background": {
"service_worker": "background.js",
"persistent": true
},
"options_page": "options.html",
"permissions": ["storage",
"activeTab",
"scripting",
"webRequest"],
"host_permissions": [
"*://*.mydomain.vn/*",
"*://dms.mydomain-inc.com/",
"wss://news.mydomain-inc.com/"
],
"content_scripts": [
{
"matches": ["*://news.mydomain-inc.com/"],
"css": ["css/style.css"],
"js": ["contentScript.js", "jquery-3.5.1.min.js"]
}
],
"action": {
"default_popup": "popup.html",
"default_icon": {
"16": "/images/get_started16.png",
"32": "/images/get_started32.png",
"48": "/images/get_started48.png",
"128": "/images/get_started128.png"
}
},
"icons": {
"16": "/images/get_started16.png",
"32": "/images/get_started32.png",
"48": "/images/get_started48.png",
"128": "/images/get_started128.png"
}
}
Thanks
it is normal thing developing manifest version 3 extensions.
Chrome is becoming a browser that is everything but light and this is partly due to the dozens of extensions the user installs.
Thus Google introduced service worker in extensions in order to free up some memory whenever possible.
SW is activated when necessary and then goes to sleep until the moment it's awakened to perform a new job.
Said this,
"persistent": true in manifest is useless and could generate an error.
we have to realize that when SW becomes inactive all variables and objects defined in this script will be lost unless we plan to save them somehow in a persistent storage.
Normally, the asynchronous chrome.storage API are used to save variables \ objects used in the SW.
If you cannot allow SW become inactive (for some important reason) you could use a "dirty" technique that bypasses this "restriction".
This technique consists in opening a long-lasting communication channel and sending fictitious messages between SW and any browser tab.
For more details on this technique read this thread: Persistent Service Worker in Chrome Extension
Related
Recently, I have been working on a Chrome plug-in with co-workers and I must admit that I do not have much experience with Chrome extensions. We already published one version. Now, I just submitted a second release.
I am aware that following the Manifest v3 rules helps to speed up the review process. Also, I believe we are following the rules and we really need to have a fast review process.
However, I keep seeing this message:
It points to the official documentation on the topic: Migrating to Manifest v3 which includes a check-list.
This message makes me suspicious that I might have made some mistakes.
Hence, I would like to show my manifest.json:
{
"name": "My plug-in name",
"description": "Auto-fill some specific forms",
"version": "0.0.22",
"manifest_version": 3,
"action": {
"default_popup": "src/importer/popup.html",
"default_icon": "src/importer/img/company-logo.png"
},
"icons": {
"128": "src/importer/img/company-icon.png"
},
"permissions": ["activeTab", "scripting"],
"background": {
"service_worker": "src/importer/background.js"
},
"content_scripts": [
{ "js": ["src/importer/content-script.js"],
"matches": ["https://*.onewebsite.com/*"] }
]
}
It seems to be correct.
Am I missing something? Is the extension Manifest V3 compliant?
Should I ignore Chrome Web Store alert?
I built a small Chrome extension that works properly using the Chrome extension Manifest v2; however, support for v2 has been deprecated and updates must be published using Manifest v3.
Seems straightforward enough but Chrome throws an error when trying to load the unpacked extension with the new Manifest. Moreover, the error that it throws seems unrelated to the code I wrote and refers to one of the common libraries that I imported. The libraries I import include debounce for lodash, get from lodash, cheerio, and axios.
Here are both versions of the manifest followed by the error that Chrome throws when loading the extension via the new manifest.
Any pointers would be greatly appreciated. Thank you so much!
Manifest v2
{
"name": "LastBottle Price Checker",
"version": "1.0.0",
"description": "Fact-check the retail and web prices advertised on LastBottleWines.com by viewing crowd-sourced from consumers.",
"manifest_version": 2,
"icons": {
"128": "icon128.png"
},
"permissions": ["*://www.vivino.com/*", "*://api.vivino.com/", "unlimitedStorage", "activeTab"],
"content_scripts": [
{
"matches": ["https://www.lastbottlewines.com/*"],
"js": ["contentScript.js"]
}
],
"background": {
"scripts": ["bgScript.js"],
"persistent": false
}
}
Manifest v3
{
"name": "LastBottle Assistant",
"version": "1.0.0",
"description": "Fact-check the retail and web prices advertised on LastBottleWines.com by viewing crowd-sourced from consumers.",
"manifest_version": 3,
"icons": {
"128": "icon128.png"
},
"permissions": ["unlimitedStorage", "activeTab"],
"host_permissions": ["*://www.vivino.com/*","*://api.vivino.com/"],
"content_scripts": [
{
"matches": ["https://www.lastbottlewines.com/*"],
"js": ["contentScript.js"]
}
],
"minimum_chrome_version": "93",
"background": {
"service_worker": "bgScript.js",
"type": "module"
}
}
Error thrown by Chrome when loading unpacked extension
The first message is seemingly caused by the second...
I tried following Google's guide for migrating to Manifest v2, including the move from the background scripts to the service_worker framework. The service_worker conforms to the single JS file requirement and unchanged from the single JS file that worked properly when run in the previous manifest. The service_worker also meets the stated requirement of not interacting with the DOM.
While developing a chrome extension and delivering to users via GPO, for some reason after the installation of the extension on chrome the service worker do not register on chrome in Citrix environment. That seems to be a problem only with Manifest V3.
Things to note:
Installation is successful on chrome, I can see the icon on chrome://extensions/, but the service worker appears "Inactive".
This particular extension is hosted on private web server.
After restarting chrome, sometimes the service worker is successfully registered.
To see if the service worker was registered, I checked on chrome://serviceworker-internals/.
What I have tried so far:
When the installation is successful, on the service worker I used this approach:
chrome.runtime.onInstalled.addListener(function (value) {
if (value.reason == 'install') {
setTimeout(function () {
chrome.runtime.reload();
console.log('Reload!');
}, 2000)
}
})
But since the service worker keeps "Inactive" and not registered on chrome://serviceworker-internals/, it didn't work.
I checked that the problem only happens in Citrix environment with non-permanent images, meaning that the extension will install in every user logon via GPO.
This extension does not have a default popup, it's supposed to work entirely on service workers, without a user interface.
I checked that with manifest V2 extensions, on the same environment, everything works fine.
If I add a popup, sometimes when the user clicks on the popup, the registration of the worker starts. Same behavior as restarting chrome.
I did not find any mention to this problem anywhere, since it's so specific.
Note: I can't share any part of the service worker since it's a private extension, but I'll share the manifest below, but keep in mind that the installation works fine as I mentioned before.
So, I'm looking for any idea on what is going on before sending an issue on chrome.
manifest.json:
{
"manifest_version": 3,
"name": "",
"description": "",
"version": "1.0",
"background": {
"service_worker": "background.js"
},
"content_scripts": [
{
"matches": [ "<all_urls>" ],
"css": [ "logic.js" ]
}
],
"permissions": [ "storage", "declarativeContent", "activeTab", "scripting", "tabs", "webNavigation", "nativeMessaging" ],
"host_permissions": [ "https://*/*" ],
"action": {
"default_icon": {
"16": "/images/logo16.png",
"32": "/images/logo32.png",
"48": "/images/logo48.png",
"128": "/images/logo128.png"
}
},
"icons": {
"16": "/images/logo16.png",
"32": "/images/logo32.png",
"48": "/images/logo48.png",
"128": "/images/logo128.png"
}
}
Hello Stack Overflow Team, I am hoping you can help.
The Google Chrome webstore as of 3/1/2020 is rejecting all my extensions that have activeTab permissions specifically <all_urls> requests. Below is the email I get AFTER my extensions are reviewed.
Your item did not comply with the following section of our Program Policies:
"User Data Privacy"
Your product violates the "Use of Permissions" section of the policy, which requires that you:
Request access to the narrowest permissions necessary to implement your product’s features or services.
If more than one permission could be used to implement a feature, you must request those with the least access to data or functionality.
Don't attempt to "future proof" your product by requesting a permission that might benefit services or features that have not yet been implemented.
This is a HUGE problem because not only are all our recent apps being rejected, but so are the updates to our existing apps that are using the EXACT same permission set.
Our extensions connects business phone systems to Chrome and one of the features we offer is click to call. In order for click to call to work we need <all_urls> permissions so we can find phone number and make them clickable. Below is a sample of our code.
What changes do I need to make in order for Google Chrome to STOP rejecting our extensions?
{
"update_url": "https://clients2.google.com/service/update2/crx",
"name": "abc extension",
"description": "abc company click to call",
"short_name": "abc click to call",
"version": "0.00.01",
"manifest_version": 2,
"permissions": [
"storage",
"notifications",
"tabs",
"contextMenus",
"<all_urls>"
],
"browser_action": {
"default_icon": {
"19": "images/icon.png"
}
},
"content_security_policy": "script-src 'self' https://maxcdn.bootstrapcdn.com; object-src 'self'",
"default_locale": "en",
"content_scripts": [
{
"matches":["<all_urls>"],
"css": [ "css/content.css" ],
"js": ["js/jquery.min.js","js/content.js"],
"run_at": "document_end"
}
],
"background": {
"scripts": ["js/jquery.min.js","js/background.js"]
},
"web_accessible_resources":["images/*.png","html/login.html","html/dashboard.html"],
"icons": {
"16": "images/icon.png",
"48": "images/icon.png"
}
How force (or request in installation) WebExtension update on start browser?
In Firefox I need click in this option:
In Opera I need click in this button:
What I want to know is if there is any way to check using the API if there is any update or configure "manifest.json" to do this.
I need add autoupdate to Opera, Firefox and Chrome.
My current manifest.json (Firefox):
{
"name": "Name",
"version": "0.0.1",
"manifest_version": 2,
"description": "Description",
"applications": {
"gecko": {
"id": "xxxxxxxxx#xxxxxxxxx.org",
"strict_min_version": "45.0"
}
},
"browser_action": {
"default_icon": "images/icon.png",
"default_popup": "popup.html"
},
"background": {
"scripts": [
"background.js"
]
},
"icons": {
"128": "images/icon-128px.png",
"48": "images/icon-48px.png",
"32": "images/icon-32px.png",
"16": "images/icon.png"
}
}
For chrome extension, you could use chrome.runtime.requestUpdateCheck to request an immediate update check, and please be aware of the following important tips.
Important: Most extensions/apps should not use this method, since chrome already does automatic checks every few hours, and you can listen for the runtime.onUpdateAvailable event without needing to call requestUpdateCheck.
This method is only appropriate to call in very limited circumstances, such as if your extension/app talks to a backend service, and the backend service has determined that the client extension/app version is very far out of date and you'd like to prompt a user to update. Most other uses of requestUpdateCheck, such as calling it unconditionally based on a repeating timer, probably only serve to waste client, network, and server resources.