Upload issue to Apple Health

[JohnV235]

Nightguard has started uploading 54 entries for every second to Apple Health. Example: at 4:45 AM it sends the same glucose reading 54 times. Then at 4:45 AM it will send the reading 54 times. Then at 4:46 AM, etc. Totally messed up using Apple Health for my glucose. Any ideas?

[dhermanns]

Would be helpful what versions you are running.

[JohnV235]

Thanks - I'm new to this. Version 3.8.1.831

[dhermanns]

This is the latest App-Store Version. @sebdei could you have a look?

[sebdei]

If I remember correctly, duplication handling is done by apple health itself. Since I'm not using the App anymore, it would be nice if somebody would approve this bug. In any case I might find some time during the next few weeks.

[superevr]

First time setting up Nightguard and syncing to Apple Health. I'm really happy to have this functionality to put more of my information in one place. This is very helpful, especially when looking up historical changes and trends.

Unfortunately I also came across this bug. Similar to the first post, Nightguard generated dozens and dozens of duplicate entries for readings. For example, one of the synced historical records for Jan 26 at 5:50:23 PM appears in the Apple Health Recorded Data 56 times. That is, Same glucose, same date (to the second), same source, and nearby "Date Added to Health". (From Jan 26, 2024 at 6:17:55 PM through 6:17:56 PM)

This doesn't happen always, but it certainly floods Apple Health with duplicate data. I don't think Apple Health de-duplicates the raw data. But it will de-duplicate the information from two different apps before it displays it in a chart.

This is version 3.9.1 from the app store.

[superevr]

If it helps, the data is syncing from the Gluroo API, which is populating data for Freestyle Libre 3 via Libre Link Up.

[Parke-Bench]

Same issue here, data coming from GluRoo’s LibreLinkUp connection to my Libre 2.

Love the NightGuard app and having my BS nums on my Apple Watch, but I had to disable the HealthKit integration because it was flooding my history with thousands of readings every hour.

I’m not super experienced with iOS programming but I do have an Apple Developer’s Licence, and am a fairly experienced programmer in general, so if anyone wants to point me to the “likely culprit” code in the repository, I can poke around and do some diagnostics.