Skip to content

Pair for real in the Simulator when a Bluetooth bridge is injected - #89

Merged
ps2 merged 1 commit into
next-devfrom
simulator-bluetooth
Oct 11, 2026
Merged

ps2 merged 1 commit into
next-devfrom
simulator-bluetooth

Conversation

@ps2

@ps2 ps2 commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

In a Simulator build, G7PairingService always ran the simulated pairing stand-in. When a CoreBluetooth bridge is injected into the app (ImpossiBLE, detected by its CBSPeripheral class), it now takes the real Bluetooth path instead. That lets Loop pair with and stream from LoopKit/g7sim running with -transport impossible on the Mac. Without the bridge, nothing changes.

Verified in the iOS Simulator against g7sim: full J-PAKE pairing, certificate exchange, glucose plus backfill, reconnect with the stored key, and backfill after a relaunch. I couldn't test the pairing-screen UI path here, because it needs taps.

Setup steps are in the LoopKit/g7sim README, under "Run it for Loop in the iOS Simulator". The injected dylib carries a fix for an ImpossiBLE queue bug (mickeyl/ImpossiBLE#2).

With ImpossiBLE injected into the app and g7sim serving its socket, the
Simulator has a sensor to talk to, so the pairing run uses the real path
instead of the stand-in. Without the bridge nothing changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant