fix(apple): point pairing copy at the web console's real port (47992, HTTPS)

Every pairing surface in the Apple client still told users to open the web
console on port 3000 — the pre-move port. The console has served :47992 for a
long time, so anyone following the on-screen instructions hit a dead port and
had no way to approve the device or read the PIN.

Seven strings across ContentView, SessionModel and PairSheet (iOS/tvOS/macOS
share them). The two that spell out a full URL also said `http://`; the console
is HTTPS-only (host's self-signed cert), so they now read
`https://<host>:47992`, matching the phrasing in the host README, install docs
and the deb/rpm packaging notes.

Copy-only — no behavioural change; a repo-wide sweep found no other stale :3000.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
2026-07-19 10:17:36 +02:00
parent a83acf3ee1
commit c131603f0d
3 changed files with 7 additions and 7 deletions
@@ -292,7 +292,7 @@ struct ContentView: View {
Button("Cancel", role: .cancel) {}
} message: { req in
Text("\(req.host.displayName) requires pairing. Request access and approve this "
+ "device in the host's web console (port 3000 → Pairing) — no PIN needed. Or "
+ "device in the host's web console (port 47992 → Pairing) — no PIN needed. Or "
+ "pair with the 4-digit PIN it can display.")
}
// One "Connection failed" surface for every home screen (touch grid, gamepad launcher) and
@@ -335,7 +335,7 @@ struct ContentView: View {
Button("Cancel", role: .cancel) { model.disconnect() }
} message: { req in
Text("Approve \u{201C}\(localDeviceName)\u{201D} in \(req.host.displayName)'s web "
+ "console (port 3000 → Pairing). This device connects automatically once you "
+ "console (port 47992 → Pairing). This device connects automatically once you "
+ "approve it — no need to reconnect.")
}
// Informational deep-link outcome (unknown host / already streaming). Not an error.