You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Loop failure as a result of signal loss in "update_dev_to_3.14.5" #2501
Expected behavior
An alert-message appears on the phone. When unlocking the phone and opening the Loop-app, it shows "Signal-loss" in the pod-section in the upper-right corner. This is restored within seconds.
Screenshots
Phone
Hardware: iPhone 15
OS Version: iOS 26.6
Loop Version
Version Number: 3.14.5
Repo: mdhaan69/LoopWorkspace
CGM
Device: xDrip4iOS
Manager app: [e.g. Dexcom App, Spike]
Pump
Manufacturer: OmniPod
Model: Dash Atlas
Firmware version:
Additional context
Add any other context about the problem here.
Just to be complete: I'm using xDrip4iOS customization with xDrip4iOS version 7.0.0 as CGM and this all worked like a charm in 3.14.4!
Just updated my Loop to "dev" (3.14.5) with xDrip4iOS as CGM and unfortunately Loop fails again, because the connection with the Omnipod DASH failed again after 20 minutes.
Now I replaced the xDrip4iOS for the native Freestyle Libre CGM in Loop and Loop did not report any issues after 20 minutes.
This may confirm Marion's assumption that the issue was related to xDrip4iOS.
Have you been able to find anything regarding xDrip4iOS that may solve the issue in one of the future version?
I really hope I can keep using xDrip4iOS as I have been used to, as it provides so much more insight regarding the past couple of hours.
Activity
mdhaan69 commentedon Sep 8, 2026
Just to be complete: I'm using xDrip4iOS customization with xDrip4iOS version 7.0.0 as CGM and this all worked like a charm in 3.14.4!
Just updated my Loop to "dev" (3.14.5) with xDrip4iOS as CGM and unfortunately Loop fails again, because the connection with the Omnipod DASH failed again after 20 minutes.
Now I replaced the xDrip4iOS for the native Freestyle Libre CGM in Loop and Loop did not report any issues after 20 minutes.
This may confirm Marion's assumption that the issue was related to xDrip4iOS.
Have you been able to find anything regarding xDrip4iOS that may solve the issue in one of the future version?
I really hope I can keep using xDrip4iOS as I have been used to, as it provides so much more insight regarding the past couple of hours.
marionbarker commentedon Sep 9, 2026
The fix for this was identified and will be in the next update to dev.