Connect IQ App hangs when updating apps

Lately, the Connect IQ app on my iPhone has been hanging during app updates - it just shows "Updating" indefinitely, even though the app does eventually update. This happens not only with my own app but also with other CIQ apps I use.

Is anyone else experiencing this issue?

  • I ocasionally experience same issue on Android and recieve complains from users that this is happening. Was asking for troubleshoot instruction from garmin with no response. Would love to see some step by step guidance published by garmin in order not to waste time on supporting users with troubles I dont control.

  • With my Connect IQ App the issue resolved itself recently. No idea what changed ...

  • I keep getting complaints from users who think that this update problem via GC IQ is related to my Edge data fields. I keep having this problem myself.

    I have found a way to end this eternal queue and advise my users to do the following:

    This is a problem with the mobile app GC IQ.

    Do the following:

    Turn off your Edge

    Close the app GC IQ on your phone (see attatchments how to close!)

    Turn on your Edge

    Run the „normal“ Garmin Connect on your phone

    Let the Edge sync with the GC

    Turn on the app CG IQ and it will boot from the scratch.

    If necessary do the whole process a second time.

    To close an app:

    https://support.apple.com/en-us/109359

    https://support.google.com/android/answer/9079646?hl=en

  • I keep getting complaints from users who think that this update problem via GC IQ is related to my data field. I keep having this problem myself.

    I have found a way to end this eternal queue and advise my users to do the following:

    For me, the issue wasn’t that severe. The updates still went through successfully, and when I exited the update screen in the Connect IQ smartphone app and re-entered it, the entry had disappeared.

  • When this happens, then all this doesn't help in case of my fr965 and android apps

  • I am not experiencing this personally (due to no updates required for a while), but i am getting a lot of feedback from Users, who assume it is my app that is causing the problem. My guess is it is intrinsically linked to the various server gremlins Garmin have been having over the last few weeks. I'm hoping they have taken their eye off the ball recently because resources are working on other changes e.g. forcing the use of SDK 8.1 etc.. - I like to think positively :-)