Acknowledged

Cannot upload to the IQ store/....... come back later

Hello, 

Is there an outage to the IQ store Upload APP facility..... I;'ve been getting come back later ever since the last maintenance period?

  • I didn't - I only saw down for maintenance after about 60 seconds of waiting, no file updated. I think they either have a time limit on the upload or a size limit or both.

  • Good morning  - I was wondering if there has been any improvement to the store upload megabyt limit yet, or is it still stuck at 20 something Mb ?

    I'm supporting over 90 watches with one of my apps, and because of this when the project gets compiled the annimation is re-made several times for several different watch sizes, which baloons the file size so that the store does not accept the upload.

    Has anyone else experienced this, or know what the filesize limit is precisely, or if Garmin will increase it to allow propper annimations?

  • What I see is if the iq file is over a certain size, you see the "down for maintenance" screen, but the iq file is correct, and the new version of the app can be downloaded.

  • For me, this was related to the file size. The Garmin store seems unable to accept files over a particular size. I was supporting over 20 watches and using an animation, so the file for my app was quite big, over 25 Mb. It never worked, so I gave up using animations.

  • Just to bump this, I'm seeing this error on app upload. Salt in the wound is that the error message says "Garmin is downed for planned maintenance", but that is certainly not accurate--unless Garmin is coincidentally doing planned deploys at the exact moment when I choose to upload an app, repeatedly. Slight smile

    Also annoying is that when the upload times out, it's unclear what state the store version of the app is in. The store version will show reflect the new version, however, if the upload timed out, did the bundle fully upload? How can that be verified?

    The only thing I can think to do, is repeat the upload, and hope it doesn't timeout again. This requires bumping the minor version which ends up with gaps in the version history which is a little annoying.