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
Describe the bug
My son’s loop crashes and will not stay up while I am close to him. If I walk away to another room it will stay up but still red loop. Says Omnipod dash has no signal. The pod before this one has same issue. Worked for 12 hours, then during the night about 10 pm it stopped looping and said pod signal failure. I have seen the time date off several times, since the time change. And I’ve checked his setting every time and the automatic time change is toggled on and set to New York eastern time zone. Tonight it worked great all evening until my son bolus a snack in his bedroom at 9:45, at 9:46 pod signal failure can be seen on the repost, says the “pod has disconnected from us” and another thing I think is related is the Dexcom share always says “internet server down” unable to share every time I turn on the WiFi on his phone. As soon as I put back on cellular beats, the share works again. So I have to leave the WiFi off completely for Dexcom to work. There is definitely some type of signal connection problem and I need help please. Loop Report 2024-04-11 03:36:44-04:00.pdf Loop Report 2024-04-11 03:36:44-04:00.pdf
Attach an Issue Report
Tap the Loop settings icon on the bottom of the screen, then tap Issue Report and attach it to this ticket.
It’s 778 pages long. I can try to email it directly but will not link here To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
I expect loop to not crash
Screenshots
If applicable, add screenshots to help explain your problem.
Phone
Hardware: [e.g. iPhone 15
OS Version: [e.g. iOS 17
Loop Version
Version Number: just finished new build last week because of connectivity problems with his last phone, I bought at brand new phone, made a brand new loop, still not working
Brantley is 14 and very active baseball player, we have been struggling with loop crashing for several weeks now, I have lost hours of sleep doing countless builds to try and fix it, bought a brand new phone. Nothing stays fixed, eventually the loop crashes within a week every time.
Describe the bug
My son’s loop crashes and will not stay up while I am close to him. If I walk away to another room it will stay up but still red loop. Says Omnipod dash has no signal. The pod before this one has same issue. Worked for 12 hours, then during the night about 10 pm it stopped looping and said pod signal failure. I have seen the time date off several times, since the time change. And I’ve checked his setting every time and the automatic time change is toggled on and set to New York eastern time zone. Tonight it worked great all evening until my son bolus a snack in his bedroom at 9:45, at 9:46 pod signal failure can be seen on the repost, says the “pod has disconnected from us” and another thing I think is related is the Dexcom share always says “internet server down” unable to share every time I turn on the WiFi on his phone. As soon as I put back on cellular beats, the share works again. So I have to leave the WiFi off completely for Dexcom to work. There is definitely some type of signal connection problem and I need help please.
Loop Report 2024-04-11 03:36:44-04:00.pdf
Loop Report 2024-04-11 03:36:44-04:00.pdf
Attach an Issue Report
Tap the Loop settings icon on the bottom of the screen, then tap Issue Report and attach it to this ticket.
It’s 778 pages long. I can try to email it directly but will not link here
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect loop to not crash
Screenshots
If applicable, add screenshots to help explain your problem.
Phone
Loop Version
CGM
Pump
Manufacturer: [e.g. Omnipod
Model: [e.g.Daah
Loop Report 2024-04-11 03:36:44-04:00.pdf
Firmware version: [e.g. 2.3A 1.1 0B 0B]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: