Define Network backend API expectations - #34
Closed
rchatham wants to merge 2 commits into
Closed
Conversation
rchatham
force-pushed
the
feature/network-migration-api-expectations
branch
from
August 7, 2026 03:51
928be06 to
7530830
Compare
…tion-hardening' into HEAD # Conflicts: # Sources/PeerConnectivityUI/PeerConnectionManager+UI.swift
Owner
Author
|
Superseded by consolidated PR #42. No commits were discarded; this branch is preserved as a recovery and reference point. Addressed review findings were replied to and resolved before consolidation. |
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.
Summary
Defines the initial API expectations for the experimental Network framework backend and makes the browser UI path fail predictably instead of reaching MultipeerConnectivity-only state.
Changes
.automaticdiscovery/connect is supported..custom+invitePeeris supported for app-owned peer selection..inviteOnlydoes not provide MultipeerConnectivity UI with.networkFramework.sendDataandsendMessageare supported.multipeerSessionremains MultipeerConnectivity-only..foundPeer/.lostPeerandinvitePeer, recommending.preSharedKeyfor authenticated encrypted sessions.networkSecurityapplies only to.networkFramework; MultipeerConnectivity retains its ownMCSessionsecurity behavior.PeerConnectivityUI.browserViewControllerto returnnilfor Network-backed managers instead of touchingmultipeerSessionand triggering a programmer-error fatal path.networkSecuritystorage/default behavior and the fact that MultipeerConnectivity ignores the Network security configuration.Verification
swift test— 104 tests passedxcodebuild test -project PeerConnectivity.xcodeproj -scheme PeerConnectivity -destination 'platform=iOS Simulator,name=iPhone 16,OS=18.3.1' -configuration Debug— 104 tests passedNotes / limitations
Stack context
Stacked on PR #33 (
feature/network-migration-connection-hardening). This is the API expectation stabilization slice of the Network migration stack.