What happens
After the browser page says authentication succeeded, the desktop launcher banner can show "Not connected to the server. Sign in again to reconnect" with Sign in offered again. A second click restarts OAuth for a flow that already wrote tokens. Waiting a few seconds without clicking also clears it.
The app's own SignalR lane can report Connected while the local daemon's connection word is still disconnected (token pickup and hub redial lag the loopback page). The launcher settles the post-sign-in banner on that lane, so catch-up is shown as a lost session.
Expected
While the daemon is still catching up, keep finishing/connecting copy, hide Sign in, and show a busy indicator. Offer Sign in again only when the session is actually expired (lane SignedOut).
Repro
- Quit the app,
kcap daemon stop, kcap logout, kcap daemon start -d, start the app.
- Sign in in the browser until "Authentication successful!".
- Return to the launcher before the daemon reports connected.
What happens
After the browser page says authentication succeeded, the desktop launcher banner can show "Not connected to the server. Sign in again to reconnect" with Sign in offered again. A second click restarts OAuth for a flow that already wrote tokens. Waiting a few seconds without clicking also clears it.
The app's own SignalR lane can report Connected while the local daemon's connection word is still disconnected (token pickup and hub redial lag the loopback page). The launcher settles the post-sign-in banner on that lane, so catch-up is shown as a lost session.
Expected
While the daemon is still catching up, keep finishing/connecting copy, hide Sign in, and show a busy indicator. Offer Sign in again only when the session is actually expired (lane SignedOut).
Repro
kcap daemon stop,kcap logout,kcap daemon start -d, start the app.