Bug
In Sources/SundialKitStream/ConnectivityStateManager+Updates.swift, the non-iOS branches disagree about isPaired on watchOS:
handleActivation(from:activationState:error:) hardcodes isPaired: false — with a comment claiming "Always true on watchOS (implicit pairing)".updateCompanionState(isPairedAppInstalled:isPaired:) hardcodes isPaired: true.
So stateManager.isPaired on watchOS flips between false and true depending on which delegate event ran last. (WatchConnectivitySession.isPaired itself returns true on watchOS, so message routing — which reads the session directly — is unaffected; only the public state-manager API is inconsistent.)
Fix direction
Use true consistently on watchOS in both paths (matching the session wrapper), and align the comment.
Bug
In
Sources/SundialKitStream/ConnectivityStateManager+Updates.swift, the non-iOS branches disagree aboutisPairedon watchOS:handleActivation(from:activationState:error:)hardcodesisPaired: false— with a comment claiming "Always true on watchOS (implicit pairing)".updateCompanionState(isPairedAppInstalled:isPaired:)hardcodesisPaired: true.So
stateManager.isPairedon watchOS flips between false and true depending on which delegate event ran last. (WatchConnectivitySession.isPaireditself returnstrueon watchOS, so message routing — which reads the session directly — is unaffected; only the public state-manager API is inconsistent.)Fix direction
Use
trueconsistently on watchOS in both paths (matching the session wrapper), and align the comment.