Loop "missing data: glucose data not available" but dexcom working

[mitchellhenke]

Discussed a little bit here where Loop shows Missing data: Glucose data not available, though the Dexcom app shows no gaps and appears to otherwise be functioning fine.

It is mentioned by @Kdisimone in the thread that this may be due to an iOS resource issue, but I was hoping there would be a way to make Loop reconnect? Someone else suggested that it's due to Apple Health lagging, but it never seemed to catch up in my case.

Looking back, Apple Health has no Glucose measurements from Loop during that time, but Dexcom shows no interruptions. I can get back into a working Loop state when it happens by toggling Bluetooth on and off.

I have set up Amplitude so I'll have that if it happens again in the future, but is there anything else I could do to help narrow down where the issue may be?

I’m using Dexcom G5 and Dexcom app and have seen the issue on Loop 1.9.2.

[mitchellhenke]

This happened again last night. Issue report uploaded in this gist: https://gist.github.com/mitchellhenke/089054cf1f92eed5878ba1a102723ac6

As before, Apple Health doesn't have glucose data for the time period. This time starting around 2am:

[francesc0-cgm]

It happened to me too two times in 5 days

[chelle0207]

This is not happening to me. It has in the past.

I’ve had a lot of Signal loss issues and other Bluetooth issues with Dexcom. My chats with the reps have resulted in many recommendations to reboot my iPhone nightly. I’m not great about doing it nightly, but I do it about once a day. I think that helps a lot. This seems to be an issue with Dexcom not connecting to the Internet.

At night, I run my Nightscout app, my Garmin app, Dexcom G5 app, and Loop. I don’t let my phone automatically update anything. Those kinds of things keep me connected pretty well. And I run everything on WiFi.

[jeremybarnum]

We have the 2 am problem (loop red, glucose data not available) but checking HK records, there is no gap visible which is weird. We are following FB troubleshooting steps and will report back. Starting by deleting server from loop.

[jeremybarnum]

Deleting dex server from Loop did not work. One again a 2 am drop that persisted until wake-up. Interestingly no NS data uploaded during that period. Need to understand what that could indicate - more of an iPhone issue than a Loop issue? which is consistent with the idea that it's contemporaneous with iOS12. HK BG records are weird - Dex is the source but then Loop records twice, and then stops and there is no record of either app recording BGs - and this begins around the time that loop seems to have turned red (Loop is the blue icon).

I probably don't understand the Dex backfill logic that well and the HK "priority" logic, if any. On wakeup, it was impossible to get BG back despite standard troubleshooting - BT toggle, force quitting Loop, confirming that Dex app is receiving BGs, which it was. I did note that some very old, since deleted, versions of Loop still showed up as being allowed to read from HK.

I disabled that, but it makes me wonder. Only way to get back to green was to add back Dex server, and have it go to the cloud. During the day cloud icon is gone. This is iOS 12 with a 1.5.7 modified version. We will upgrade to 1.9.3 over the weekend but this is definitely a new problem that seems contemporaneous with iOS12, so while it will be nice if 1.9.3 solves it, it's not clear why that would be the case, unless it's something very subtle about the interaction between the new rileylink frameworks in 1.9.x, the heartbeat, the sniffing of the transmitter signal, and iOS12. Will try turning off WiFi tonight.

LoopIssueReport.pdf

[kenstack]

@jeremybarnum you need to check with @Kdisimone or @ps2 , but if I look at your issue report I think loop had crashed until moments before you sent the report (ie you interacted wtih the app). The launch date of the device manager is 26 seconds before the report date. That indicates that after a crash it didnt restart, which used to be a problem that @ps2 had fixed but i cant remeber if that was in 1.5.7 or after (I fought it for a long time but after he made some adjustments to how data gets saved to HK I think all was good). I believe it restarts based on the transmitter heartbeart, so if the dex app is crashing there is nothing to restart loop with (again check with the experts). If NS didnt have data then I assume share didnt have data so likely its a dex app issue, but that is just my opinion. We just upgraded my sons phone to ios 12 - first night the dex app crapped out after the ios 12 upgrade. Last few nights he takes the password off and leave the dex app up on the screen all night - rock solid last few nights - but that is just a few data points. check the analytics logs to see if you can see any crashes around that 2 am timeframe - dex app, loop, watch etc.

[jeremybarnum]

Thanks @kenstack, very helpful, will do. I also just noticed that even though I thought I had gotten rid of all the old apps that might be conflicting (a thing that I believe was also fixed in 1.9.x ) there was one. So we've deleted that.

[Piotras625]

I got same issue. I am using miaomiao and libre with spike, loop version 1.9.3 katie. Ios 12.0.1 Get missing data but after I open loop it comes straight on. Been doing I think everything now but no luck. Just wondering to clear my phone and start from scrateches.

[jeremybarnum]

FWIW we tried removing screen lock and having the Dexcom app up and that worked last night.

[chelle0207]

Also, FWIW, (again, I don’t have the issue of Loop turning red), I typically use my iPhone 7 at my bedside to alert me for hypo and hyperglycemia at night. I leave my phone on the Nightscout app either Nightscout X or the original Nightscout app), with the “screen lock override” on (so my phone screen doesn’t lock).

On Wed, Oct 24, 2018 at 16:47 jeremybarnum ***@***.***> wrote: FWIW we tried removing screen lock and having the Dexcom app up and that worked last night. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#837 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIjz3Ix7RW6xGjJ9flhZzKipdAyqzB6lks5uoNHWgaJpZM4Xi08b> .

-- Sent from Gmail Mobile Please excuse typos & brevity.

[Piotras625]

Just to update. I also kept phone unlocked over night and loop worked great :)

[francesc0-cgm]

Which phone do you have? I have an iphone se

[Piotras625]

I have Iphone 5s. Unfortunatelly daughter is in school and we lost already connection as phone was locked all the time

[jeremybarnum]

Probably worth having everyone clarify their platforms and versions to clarify whether this problem exists in 1.9.3 or is fixed? @Piotras625 post would suggest the problem still exists but if so why is everyone not seeing it, and @kenstack seems to think some recent improvements should have fixed it. Good news is leaving Dex open and phone unlocked seems to do the trick but that's not a proper solution. We are on iPhone SE with iOS12. UPDATE: I believe, but for reasons of branch management sloppiness I can't be totally sure, that the installed version is based on 1.5.2, with Loopkit 1.5.4 and rileylink_ios 1.2.2. Here it is - branch "1.5.2-x15-and-absorb-fix". Our version has been the same for months, but the problem arose after iOS12 update, although I can't definitely prove the causality there. We will probably update to 1.9.3 this weekend and we can't afford to try to reproduce tonight so I guess if the problem is gone in latest version, who cares. I'll report back.