Tracks the batch of mobile-side improvements landed on main but awaiting the next App Store / Play Store release to reach end users.
What's in main, pending store release
- iOS QR scanner black camera —
AVCaptureSession.startRunning now runs on a dedicated background queue, preview layer re-frames in viewDidLayoutSubviews, and camera-permission denial shows a user-visible message instead of a black screen. (packages/ios/Byoky/Views/Pair/PairView.swift)
- Manual-entry pair code now accepts URLs on iOS and Android. Previously only the raw base64 blob decoded; pasting
https://byoky.com/pair#… silently failed. (packages/ios/.../PairView.swift, packages/android/.../PairScreen.kt)
- Setup token "online only" warning in Add Credential screens on iOS + Android + extension, since OAuth setup tokens can only be proxied while the phone/extension is active.
relay:vault:offer now carries the vault's /connect providers map so the web SDK can distinguish phone-only providers from vault-capable ones. Fixes refresh restoring a stale "connected" state that 404s on first request.- Phone keeps paired state across
peer:status offline so the browser can rejoin the same relay room on refresh without the phone dropping the session.
Known regression until this ships
The SDK's relay-rejoin path is live on byoky.com, but existing App Store / Play Store phones tear paired state down on peer:offline. Refresh against an older phone auths successfully then hangs ~120 s waiting for a response that never comes. Mitigation plan: gate SDK rejoin behind a pair:hello capability flag (tracked separately) or ship these mobile builds.
Tracks the batch of mobile-side improvements landed on
mainbut awaiting the next App Store / Play Store release to reach end users.What's in main, pending store release
AVCaptureSession.startRunningnow runs on a dedicated background queue, preview layer re-frames inviewDidLayoutSubviews, and camera-permission denial shows a user-visible message instead of a black screen. (packages/ios/Byoky/Views/Pair/PairView.swift)https://byoky.com/pair#…silently failed. (packages/ios/.../PairView.swift,packages/android/.../PairScreen.kt)relay:vault:offernow carries the vault's/connectproviders map so the web SDK can distinguish phone-only providers from vault-capable ones. Fixes refresh restoring a stale "connected" state that 404s on first request.peer:status offlineso the browser can rejoin the same relay room on refresh without the phone dropping the session.Known regression until this ships
The SDK's relay-rejoin path is live on byoky.com, but existing App Store / Play Store phones tear paired state down on
peer:offline. Refresh against an older phone auths successfully then hangs ~120 s waiting for a response that never comes. Mitigation plan: gate SDK rejoin behind apair:hellocapability flag (tracked separately) or ship these mobile builds.