Error on my unpacked extension

[Ghostmancer]

The error says that the Manifest is not correct Json. It says that
Dictionary keys must be quoted. Here is the code and will bold the
location of the error.

{
"name": "Ghostmancer's Blog Extention-Chrome",
"version": "1.0",
"incognito": "split",
"chrome_url_overrides": {
"newtab": "http://ghostmancer.blogspot.com/p/most-recent-post.html"
},
<b>"</b>browser_action": {
"default_icon": "icon.png", // required
"default_title": "Ghostmancer's Blog", // optional; shown in
tooltip
"default_popup": "popup.html" // optional
},

[PhistucK]

Remove the comments. Comments are not allowed in JSON files.

☆PhistucK

--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
   http://groups.google.com/a/chromium.org/group/chromium-discuss

[PhistucK]

Also, if the error did not say that the comments are the problem, please, search crbug.com for an existing issue and star it. If you cannot find one, file a new issue at new.crbug.com.

Add complete reproduction steps and ask for a better error text.

Thank you.

☆PhistucK

On Tue, Sep 7, 2010 at 07:11, Ghostmancer <ghost...@gmail.com> wrote:

[psun]

Hi,

I'm also getting the same message. I tried retyping all the quotes with double quote as some web sites point. 

Chrome version:21.0.1180.90 on Mac version 10.5.8.

Error message: "Manifest is not valid JSON.  Line: 1, column: 2, Dictionary keys must be quoted."

Here is my json file:

{

  "name":  "my app name",

  "description": "Blog",

  "version": "0.0.0.1",

  "manifest_version": "1.1",

  "icons": {

    "128": "icon_128.png"

  },

  "app": {

    "urls": [

      "http://myblog.blogspot.com/"

    ],

    "launch": {

      "web_url": "http://myblog.blogspot.com/page-1.html"

    }

  }

}

[PhistucK]

I am not sure what is the problem to which this error points, but here are two actions you can perform that might alleviate the issue -

1. Save manifest.json using a UTF-8 encoding - with BOM.

2. Change "manifest_version": "1.1", to either "manifest_version": 2, or completely remove it (though I believe Chrome will not load it as an unpacked application anymore if the manifest version is not 2. I am also not sure whether the Web Store accepts old manifest version anymore).

☆PhistucK

[Tibor]

Using incorrect manifest version may result in strange errors too.

Version 1 is phased out:

http://developer.chrome.com/extensions/manifestVersion.html