Geek Answers Handbook

The Chrome Web Store server rejects the extension using "Error: manifest must determine version."

NOTE. This question is about the version manifest.json attribute that you use when developing Chrome. This is similar to the question below about manifest_version , but it is not. I really tried to learn from this, but I failed.

Do I need to update the Chrome extension for manifest version 2 if the manifest version is not initially specified?

-

I am currently making my first Chrome extension. Powerful, funny, great.

Except for the stupid thing that annoys me.

My Chrome extension is open source, so you can go straight to the GitHub code to see right away that I made a dumb mistake.

https://github.com/internaciulo/search-tab-in-chrome-s-omnibox

In manifest.json , the most imortant file in Chrome development, you should see

 { ... "version": "13", ... }

The chrome extension itself works quite well, see the screenshots folder in github, but only locally, that is, when I open it as an application for unpacking (this can be done in Chrome by going to chrome://extensions

Great, so I go to [Chrome Dashbord Developer for Webmasters], download, let 2 or 3 users download it for free, profit!

Not really.

I tried everything: maybe he wants 13 or "13" or "13.0", or there is confusion with manifest_version , which should be an integer of either or or or or. Each time the same annoying error:

Download an extension or application (.zip file)
search-tab-in-chrome-s-omnibox.zip (server rejected)
An error occurred: your item could not be processed.

the manifest must determine the version.

Oh, computers, you are so useful, but why is an expensive computer so intolerant of our mistakes? Yes, they are stupid, but from the very beginning of the calculations you should have known that we are “People, all too people” ( http://en.wikipedia.org/wiki/Human,_All_Too_Human )

PS: this is not only my first chrome extension, but also my first stackoverflow question, while I used it in the past, but read-only. Please be nice: -D

Update:

  • 2013-10-13: ok, the problem is solved, that’s all: comments in json files
  • 2013-10-13: part (only) of the error was fixed thanks to @ChrisP: comments are not allowed in json files, which is sad but legal. https://github.com/getify/JSON.minify allows you to take a json file with comments and display it without comments. The best of both worlds.
+7
json javascript google-chrome google-chrome-extension
source share
1 answer

The manifest.json file contains comments:

 { "name": "__MSG_name__", // {en}: "Search Tab in Chrome Omnibox" "description": "__MSG_description__", ... }

which are not allowed in JSON, cf http://json.org/ .

If you delete them, your manifest should be valid and the error should go away. You can find JSON parsers online to make sure it is valid, for example:

+8
source share

More articles:


All Articles