Files
openchamber/packages
Bohdan Triapitsyn e8e6e4cacf fix(mobile): keep tokenless connections alive across launch and resume
A server running with authentication disabled pairs and connects fine, but
the saved connection has no bearer token. Auto-connect silently bailed on
the missing token and the resume reprobe reported it as 'unreachable',
so every return to the app kicked the user to the connect screen.

Treat a saved tokenless connection as valid: probe it without a bearer and
let the probe decide — auth disabled connects, auth enabled later reports
needs-login. Bail out only when an expected token cannot be read.
2026-08-14 17:29:49 +03:00
..
2026-08-14 00:55:17 +03:00