App publishing not working?

Does it show on your "uploaded apps" page?

did you try uploading from that page (the blue "upload an app" button) or using the "upload an app" link at the top?

Hello and thanks again for the quick and precise reply. It turns out my app has been uploaded, despite the error message received.

Of course, I used the submit button on the bottom of the page.

One other thing to keep in mind. While the app is waiting for approval, you will probably get an error if you try to download it yourself. This is a known bug with the store that's been there for a while. After approval, it will work fine.

When you update an app, there is no wait for approval, so you can download right away.

This bug has been at least partially addressed. You shouldn't see an error on the store when attempting to download pending apps, but there may still be an error during the syncing process with Garmin Express or GCM. The store team is aware of the issue and is working on a fix.

Hello Connectors,

I am adding to this thread because - though my experience is different than that below - the title of the thread is general enough to do so.

ITEM ONE: The error I see when I try to upload a new version of my watch face *.iq file is as follows (I know the upload page asks for a zip - we will get to that in a moment - but I was able to upload the previous version of my watch face as an IQ file so, hey, this should work right?)

"The following errors were detected in your app file
The updated version should be different from previous versions."

My updated version is clearly newer and different than the previous version. I would know; I worked on it for hours :).

ITEM TWO: When uploaded as a .zip file I see this

"The following errors were detected in your app file
The uploaded file contains invalid paths. : CleanWatchFace.iq <-- No idea what this means
The uploaded file does not contain at least one 006-* folder. <-- What the heck is this folder?

As always ladies and gentlemen, your expert advice is welcome.

Thanks,
Jeff

1) I've seen that, but it has to to with the version number, and not the .iq file.
If you already have a version 1.0 in the store, you get it if you try to upload another .iq file as version 1.0, for example (try using something like 1.0a if you get this error). It has to do when the version number you enter right after you specify the .iq file and nothing aboit the .iq itself.

2) The .iq file is actually a .zip file, but with the .iq extention. If you rename it .zip, normal zip tools will allow you to open it, etc. But I agree - The upload to the store should talk about .iq instead of .zip

For the errors, the first is that you have the .iq (a zip) within the .zip and it doesn't like that

for the second one, if you look at a .iq it's actually tree structure, with a directory per part number, with the .prg, etc, for each you support, and the 006- is how part numbers begin. It's saying it can't find any of the part number directories - so no supported devices, in other words.

805

Hi Jim,

First thanks for the tip on .iq files actually being .zip files. With that information in hand, I was able to view the tree structure you mentioned and confirm that the 006- folders exist.

As far as file versions are concerned, when I submitted version 1 I entered "1.0.0" on the upload page. With version 2, I entered "1.1.0". Still the upload tool did not like this. The only other place where a version string comes into play is in the manifest file:

<iq:manifest xmlns:iq="www.garmin.com/.../connectiq" version="1">

I would change the string here but since this is an auto generated file I thought it best not to do that.

As always, thanks

Jeff

<iq:manifest xmlns:iq="www.garmin.com/.../connectiq" version="1">

Jeff

That's the version number used by the manifest file itself, and NOT the version number of your app. You shouldn't change it. You should rarely hand edit the manifest file at all (with eclipse, you don't need to at all)

The only version number that matters is what you enter on the form when you are uploading an app to the store, and that can be anything you want.

I suspect that with the errors you were getting, you were using the same version number you used before that resulted in an error. if 1.1.0 didn't work, how about 1.1.1 or something?