Bug: Incorrect pod suspended message when bolusing after comms error

[marionbarker]

Updated Status Leaving the issue open until the submodule updates associated with this issue are added to LoopWorkspace for released and development code

Describe the bug Using my regular Looping phone, I tried to bolus and Loop reported Pod was suspended (it was not). Repeated the bolus attempt and it went through successfully. I have seen comments about this intermittent error on Facebook, but never got a Loop Report.

Attach an Issue Report Loop Report 2024-07-09 202155-0700.md

The incorrect pod suspended message should be around 16:25 PDT or 23:25 UTC, 2024-07-09

This was analyzed by @itsmojo who reports:

• the Device Communication Log showed there was IO error (“messageIOException("Could not write $msgType: unsentWithError(OmniBLE.PeripheralManagerError.timeout([...”)
  • this was on the last get status with a response before the bolus was attempted
  • this combination resulted in the incorrect warning about the pod being suspended on the subsequent bolus attempt

To Reproduce This is an intermittent error.

Expected behavior Do not show user a message that pod is suspended when it is not.

Screenshots n/a

Phone

• iPhone 15 pro, iOS 17.5.1

Loop Version

• essentially the same as Loop 3.4.1 (before the release)

CGM

• Dexcom G7 using Dexcom app

Pump

• Omnipod DASH

Additional context I was super busy at the time. I sent the Loop report to Joe (itsmojo).

He provided this solution.

• Update logic to prevent bogus suspend error after comms error
• Update logic to prevent bogus suspend error after comms error