Complete

CIQSTORE-2349

Fixed

Bizarre app versioning error - need to upload twice to update - Connect IQ developer

Hi,

This is what I am seeing today:

1. Compile new version of app ("0.0.39")

2. Upload newly compiled app specifiying correct version number ("0.0.39")

3. Update page with what's new ("0.0.39 : Fix partial screen layout with Fenix")

Then, when I go to the app store:

1. I see my "what's new" correctly stored with Fenix bug detail

2. I get version 0.0.38, and Connect store tells me latest is 0.0.38

So I figure something went wrong with upload...

1. Go to connect "upload new version" >> Garmin tells me 0.0.38 is latest upload

2. Upload version 0.0.39 again

3. See an error in Garmin connect "The following errors were detected in your app file

  • The updated version should be different from previous versions."

4. Check in Connect store - page and app has now updated to correct version - 0.0.39

At no point during this process have I had to do any recompiles or similar. The same file uploaded twice in each case. I have verified this across all 9 of the related DataField dials that I uploaded this morning.

Shome mishtake shurely...

9635560

  • This bug was already reported about 2 or 3 months ago... Garmin doesn't do anything to fix this issue.

    ...and the worst of all the connect and the connect iq app behave differently. That means the connect iq store app displays the previous uploaded version.

    This leads to an update loop if a user enables the automatic update option.

    ...the best of all this option is enabled by default.

    happy updates @ all

  • in reply to 9635560

    Yep, I agree it's a bug. I just disagree that the workaround is to upload the app twice.

  • in reply to flowstate

    Still a bug, though. 

    And the manifest info displayed in the upload form that is intended to allow you to verify your upload is previous version. 

    Still a bug. 

  • I think this is happening to everyone, but I don't think you actually have to upload twice. I think the issue is you have to wait maybe 30 seconds to a minute for the new version to be actually fully reflected in the garmin store. Seems that the new version has already been stored on the backend, which is why the 2nd upload fails.

    I saw this when updating multiple (8) apps at once. There was a noticeable lag between an upload and the new version being reflected in the store -- but at no point did I have to re-upload an app. I just waited.

    Still a bug, but not exactly as described.