Duplicate entries in Apple Health

Update.

Finally, I have numerous duplication of data:

— walking+running distance

— resting calories

— active calories

Records with activity as well as records for the day are duplicated. Duplication records for activity are posted with every sync of watch with Garmin connect app

Attached are records from Garmin connect and relevant records from Apple health

trux, part 2 of your post may have some merit, but if it has then it is rendered obsolete by the fact that Garmin has been promising customers fixes for these issues for a minimum of 8 months. And failed to deliver. Or if there were widespread reports of other OEMs having similar issues. There aren't.

Handing the task of developing the AH interface to someone inexperienced or incompetent would be forgotten, had the product been suitably tested and the failures identified before inflicting them on customers. It may have been excusable - if unprofessional - had Garmin released the integration in its poor state but acted quickly when customers started reporting the issues.

It is unforgivable that Garmin developed, released and have now failed to resolve the issues for months and months. As I said in my earlier post, I would be embarrassed if I was a manager there and this sequence of events had occurred. I certainly wouldn't be sat thinking I deserve customer trust and loyalty.

This may be a minor issue on its own, but I'm afraid is indicative of the widely discussed problems with Garmin's software, which undermines the undoubted quality of its hardware. 

lj50 said:

trux, part 2 of your post may have some merit, but if it has then it is rendered obsolete by the fact that Garmin has been promising customers fixes for these issues for a minimum of 8 months.

Sorry, I just tried to help by putting some light on the data, and make it clear where the problem exactly is. As for the way Garmin is handling the issue, I cannot help you in any way, being just a regular user like anyone else. And nobody else here on the user forum can influence it either. Turning up you anger and frustration against other users trying to assist on this forum, won't help anyone. You need to address Garmin, but the user forum is not the best platform for it, since Garmin employees only very exceptionally intervene in a very limited number of threads, and most likely will never see these posts.

Please don't misunderstand, I wasn't criticising your post or directing any anger towards you. I don't understand how it could have appeared that I was, but if it did then my apologies that you took it that way.

I was just pointing out that I have seen Garmin try to point the finger at Apple (if you see further down the thread, this is what some people have been told by the Support Desk) but I think that their track record on this issue removes their entitlement to do so. If they had responded and reacted and acted professionally, then they would be entitled to point out room for improvement in Apple's API. 

FWIW Garmin employees have intervened in a number of threads on this topic. Specifically, telling us that they are "fixed" and closing the thread. Only for new ones to be created by users because the issues are not fixed.

I'm not angry at anyone for this issue, it's fairly trivial, but I am frustrated by any company that has the the level of contempt Garmin gives the impression that it has for its customers.

lj50 said:

I wasn't criticising your post or directing any anger towards you.

It's all right, I did not take it personally. What I meant, it won't help anything if you complain here about the way Garmin handles the issue, because the users cannot help you with it, and Garmin won't see it. You have to complain to Garmin, if you want to be heard.

And to review it accordingly in the AppStore. Potential users should know how Garmin handles their software development.

I’ve been in fairly active dialogue with Garmin over the past 9 months, and have escalated my complaints (the first timo I have had cause to do so with any organisation) but I do think it’s is helpful to reiterate the points on here also. If it encourages user to get back in touch with Garmin when they’ve previously been fobbed off with “it’s an Apple issue, contact them” (which it seems many have had as the first response) then it is another user adding to the pile to support tickets on the issue. That’s how we get heard. 

I've started tweeting to major tech sites for them to cover these issues. I suggest you do the same. Also, remember to 1* them on the app store and mention these bugs in the review.

Nice! I didn't think about it. I wouldn't normally advice to do the same, but since Garmin is treating us like fools, pretending it's Apple's fault, I think that's fair, and the just thing to do.