/build/static/layout/Breadcrumb_cap_w.png

Chrome manifest file - required value name is missing or invalid

Hi All,
I have combined two manifest.json files together using this page and it validates fine using JSON Editor Online and some other online validators.  The problem I have is when I am trying to import the package into Chrome Developer Mode.  I click the link to load an unpacked extension.  I then receive the message "required value name is missing or invalid"
I will include the json file here for people to read

{
  "name": [
    "itninja",
    "Print this page"
  ],
  "version": [
    "0.1",
    "1.1"
  ],
  "manifest_version": [
    2,
    2
  ],
  "minimum_chrome_version": "37.0.0.0",
  "permissions": [
    "webview",
    "power",
    "storage",
    "videoCapture",
    "geolocation",
    "pointerLock",
    "system.display",
    {
      "fileSystem": [
        "write",
        "retainEntries",
        "directory"
      ]
    },
    "tabs",
    "http://*/*",
    "https://*/*"
  ],
  "app": {
    "background": {
      "scripts": [
        "js/foam.js",
        "js/cab.js",
        "config.js",
        "background_main.js"
      ]
    }
  },
  "default_locale": "en",
  "icons": {
    "128": "img/128.png"
  },
  "description": "Adds a print button to the browser.",
  "background": {
    "scripts": [
      "background.js"
    ]
  },
  "browser_action": {
    "default_title": "Print this page",
    "default_icon": "print_16x16.png"
  }
}

The reason behind this merge, I have to build a kiosk chrome (I am using Chrome App Builder) for a particular website.  It needs to have either IE or Chrome and has to use Java 1.6.23.  Because of the old java requirement, I have to use Chrome 41 or less, (I am using chrome 39) it is going to be Thinapp'd.  The problem with Kiosk, it has no print function.  The above should (fingers crossed) include a print button in the limited app.
All the files are in the scripted locations.
I have been pushing through this print issue most of the day. 
Any help is a big thanks.

0 Comments   [ + ] Show comments

Answers (2)

Answer Summary:
Posted by: dunnpy 8 years ago
Red Belt
0
As there are no takers on this question I thought I might offer some 'general' comments :)

Do the two JSON manifests function independantly and correctly before the merge?

Does it work on the very latest version of Chrome?
I'm thinking there might not be the functionality in Chrome 39 to set this correctly. Maybe try Chrome 41, if that's the latest version you can go to.

If still no joy, can you break it down and add parts of the manifest and test, until you reach a point where you get the error again? It may help to identify where the issue may be occurring

You've probably done all of this already, but it's sometimes good for someone outside of it all to give a different perspective.

Dunnpy

Comments:
  • Hi Dunnpy,
    I have tried the two manifest files separately they both work.
    I have not tried to run the manifest on 41.
    I had thought the manifest would have to work as a complete module, two names, two versions etc... but I could start with each section and work down the list in pairs.
    Thanks for the eyes, I will try your suggestions in the morning. Just have to find an archive somewhere to D/L 41.
    Also, I didn't mention in my original post, I was using Chrome 64bit enterprise.
    Thanks - Tempril 8 years ago
Posted by: Tempril 8 years ago
Purple Belt
0

Top Answer

I have tried to merge the two files together, but as soon as you place two responses under one title, the second then becomes the response for the input.  From what I have discovered, there is no way of combining the two files to make one, or giving a print button in Chrome kiosk.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ