Users not being able to update app to latest version, connect IQ pushes/installs old versions

Yes, I experience the same on an almost daily basis (well every time I upload a new version). There are a few "phases":

1. the new version (n+1) seems to be available on the web connect iq store, but still not in the mobile app

2. in the mobile app it displays the newest version and it enqueues the update

3. in the mobile app it looks as the latest version is already installed, but on the device it's still the old one

4. sometimes the mobile app enqueues and updates the app again and again (kind of endless loop) even though it already displays it to be the oldest version, and still it's not the oldest version on the device.

5. usually either after a long time (can be a day or more) or sometimes triggered by uploading another "version" (even if there's no change in the code, except the version I type in: n+2) the latest (at least n+1, sometimes even n+2) version is finally installed on the device.

This is so annoying that 1st I started to add the version number (something I update every time I make a new build for a new upload.) to the code and display it somewhere in my app. Either in the bottom of the settings or somewhere else. For data fields, especially for betas I even change the title to include the build (and if my versions are x.y.x then I usually add the next number from the store: x.y.z.(n+1))

Hi Flocsy, Yes, I also display the version number in the app. That is also how me and some users found out that they arent up to date ("the stores shows 3.5 but the app shows 3.3"). The question remains though: how to get them upgraded? At first I thought it was because their firmware was not up to date, since the auto sdk update forced me (https://forums.garmin.com/developer/connect-iq/f/discussion/407332/forced-to-build-with-sdk-8-1-0-compatibility-issues) I run into that problem; users need to update the firmware. 

But some users are reporting the firmware is up to date, they still cant see my latest version. Any ideas? I guess I can try to recover older compiler.json so I can move back to SDK 7.x instead of 8.x which I got forced to after the connect-iq-sdk-manager auto updated my compiler.json.

Any chance you, or anyone has a zip of devices with compiler.json that I need to be able to built with 7.x SDK as well? At least my users could than upgrade again.

To get an update, you have to run the CIQ Mobile app for the device or use Garmin express.  In both cases there is a a setting to auto update, so make sure updates are enabled.

I'm not doing these compiler.json changes. It might result in other problems.

Sometimes uploading "another version" (same code) helps. But I suspect that there are multiple bugs that play here. This one is probably in Connect IQ app.

Over a few days I updated a number of apps for the new forerunners and my devices didn't get the updates until I opened the CIQ mobile app.  In one case I had auto-update off, and I could see there were pending updates that I could then update manually.

I think many users don't open the CIQ mobile app unless they want to install a new app of change settings so the updates don't get sent as soon as expected.  Things were faster when GCM installed the updates vs how it works now with the mobile app

jim_m_58 said:

To get an update, you have to run the CIQ Mobile app for the device or use Garmin express.

Michael said:

In other words: when they update the app from Connect IQ, Connect IQ is not pushing the latest version.

There has been an issue where apps can be stuck as "queued" in the mobile app, and a work-around I suggest is powering off both the garmin and the phone and then turning both back on.  This is nothing new and has been the case for a long time,

The other thing that can be tried is to use Garmin express.