"Upload an extension or app (.zip file)" gives "Invalid package."

[John J Barton]

Evidently the instructions on assigning a chrome extension id are out of date:

  http://code.google.com/chrome/extensions/manifest.html#key

It instructs you to go to this page:

http://code.google.com/chrome/extensions/packaging.html

but that page seems pretty pointless: after creating the .crx file using the Pack Extension option, the resulting .crx cannot be loaded.

If you try you get this message:

"Extension error: Extensions, apps, and user scripts can only be added from the Chrome Web Store."

So I tried to use the Chrome Web Store to create a .crx just so I can have an id. I used zip on linux and I checked that the .zip file has manifest.json at the top level. But the upload fails with Invalid Package.

Any hints?

jjb

[Joshua Woodward]

when visiting http://code.google.com/chrome/extensions/apps.html you should notice the warning - 

"All content in this doc refers to the legacy version of packaged apps. Your legacy packaged apps will still work, but you won't have access to any of the new APIs. Check out the new version of packaged apps; otherwise, you're missing out!"

here are the new docs for packaged apps

http://code.google.com/chrome/extensions/trunk/apps/about_apps.html 

jjb

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.
For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.

--

Google+ - http://joshuawoodward.com/+

Twitter - @howtohtml5

[John J Barton]

On Tue, Jul 24, 2012 at 11:29 AM, Joshua Woodward <j...@woodwardmedia.net> wrote:

when visiting http://code.google.com/chrome/extensions/apps.html you should notice the warning - 

"All content in this doc refers to the legacy version of packaged apps. Your legacy packaged apps will still work, but you won't have access to any of the new APIs. Check out the new version of packaged apps; otherwise, you're missing out!"

here are the new docs for packaged apps

http://code.google.com/chrome/extensions/trunk/apps/about_apps.html 

Thanks, but I was not visiting that page and I am not creating  packaged app.

jjb

[Joshua Woodward]

Your right, I read that too quick, i saw "package" and went somewhere else with it

Which version of chrome are you running?

Also, code.google.com may not be up to date, try developers.google.com -  (i know some links back to code.google.com, weird)

https://developers.google.com/chrome/web-store/docs/publish 

[John J Barton]

On Tue, Jul 24, 2012 at 11:23 AM, John J Barton <johnj...@johnjbarton.com> wrote:

Evidently the instructions on assigning a chrome extension id are out of date:

  http://code.google.com/chrome/extensions/manifest.html#key

It instructs you to go to this page:

http://code.google.com/chrome/extensions/packaging.html

but that page seems pretty pointless: after creating the .crx file using the Pack Extension option, the resulting .crx cannot be loaded.

If you try you get this message:

"Extension error: Extensions, apps, and user scripts can only be added from the Chrome Web Store."

I discovered that this message is also incorrect. Extensions can be loaded using drag and drop from your operating systems directory-viewing application:

http://support.google.com/chrome_webstore/bin/answer.py?hl=en&answer=2664769&p=crx_warning

jjb

[PhistucK]

There is (or should have been) a "Learn more" link next to that message.

☆PhistucK

[John J Barton]

Yes, as I recall the link I posted was the Learn More link. Unfortunately it contradicts the message.
jjb