Unable to Upload Zip file with Packaged App to Chrome Web Store

[Carl]

I tried packing the extension manually and there was no problem. I do
have a key in the manifest and also a key.pem file in the top-level
folder (along with manifest.json). I did try packing the App via
chrome:extensions and there was no problem with that.

When I attempted to upload via the developer dashboard, I was
initially unable to upload at all; when I tried it accepted my file
name but then, without showing any progress bar for uploading,
immediately showed a message "An error occurred: please try again
later." Above this it read "(unable to read file).

I then logged out and logged back in again. After that, my file
uploaded, inasmuch as the progress bar showed progress up to 100
percent, but then the page just hung there with the small circular
busy bee just marking time and no confirmation
page. There was no error message, and after at least eight minutes
had elapsed I gave up and tried again. The same thing happened two
additional times.

This all happened in the course of about one hour of wall time, so
perhaps there is some kind of transient problem with the site? Is
this a known issue? Can someone make a suggestion as to how to
proceed?

[Carl]

Here is an update:

Because Chrome had already crashed on my PC prior to the above, I
performed a cold boot and tried again, with identical (unsatisfactory)
results.

So, while entirely cognizant of the ironies involved, I decided to try
Firefox for my upload. This went much better!

Specifically, I got a meaningful error message this time that told me
I could not include a key value in the manifest.

"(Server rejected)" at the top, and at the bottom:

"An error occurred: 'key' is not allowed in manifest."

OK, that is something specific. I'm upset at not being able to
include a key, because I want to keep my specific app ID, but that's a
separate issue. So, I removed the key value from the manifest, and,
after being told I needed a 16x16 icon (which I had thought was
optional) and providing it, the upload succeeded!

So, I would recommend trying Firefox to anyone who is having upload
difficulties with the present developer release of Chrome.

[PhistucK]

The manifest "key" issue is not an issue.

When you include the "key.pem" file in the top level directory of your ZIP file and upload it as a new extension (meaning, do not upload the file into an existing entry), the gallery will just add the right "key" to the manifest and your ID will be persisted.

In other words, the gallery is in charge of adding the "key" to the manifest, based on their generated private key, or based on your supplied private key. And of course, the "key.pem" file should only be provided once - when you first upload your extension. Whenever you update your extension after that, there is no need to include it.

You probably knew some of that, but it is always good to remind.

(Same goes for apps, sorry, I just realized that you were asking this in the apps groups.)

@Aaron\Sam -

This issue of not being able to upload with Chrome was heard not a few times recently, can you, please, check it?

And by the way, I also find the required icon (and screenshot!) annoying. What if I just want to upload an extension? Why do I have to start thinking about its graphics? some extension authors are only coders, not designers and do not have any designers at hand.

☆PhistucK

[Carl]

I had been uploading both key.pem and the key value in my manifest,
but evidently the belt got tangled up in the suspenders, so taking out
the manifest key was exactly what I did yesterday, leaving the key.pem
file, and therefore the correct key should now have been generated,
which is gratifying to know.

I did not know that subsequent uploads could omit the key.pem file, so
thank you for that information, as well. I presume that this would
then prevent the key.pem file with its private key value from
appearing in the CRX files that are distributed to customers, provided
that at least two uploads had been performed prior to the release.

A minor point: If someone (you know, one of those perfect programmers
who never makes mistakes and whose work can never be improved) were to
upload *just once*, including the key.pem file, would the Chrome Web
Store *remove* the private key file prior to zipping up the CRX and
sending it out to the world? I am not that practically-perfect
person, but you might want to look into that issue because once the
store goes live, a programmer's very first upload (with key.pem) may
become instantly available to the hungering mobs. Also, a less-than-
perfect programmer might inadvertently leave the key.pem file *in* the
top-level folder on *subsequent* uploads, and so I would hope that
this would be removed by the Chrome Web Store in that case, as well.

The icon requirement didn't bother me at all, although I can see how
some developers might find it to be a nuisance.

Well, off to explore what the Web Store means when it says that
browsers other than Chrome are supported! This should be
interesting. I will probably have some serious questions about that
(like, what will the base URL be for such browsers, how will the app
be invoked, and so on). As always, will be relying upon the excellent
support of those monitoring these lists.

C.

On Nov 26, 1:14 am, PhistucK <phist...@gmail.com> wrote:
> The manifest "key" issue is not an issue.
> When you include the "key.pem" file in the top level directory of your ZIP
> file and upload it as a new extension (meaning, do not upload the file into
> an existing entry), the gallery will just add the right "key" to the
> manifest and your ID will be persisted.
> In other words, the gallery is in charge of adding the "key" to the
> manifest, based on their generated private key, or based on your supplied
> private key. And of course, the "key.pem" file should only be provided once
> - when you first upload your extension. Whenever you update your extension
> after that, there is no need to include it.
>
> You probably knew some of that, but it is always good to remind.
>
> (Same goes for apps, sorry, I just realized that you were asking this in the
> apps groups.)
>
> @Aaron\Sam -
> This issue of not being able to upload with Chrome was heard not a few times
> recently, can you, please, check it?
>
> And by the way, I also find the required icon (and screenshot!) annoying.
> What if I just want to upload an extension? Why do I have to start thinking
> about its graphics? some extension authors are only coders, not designers
> and do not have any designers at hand.
>

> ☆*PhistucK*