Package is invalid. Details: 'Could not decode image

3,349 views
Skip to first unread message

Chris McMichael

unread,
Feb 12, 2015, 4:29:18 PM2/12/15
to chromium-...@chromium.org
Hello, I am trying to upload an extension to the chrome store and I am getting the following error message when I try to install the extension:

Package is invalid. Details: 'Could not decode image: 'logo.png''.

The unpacked version works.
And the packed crx version works.
But trying to download from the chrome store does not.
Please help! Thanks in advance!

Here is what my package.json looks like:
{
  "name": "",
  "author": "",
  "description": "",
  "version": "1",
  "manifest_version": 2,
  "icons": {
    "16": "app/img/logo-16x16.png" ,
    "48": "app/img/logo-48x48.png",
    "128": "app/img/logo-128x128.png"
  },
  "browser_action": {
    "default_icon": {
      "19": "app/img/logo-19x19.png",
      "38": "app/img/logo-38x38.png"
    },
    "default_title": ""
  },
  "background": {
    "scripts": ["app/js/browser-action.js"]
  },
  "content_scripts": [{
    "matches": ["*://*/*"],
    "js": [
      "app/js/loader.js",
      "app/js/stuff.js"
    ],
    "css": [
      "app/css/stuff.css"
    ]
  }],
  "web_accessible_resources" : [
    "app/index.html"
  ],
  "permissions": [
    "*://*/*",
    "tabs",
    "background"
  ]
}

Antony Sargent

unread,
Feb 12, 2015, 5:05:56 PM2/12/15
to Chris McMichael, Chromium-extensions
Did you mean manifest.json (not package.json)?

Usually that error message will only appear for images that are referenced somewhere in the manifest.json (typically in either the icons or browser_action/page_action sections, although  there might be other places too). Any chance in a previous version of your extension that you uploaded to the store you were referencing just 'logo.png' and you have since fixed that and uploaded a new version to store? If so then it might just be that there's a delay between publishing a new version and that version becoming live, as various automated checks run on the source and then it propagates to the download servers. 
 

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/dad4cb8b-ebb1-42fa-b3a1-66ed005eb16e%40chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

Chris McMichael

unread,
Feb 12, 2015, 5:12:29 PM2/12/15
to Antony Sargent, Chromium-extensions
OK it seems to work now. I think I was just getting impatient and needed to wait for the new extension to fully publish. Thanks for the reply!
Reply all
Reply to author
Forward
0 new messages