Submitted Chrome extension: “manifest is invalid” on download
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
1
I recently submitted a chrome extension, but when I try to download the extension it says that the manifest file is invalid. Not sure why.
Here is my manifest :
"name": "My chrome extension",
"version": "0.2",
"description": "My chrome extension description.",
"permissions": [ "activeTab", "tabs", "contextMenus" ],
"background":
"persistent": false
,
"browser_action":
"default_icon": "favicon.png",
"default_popup": "index.html"
,
"manifest_version": 2
Is there a tool online where I can validate a Chrome extension manifest file?
google-chrome-extension chrome-web-store edited Nov 14 '18 at 11:02
Xan
55k10109140
asked Nov 13 '18 at 22:37
JibusJibus
262
add a comment |
1
I recently submitted a chrome extension, but when I try to download the extension it says that the manifest file is invalid. Not sure why.
Here is my manifest :
"name": "My chrome extension",
"version": "0.2",
"description": "My chrome extension description.",
"permissions": [ "activeTab", "tabs", "contextMenus" ],
"background":
"persistent": false
,
"browser_action":
"default_icon": "favicon.png",
"default_popup": "index.html"
,
"manifest_version": 2
Is there a tool online where I can validate a Chrome extension manifest file?
google-chrome-extension chrome-web-store edited Nov 14 '18 at 11:02
Xan
55k10109140
asked Nov 13 '18 at 22:37
JibusJibus
262
add a comment |
1
1
1
I recently submitted a chrome extension, but when I try to download the extension it says that the manifest file is invalid. Not sure why.
Here is my manifest :
"name": "My chrome extension",
"version": "0.2",
"description": "My chrome extension description.",
"permissions": [ "activeTab", "tabs", "contextMenus" ],
"background":
"persistent": false
,
"browser_action":
"default_icon": "favicon.png",
"default_popup": "index.html"
,
"manifest_version": 2
Is there a tool online where I can validate a Chrome extension manifest file?
google-chrome-extension chrome-web-store edited Nov 14 '18 at 11:02
Xan
55k10109140
asked Nov 13 '18 at 22:37
JibusJibus
262
I recently submitted a chrome extension, but when I try to download the extension it says that the manifest file is invalid. Not sure why.
Here is my manifest :
"name": "My chrome extension",
"version": "0.2",
"description": "My chrome extension description.",
"permissions": [ "activeTab", "tabs", "contextMenus" ],
"background":
"persistent": false
,
"browser_action":
"default_icon": "favicon.png",
"default_popup": "index.html"
,
"manifest_version": 2
Is there a tool online where I can validate a Chrome extension manifest file?
google-chrome-extension chrome-web-store google-chrome-extension chrome-web-store edited Nov 14 '18 at 11:02
Xan
55k10109140
asked Nov 13 '18 at 22:37
JibusJibus
262
edited Nov 14 '18 at 11:02
Xan
55k10109140
asked Nov 13 '18 at 22:37
JibusJibus
262
edited Nov 14 '18 at 11:02
Xan
55k10109140
edited Nov 14 '18 at 11:02
Xan
55k10109140
edited Nov 14 '18 at 11:02
Xan
55k10109140
55k10109140
asked Nov 13 '18 at 22:37
JibusJibus
262
asked Nov 13 '18 at 22:37
JibusJibus
262
asked Nov 13 '18 at 22:37
JibusJibus
262
262
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
3
You are missing scripts in your background item.
...
"permissions": [ "activeTab", "tabs", "contextMenus" ],
"background":
"scripts": [
"path/to/js/script",
],
"persistent": false
,
"browser_action":
"default_icon": "favicon.png",
"default_popup": "index.html"
,
...
OR just remove the background item from your manifest if you are not planning on using it.
...
"permissions": [ "activeTab", "tabs", "contextMenus" ],
"browser_action":
"default_icon": "favicon.png",
"default_popup": "index.html"
,
...
--
You don't need tools to test the manifest, go to the chrome://extensions page, enable developer mode on the top right and load your extension, it will tell you the error and how to solve it.
edited Nov 14 '18 at 5:57
wOxxOm
27.9k44963
answered Nov 14 '18 at 4:37
ToxnycToxnyc
33418
Thank you ! Indeed it was the background to remove
– Jibus
Nov 14 '18 at 9:24
1
In addition to loading an extension unpacked, a developer can pack an extension locally (though the resulting package will only really work on the same machine). Installing an extension packaged this way will perform all the checks that a "real" install would. However, there's some differences between that logic and the webstore upload verification (which is the reason for the question in the first place) - some extensions may pass browser checks but not Web Store checks.
– Xan
Nov 14 '18 at 11:05
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53290559%2fsubmitted-chrome-extension-manifest-is-invalid-on-download%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
3
You are missing scripts in your background item.
...
"permissions": [ "activeTab", "tabs", "contextMenus" ],
"background":
"scripts": [
"path/to/js/script",
],
"persistent": false
,
"browser_action":
"default_icon": "favicon.png",
"default_popup": "index.html"
,
...
OR just remove the background item from your manifest if you are not planning on using it.
...
"permissions": [ "activeTab", "tabs", "contextMenus" ],
"browser_action":
"default_icon": "favicon.png",
"default_popup": "index.html"
,
...
--
You don't need tools to test the manifest, go to the chrome://extensions page, enable developer mode on the top right and load your extension, it will tell you the error and how to solve it.
edited Nov 14 '18 at 5:57
wOxxOm
27.9k44963
answered Nov 14 '18 at 4:37
ToxnycToxnyc
33418
Thank you ! Indeed it was the background to remove
– Jibus
Nov 14 '18 at 9:24
1
In addition to loading an extension unpacked, a developer can pack an extension locally (though the resulting package will only really work on the same machine). Installing an extension packaged this way will perform all the checks that a "real" install would. However, there's some differences between that logic and the webstore upload verification (which is the reason for the question in the first place) - some extensions may pass browser checks but not Web Store checks.
– Xan
Nov 14 '18 at 11:05
add a comment |
3
You are missing scripts in your background item.
...
"permissions": [ "activeTab", "tabs", "contextMenus" ],
"background":
"scripts": [
"path/to/js/script",
],
"persistent": false
,
"browser_action":
"default_icon": "favicon.png",
"default_popup": "index.html"
,
...
OR just remove the background item from your manifest if you are not planning on using it.
...
"permissions": [ "activeTab", "tabs", "contextMenus" ],
"browser_action":
"default_icon": "favicon.png",
"default_popup": "index.html"
,
...
--
You don't need tools to test the manifest, go to the chrome://extensions page, enable developer mode on the top right and load your extension, it will tell you the error and how to solve it.
edited Nov 14 '18 at 5:57
wOxxOm
27.9k44963
answered Nov 14 '18 at 4:37
ToxnycToxnyc
33418
Thank you ! Indeed it was the background to remove
– Jibus
Nov 14 '18 at 9:24
1
In addition to loading an extension unpacked, a developer can pack an extension locally (though the resulting package will only really work on the same machine). Installing an extension packaged this way will perform all the checks that a "real" install would. However, there's some differences between that logic and the webstore upload verification (which is the reason for the question in the first place) - some extensions may pass browser checks but not Web Store checks.
– Xan
Nov 14 '18 at 11:05
add a comment |
3
3
3
You are missing scripts in your background item.
...
"permissions": [ "activeTab", "tabs", "contextMenus" ],
"background":
"scripts": [
"path/to/js/script",
],
"persistent": false
,
"browser_action":
"default_icon": "favicon.png",
"default_popup": "index.html"
,
...
OR just remove the background item from your manifest if you are not planning on using it.
...
"permissions": [ "activeTab", "tabs", "contextMenus" ],
"browser_action":
"default_icon": "favicon.png",
"default_popup": "index.html"
,
...
--
You don't need tools to test the manifest, go to the chrome://extensions page, enable developer mode on the top right and load your extension, it will tell you the error and how to solve it.
edited Nov 14 '18 at 5:57
wOxxOm
27.9k44963
answered Nov 14 '18 at 4:37
ToxnycToxnyc
33418
You are missing scripts in your background item.
...
"permissions": [ "activeTab", "tabs", "contextMenus" ],
"background":
"scripts": [
"path/to/js/script",
],
"persistent": false
,
"browser_action":
"default_icon": "favicon.png",
"default_popup": "index.html"
,
...
OR just remove the background item from your manifest if you are not planning on using it.
...
"permissions": [ "activeTab", "tabs", "contextMenus" ],
"browser_action":
"default_icon": "favicon.png",
"default_popup": "index.html"
,
...
--
You don't need tools to test the manifest, go to the chrome://extensions page, enable developer mode on the top right and load your extension, it will tell you the error and how to solve it.
edited Nov 14 '18 at 5:57
wOxxOm
27.9k44963
answered Nov 14 '18 at 4:37
ToxnycToxnyc
33418
edited Nov 14 '18 at 5:57
wOxxOm
27.9k44963
edited Nov 14 '18 at 5:57
wOxxOm
27.9k44963
edited Nov 14 '18 at 5:57
wOxxOm
27.9k44963
27.9k44963
answered Nov 14 '18 at 4:37
ToxnycToxnyc
33418
answered Nov 14 '18 at 4:37
ToxnycToxnyc
33418
answered Nov 14 '18 at 4:37
ToxnycToxnyc
33418
33418
Thank you ! Indeed it was the background to remove
– Jibus
Nov 14 '18 at 9:24
1
In addition to loading an extension unpacked, a developer can pack an extension locally (though the resulting package will only really work on the same machine). Installing an extension packaged this way will perform all the checks that a "real" install would. However, there's some differences between that logic and the webstore upload verification (which is the reason for the question in the first place) - some extensions may pass browser checks but not Web Store checks.
– Xan
Nov 14 '18 at 11:05
add a comment |
Thank you ! Indeed it was the background to remove
– Jibus
Nov 14 '18 at 9:24
1
In addition to loading an extension unpacked, a developer can pack an extension locally (though the resulting package will only really work on the same machine). Installing an extension packaged this way will perform all the checks that a "real" install would. However, there's some differences between that logic and the webstore upload verification (which is the reason for the question in the first place) - some extensions may pass browser checks but not Web Store checks.
– Xan
Nov 14 '18 at 11:05
Thank you ! Indeed it was the background to remove
– Jibus
Nov 14 '18 at 9:24
Thank you ! Indeed it was the background to remove
– Jibus
Nov 14 '18 at 9:24
1
1
In addition to loading an extension unpacked, a developer can pack an extension locally (though the resulting package will only really work on the same machine). Installing an extension packaged this way will perform all the checks that a "real" install would. However, there's some differences between that logic and the webstore upload verification (which is the reason for the question in the first place) - some extensions may pass browser checks but not Web Store checks.
– Xan
Nov 14 '18 at 11:05
In addition to loading an extension unpacked, a developer can pack an extension locally (though the resulting package will only really work on the same machine). Installing an extension packaged this way will perform all the checks that a "real" install would. However, there's some differences between that logic and the webstore upload verification (which is the reason for the question in the first place) - some extensions may pass browser checks but not Web Store checks.
– Xan
Nov 14 '18 at 11:05
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53290559%2fsubmitted-chrome-extension-manifest-is-invalid-on-download%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
