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

Wrongly Closed topic: Distance sync to Apple Health still incorrect

has closed the thread below, saying the issue was resolved by 4.24. It wasn't.

https://forums.garmin.com/apps-software/mobile-apps-web/f/garmin-connect-mobile-ios/168597/incorrect-distance-syncing-to-apple-health-since-last-connect-update

See images.

Given the recent track record of poor software releases; in future, it may be better to ask your customers if the latest version has resolved an issue rather than deciding it has.

  • Yep, I saw this and just logged a new issue too. I also responded back to Garmin on the development ticket I had with them which also told me it was resolved.

    This is the new thread if anyone is interested:

    forums.garmin.com/.../incorrect-distance-syncing-to-apple-health

  • Ah yes, it looks as if we were posting at the same time. 

    Lets see how long it takes for either thread to receive a response... Support also told me today it was “fixed”, so I’ve sent them the same screenshots. Their previous story was that it was “nothing to do with Garmin Connect” and insisted that it was Apple’s issue. They haven’t answered how they could have fixed “Apple’s issue” with an app update, but either way, it’s not working. 

  • Given that you posted the issue was fixed only minutes after the release of 4.24; its frustrating that nearly a week on, you haven’t so much as acknowledged that you were incorrect in stating that. Any chance of an update or should we give up on this ever working?

  • We are researching why this similar issue is occurring. I apologize for the inconvenience and not commenting here sooner.

    As for closing threads, we do this to better manage the forum threads and many of the users that reported this issue previously are no longer experiencing the problem.

    In your experience, does this issue happen on days that you do not run?

  • In my experience it only occurs when you run. On a rest day of no running the distance is correct. 

  • Thank you for replying. 

    No, the experience I have aligns to other people reporting the issue. The discrepancy only happens on days I run. Essentially; it counts the run distance twice. That’s been the behaviour for the past month (prior to that the distances appeared utterly random). 

    Rather than fix this, as you claimed, 4.24 did introduce a new issue. Connect now deletes data in Apple Health from prior days. For example, the entry included in the screenshot above; it no longer exists. The immediately preceding day’s data is retained, then deleted. This is how the data looks now.  Everything since 26th of October deletes itself after a day. 

    I understand the desire to keep the forums tidy; but what you’ve actually done is add to the clutter because now we’ve had to open additional threads rather than replying to the original one... Why not simply ask in the thread “we believe this is resolved, please confirm this is the case. we will lock this thread in 7 days unless users advise that there has been no change”. 

  • Former Member
    0 Former Member over 5 years ago in reply to Garmin-Matthew

    Hi Matthew, same for me and reported by many others: runs have been syncing double distance to apple health since several months, walks are ok. The connect app data looks ok, it then syncs one single distance datapoint to apple health (which oddly gets distributed over the full 24hr of the day, no proper timestamp included, another dubious choice) but that datapoint is double the actual distance in Connect.

  • It happens to my apple health on days I don't run.