This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Connect 4.46.0.24 stopped to synchronize data with iOS

After last update on Aug 18 Garmin Connedt stopped to synchronize data with iOS. Any ideas how to fix it ?

  • Same symptoms as others here, all was working fine, then stopped syncing to health, only consistent solution is to restart the phone, then it syncs, but only once.

    I am on iOS 15 Beta - so I had assumed it was that, but looks like others on standard version have the same problem

  • Greetings

    I am also having this issue. Connect app *does not* transfer data to the Apple health app unless I do my workaround. Connect app does sync with my garmin device, and data shows in my app. As it also gets heart bpm data every two minutes (amongst several things) I check that metric in order to know if it's syncing or not from the health app main screen, but there several more ways to check if it's syncing, and when did stop syncing.

    First, my workaround. What I do is go to the settings app. From there, Health > [last option] > Connect and there I turn off permissions to write data to health app. Then I "kill" Connect, and open it again. Then I go back to setting and turn on permissions to write data to health app. I again kill the Connect app, then open it again. Simply reseting the iPhone does not work for me every time, and this procedure is faster.

    Unfortunately, this workaround only allows  syncing data the moment you do the procedure, but it does not solve the problem, because the syncing stops just after the first sync is done. I am doing this *every day* for almost a week now.

    My setup is as follows:

    Garmin Vivosmart 4

    iPhone 7

    IOS 14.7.1

    Connect 4.46.0.24

    My hunch is that something triggers the app to not write more data to be available for the health app, or is some problem with the procedure to do that. If this was old linux, I would check crontab.

  • Hello all.  This issue appears to be resolved in Garmin Connect update 4.47.2.2.  If you are still experiencing this issue after updating to that version of the Garmin Connect mobile app, please start a new thread.