3 people d7ca7b084e fix(#240): notification tap race condition opens new chat instead of correct session (#241) ...

Two-pronged fix for the race between GatewayReady auto-creating a session
and ChatScreen LaunchedEffect calling switchSession:

1. ChatViewModel: added `initialSessionId` field. GatewayReady now checks
   this before auto-creating a session — if set, it calls switchSession
   instead. The field is set synchronously by ChatScreen via SideEffect
   during composition, before any WS event can be processed.

2. ChatScreen: LaunchedEffect now keys on state.connectionStatus and
   waits for CONNECTED before calling switchSession. This prevents the
   SESSION_RESUME message from being dropped (webSocket is null before
   onOpen, so send() is a silent no-op).

Fixes #240

Co-authored-by: M57 <hy4ri@users.noreply.github.com>

2026-06-21 18:32:29 +03:00

..

schemas/com.m57.hermescontrol.data.local.HermesDatabase

fix(#66): enable room schema export and configure release migration safe-guards (#177)

2026-06-20 22:57:08 +03:00

src

fix(#240): notification tap race condition opens new chat instead of correct session (#241)

2026-06-21 18:32:29 +03:00

.gitignore

Initial commit of HermesControl Android app

2026-06-16 00:00:36 +03:00

build.gradle.kts

fix(#63): require keystore env variables for release builds (#176)

2026-06-20 22:47:46 +03:00

proguard-rules.pro

fix(nav): correct proguard keep rule to use extends instead of implements

2026-06-20 18:16:30 +03:00