RileyLink communications error refuses to pair

[caitp]

Describe the bug
In attempting to pair a new OmniPod, a RileyLink doesn't even try to communicate with it and I get stuck in an endless "sent ACK instead.." error, and the only option I'm given is to throw out a brand new, perfectly working pod, without even trying to work around it.

Attach an Issue Report
I can't get an issue report while stuck on this screen (awesome)

To Reproduce
Steps to reproduce the behavior:
Try to pair a pod, get unlucky and have some kind of comms error

Expected behavior
If a comms error occurs, try again

Screenshots
N/A
Phone

• iphone 13 pro, ios 18.2 maybe

Loop Version

• Version Number: whatever was stable a few weeks ago
• Repo: [LoopKit/Loop]

CGM

• Device: Dexcom G7
• Manager app: Dexcom App

Pump

• Manufacturer: OmniPod
• Model: Original
• Firmware version: N/A

Additional context
Add any other context about the problem here.

[marionbarker]

I’m sorry for the issues and loss of pod.
Can you confirm that you tried all these troubleshooting tips before discarding the pod.

• https://loopkit.github.io/loopdocs/troubleshooting/red-loop/#reset-loop-to-pump-communications

If you tried all these things a couple of times, it was probably a defective pod.

And please post your Loop Report. If it failed to pair at all, we won’t see anything but there might be Rileylink messages that provide a clue.

[caitp]

The only option I did not try was disabling and re-enabling Bluetooth -- rileylink settings and diagnostics are completely inaccessible in this state

[sp90]

After updating to the latest version on iOS 18 and using an iPhone 15 pro we had the exact same issue

[marionbarker]

Please post a Loop Report. Loop, Settings, scroll down to Support and tap Issue Report and then post it here.

These reports contain 84 hours of data so can be useful even if you prepare it after cancelling out.

Was your next pod successful? Did you try all the troubleshooting steps?

What kind of Rileylink and do you have a different one to try?