Connect IQ wants to upgrade 15 apps that are already on the latest version

Am I the only one experiencing this? I open Connect IQ Android app (2.22), it syncs, and then it displays that there are 15 upgradable apps. I didn't check all of them but most of them are already on the latest version, including my own datafield... BTW this is not the 1st time it happens, but usually it was 2-3 apps, not 15 (out of 30 installed)

By guess is that the bug is in the backend

  • What and why this happened will become clear when the new devices are announced.  Until then, Garmin won't say a word about it as the device(s) haven't been announced.

  • Still seems odd to update all IQ apps daily, this must also be a waste of resources on the Garmin servers.

  • in other words this is another "bug" (bad design) on Garmin's part, where they waste their own resources and millions of user's time and bandwidth to update literally no changes to devices that don't need the supposed changes...

  • No, not at all.  Real example. The fr230 and fr235 were introduced and available in the store.  Later, the fr735 was about to be announced, and an auto-migration occurred to add that as a device in the current apps so nothing had to be done to support apps as user started to get the 735 devices.

    As a dev, you can turn off auto migration for your apps, and as a user you can turn off automatic app updates for all your apps.

    There IS a change for your app, but you didn't make it.  New devices (part numbers) were added..  An IQ file is a .zip file.  If you look at the manafest.xml in the iq file, you'll see the devices the app supports.  Auto-migration adds the new device(s) part number(s) without you doing anything.

    It's really not that much different than if you yourself adds a new device to your app, with no change to the code.  All the users of that app get the update even if not a single byte code has changed for their device.  This is the same but on a larger scale.

    I guess you've never seen an auto-migration before.

  • Jim, what happens if after the auto migration I upload a new update that doesn't include the new devices in the manifest? Are they still available due to the initial auto migration or should I be aware of it in order to include these devices in future updates?

  • It's best to wait for CIQ to add the new device files, as yes, if you update the app after auto-migration, but before you actually add the new device(s) to your app, your app(s) won't be available for the new devices.

  • in other words this is another "bug" (bad design) on Garmin's part, where they waste their own resources and millions of user's time and bandwidth to update literally no changes to devices that don't need the supposed changes...
    No, not at all. 

    I don't think anyone is disputing that auto-migration is necessary / actually does something, given the design of the CIQ store / ecosystem, I think he's just saying he doesn't like the design.

    For example, when a new model of iPhone comes out, owners of existing iPhones aren't prompted to update all of their apps. Pretty sure the experience in the Google Play store is the same.

    One could easily imagine a world where the Garmin CIQ ecosystem acted in a similar way (regardless of implementation details). For example, if the back end is smart enough to know that auto-migration is necessary, it could also be smart enough to not push out an auto-migration version to existing devices which don't need it.

  • The reality here, is this is how CIQ has worked for 7-8 years, and it does work.  And auto-migration isn't that common anymore, and changing the design at this point isn't needed.  I'd rather Garmin spent their time fixing bugs!  Slight smile

  • For what it's worth those devices were leaked on May 12, although ofc the mods in these forums wouldn't have allowed anything to be posted here about that.