Repository navigation
Manage embedded connection setup inside the SDK - #2
Merged
Merged
Conversation
Raynan00
marked this pull request as ready for review
September 29, 2026 12:59
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
1 participant
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.
Host apps currently assemble tunnel startup, pairing, discovery and frame/event consumption themselves.
CellUseConnectionbrings those steps into the SDK: reconnect through a saved pairing, surface the next setup action, and create an agent runtime after fresh portrait frames and input readiness are available.The controller owns one set of session streams, closes failed or cancelled sessions, and ignores callbacks from earlier connections. The host retains control of its UI and background execution window. Existing direct-session integration remains available.
Validation: ten new setup lifecycle tests cover saved pairing, selection, cancellation, stale callbacks, readiness and concurrent teardown. The latest commit passes the unsigned iOS build, Swift suites on macOS and Linux, and the embedded-tunnel checks. Full iOS validation.
The combined connection flow still needs a physical iPhone run; the build checks do not verify VPN consent and pairing prompts on a device.