721051 - The Apps Submission process reports JSON error for valid JSON

Status: RESOLVED DUPLICATE of bug 721103

(addons.mozilla.org Graveyard :: Add-on Validation, defect)

Description

[[e-mail]]

A couple of customers have reported that their apps won't submit and that the get a JSON error even though they believe their manifest is correct. 

Using the following manifest file....

{
    "name": "MozApps Hello World",
    "description": "MozApps Hello World Application.",
    "launch_path": "http://helloworld.webruntime.com",
    "icons": {
        "128": "icon128.png"
    },
    "developer": {
        "name": "MisfitGeek",
        "url": "http://www.WebRuntime.com"
    },
    "locales": {
        "en": {
            "name": "MozApps Hello World",
            "description": "MozApps Hello World Application."
        },
        "de": {
            "name": "MozApps Hello World",
            "description": "MozApps Hello World Applikation."
        }
    },
    "default_locale": "en",
    "version": "1.0.0"
}

http://jsonlint.com/ reports it as valid JSON but App store submission reports

 

Your app failed validation with 1 error.

·         App: JSON Parse Error

Comment 1

[Kumar McMillan [:kumar]]

I can't reproduce this on https://apps-preview.mozilla.org/en-US/developers/app/submit/2 -- is that the site they were using? The real error is this:

App: Missing 'installs_allowed_from' property

Error: In order to submit a webapp to https://apps-preview.mozilla.org, 'installs_allowed_from' must exist and must contain https://apps-preview.mozilla.org.

which is displayed as expected for me.

Comment 3

[Kumar McMillan [:kumar]]

Not sure these are the same yet. They might be. Let's see if we can reproduce the JSON parse error first.

Comment 4

[Christopher Van Wiemeersch [:cvan]]

Your `launch_path` corresponds to the path on your server. See https://developer.mozilla.org/en/Apps/Manifest#Definition_of_the_fields

Comment 5

[Kumar McMillan [:kumar]]

I see it now. This has to do with the BOM (again). We didn't fix it all the way through the stack. See bug 721103