My manifest.json:
{
"name": "NAME",
"version": "1.0",
"description": "Desc",
"manifest_version": 2,
"chrome_settings_overrides": {
"homepage": "blank.html"
}
}
When trying to load that as an unpacked extension, I get the following error:
Failed to load extension from: D:\Path\To\Extension, Empty dictionary for 'chrome_settings_overrides'.
What did I do wrong?
Related
I got this extension for google chrome and it won't load when I try to load unpacked extension. Where is the problem?
{
"manifest_version": 2,
"name": "HTML",
"description": "HTML change",
"version": "1",
"background": {
"page": "background.html"
},
"content_scripts": [
{
"matches": ["https://ocjene.skole.hr/pocetna/prijava/*"],
}
],
}
Trailing commas mean invalid json - try this change first:
{
"manifest_version": 2,
"name": "HTML",
"description": "HTML change",
"version": "1",
"background": {
"page": "background.html"
},
"content_scripts": [
{
"matches": ["https://ocjene.skole.hr/pocetna/prijava/*"]
}
]
}
You may refer with this Can't load unpacked extension? forum.
I'm going to recommend that you start with a powerwash. This will wipe your device and return it to factory settings (and also put you back to the stable channel). Full instructions can be found in this help center article.
After the powerwash, I would suggest that you test whether or not the extension will load while still running a stable build. If it does, and then it stops working when you switch o the dev channel, that helps to narrow down the issue.
Additional references:
Load Unpacked Extension
Unable to load unpacked extensions
Here is my manifest.json file
{
"name":"Name",
"version": "1.0",
"description":"This is the description",
"manifest-version": 2
}
Chrome says
manifest file is missing or unreadable
The file is indeed a .json file, rather than a .txt file. What is wrong with my manifest.json file?
manifest file is missing or unreadable
You have manifest-json instead of manifest_json in the code snippet.
If you follow this tutorial then it lists the simple manifest.json for chrome extension. In below snippet replace name, description, icon, url with your own and give it a try.
{
"name": "Great App Name",
"description": "Pithy description (132 characters or less, no HTML)",
"version": "0.0.0.1",
"manifest_version": 2,
"icons": {
"128": "icon_128.png"
},
"app": {
"urls": [
"http://mysubdomain.example.com/"
],
"launch": {
"web_url": "http://mysubdomain.example.com/"
}
}
}
Let us know, if you have any difficulty in following the tutorial.
I'm trying to write a chrome extension that uses a CSS file, but it just does not get injected. The manifest file is pretty straight forward
{
"manifest_version": 2,
"name": "Youtube Embed Performance",
"description": "",
"version": "1.0",
"permissions": ["https://redcursor.net/channels/18181"],
"content_scripts": [
{
"matches" : ["https://redcursor.net/channels/18181"],
"css" : ["youtube.css"],
"js" : ["youtube.js"],
"run_at" : "document_start"
}
]
}
The script appears in the Sources tab as part of my extension (and gets executed). The CSS won't appear there.
Just started my first chrome extension and I'm trying to use the chrome.bookmarks.getChildren() method. I am getting an error saying
Uncaught Error: You do not have permission to use 'bookmarks.getChildren'. Be sure to declare in your manifest what permissions you need.
My manifest.json file:
{
"manifest_version": 2,
"name": "Top Sites",
"description": "blah blah blah",
"version": "1.0",
"permissions": [
"bookmarks"
],
"browser_action": {
"default_icon": "images/icon.png",
"default_popup": "html/popup.html"
}
}
Chrome API for sockets is not working now for me.
I've got following manifest:
{
"name": "My name",
"version": "0.1",
"manifest_version": 2,
"background": {
"page": "background.html"
},
"browser_action": {
"default_icon": "ico16.png",
"default_title": "My extension",
"default_popup": "popup.html"
},
"description": "bla bla bla",
"minimum_chrome_version": "23",
"icons": {
"ico128": "ico128.png",
"ico16": "ico16.png",
"icon_logo": "icon_logo.png"
},
"options_page": "options.html",
"permissions": ["experimental",
{"socket": [
"udp-send-to"
]},
"notifications",
"background"]
}
but following warning it's been displayed when loading the extension:
'socket' is not allowed for specified package type (theme, app, etc.).
I've tested with Version 23.0.1246.0 canary and 23.0.1246.0 dev-m
This is expected behavior, the socket API is only available to packaged apps, and based on the manifest you're working on an extension.
If you will communicate this extension with a NodeJs application, you can use Socket.iO for this. Check how: https://www.thirdrocktechkno.com/blog/node-js-socket-io-chrome-extension-integration/