Unable to bolus with keep pod alive

[Jemzor]

Loop.Report.2026-05-11.15.11.24+01.00.md

Describe the bug

See details below and attached issue report.

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.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Phone

• Hardware: [e.g. iPhone XS]
• OS Version: [e.g. iOS 12.0.1]

Loop Version

• Version Number: [e.g. 1.9.2]
• Repo: [LoopKit/Loop, Katie, etc]

CGM

• Device: [e.g. Dexcom G6]
• Manager app: [e.g. Dexcom App, Spike]

Pump

• Manufacturer: [e.g. Medtronic]
• Model: [e.g. 723]
• Firmware version: [e.g. 2.3A 1.1 0B 0B]

Additional context
Add any other context about the problem here.

Not able to bolus. Returns Bolus issue / unable to connect to pod message after repeated attempts. Toggling Bluetooth and repeated attempts eventually works. Issue report attached.

iPhone 16 Pro
IOS 26.4.2

Loop v3.13.1
Feat/keep-pod-alive
PKA status - When Open

Dexcom G7
DASH

[blameitonben]

The branch was built to help decrease the issue described. This was a software fix, to help a known hardware incompatibility between the iPhone 16 line (17e too) and ATLAS pods. In the event that pod disconnects, either due to local RF interference or because you left it in the other room (distance). The authorization/connection will still take time, and end in bolus failures. The only way to fix this known hardware issue is to replace your phone (no iPhone 16’s or 17e). Or get SAW pods from Omnipod (which is unlikely). If this is a regular issue for you, please upgrade (or down grade) your phone to a device that doesn’t have this known compatibility issue with ATLAS pods (all iPhone 16 models and the iPhone 17e). This was a large enough issue for our family that we just bumped the looping device to a iPhone 17. Ben From: Jemzor ***@***.***> Date: Monday, May 11, 2026 at 7:29 AM To: LoopKit/Loop ***@***.***> Cc: Subscribed ***@***.***> Subject: [LoopKit/Loop] Unable to bolus with keep pod alive (Issue #2431) [https://avatars.githubusercontent.com/u/52126870?s=20&v=4]Jemzor created an issue (LoopKit/Loop#2431)<#2431> Loop.Report.2026-05-11.15.11.24+01.00.md<https://github.com/user-attachments/files/27599010/Loop.Report.2026-05-11.15.11.24%2B01.00.md> Describe the bug See details below and attached issue report. 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. To Reproduce Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Phone * Hardware: [e.g. iPhone XS] * OS Version: [e.g. iOS 12.0.1] Loop Version * Version Number: [e.g. 1.9.2] * Repo: [LoopKit/Loop, Katie, etc] CGM * Device: [e.g. Dexcom G6] * Manager app: [e.g. Dexcom App, Spike] Pump * Manufacturer: [e.g. Medtronic] * Model: [e.g. 723] * Firmware version: [e.g. 2.3A 1.1 0B 0B] Additional context Add any other context about the problem here. Not able to bolus. Returns Bolus issue / unable to connect to pod message after repeated attempts. Toggling Bluetooth and repeated attempts eventually works. Issue report attached. iPhone 16 Pro IOS 26.4.2 Loop v3.13.1 Feat/keep-pod-alive PKA status - When Open Dexcom G7 DASH — Reply to this email directly, view it on GitHub<#2431>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACWNLO7W42GC4MC5MCOUHRD42HPVLAVCNFSM6AAAAACYZHPYBGVHI2DSMVQWIX3LMV43ASLTON2WKOZUGQZDCNRUGAYDOMY>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.

[rolandet]

I've been seeing too many statements like this that SAW pods are no longer available. I just got a new batch of SAW pods directly from Insulet, the manufacturer of the Omnipod DASH. last week and they are still the SAW pods. They came from Insulet's corporate headquarters in Action, Massachusetts. I have never received one ATLAS pod from that manufacturing location. I live two towns over from the Acton location. Might be worth contacting Insulet and explain your situation. I have an iPhone 16 Pro but I've never had to request the SAW pods specifically.

The only way to fix this known hardware issue is to replace your phone (no iPhone 16’s or 17e). Or get SAW pods from Omnipod (which is unlikely).

[blameitonben]

It’s unlikely since you have no choice in what pods you receive from your pharmacy. This is very lucky for you you’ve never seen them. I hope this keeps up for you. The statement still stands since we have no control over the type or version pods we receive. It’s a known hardware incompatibility, the moment you end up with Atlas inventory, the issue will likely start. The only way to fix the issue is by fixing the problem you have control over aka your device. Ben

…

________________________________ From: rolandet ***@***.***> Sent: Monday, May 11, 2026 8:05:32 AM To: LoopKit/Loop ***@***.***> Cc: blameitonben ***@***.***>; Comment ***@***.***> Subject: Re: [LoopKit/Loop] Unable to bolus with keep pod alive (Issue #2431) [https://avatars.githubusercontent.com/u/4328088?s=20&v=4]rolandet left a comment (LoopKit/Loop#2431)<#2431 (comment)> I've been seeing too many statements like this that SAW pods are no longer available. I just got a new batch of SAW pods directly from Insulet, the manufacturer of the Omnipod DASH. last week and they are still the SAW pods. They came from Insulet's corporate headquarters in Action, Massachusetts. I have never received one ATLAS pod from that manufacturing location. I live two towns over from the Acton location. Might be worth contacting Insulet and explain your situation. I have an iPhone 16 Pro but I've never had to request the SAW pods specifically. The only way to fix this known hardware issue is to replace your phone (no iPhone 16’s or 17e). Or get SAW pods from Omnipod (which is unlikely). — Reply to this email directly, view it on GitHub<#2431 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACWNLO5P5L2A3J2GNUBHLRD42HT3ZAVCNFSM6AAAAACYZHPYBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMRRHEYTQMRUGY>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[rolandet]

It’s unlikely since you have no choice in what pods you receive from your pharmacy. This is very lucky for you you’ve never seen them. I hope this keeps up for you.

The statement still stands since we have no control over the type or version pods we receive.

It’s a known hardware incompatibility, the moment you end up with Atlas inventory, the issue will likely start. The only way to fix the issue is by fixing the problem you have control over aka your device.

Ben
…

Ben, it never hurts to call Insulet directly and explain your situation. They might be able to replace the existing ATLAS pods with SAW pods. Obviously, the Acton manufacturing location still has inventory since I've never has received an ATLAS pod. I get my pods directly from Insulet since my health plan treats insulin pumps as medical supply equipment.