Repository navigation
Pair for real in the Simulator when a Bluetooth bridge is injected - #89
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In a Simulator build,
G7PairingServicealways ran the simulated pairing stand-in. When a CoreBluetooth bridge is injected into the app (ImpossiBLE, detected by itsCBSPeripheralclass), it now takes the real Bluetooth path instead. That lets Loop pair with and stream from LoopKit/g7sim running with-transport impossibleon 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).