Commit a4a258c
committed
fix(session): clear stale error state when signaling starts reconnecting
When SignalingConnecting fires after a failed connection attempt,
lastSignalingClientConnectError and lastSignalingDisconnectCode were
not cleared. This left the status stuck on connectError/connectIssue
('Connection error' / 'Connection issue') even though a fresh connect
attempt was already in progress.
After this fix, SignalingConnecting resets all stale error fields so
the status correctly shows inProgress ('Connection in progress') for
the duration of the reconnect.1 parent 4dcdf47 commit a4a258c
1 file changed
Lines changed: 2 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
627 | 627 | | |
628 | 628 | | |
629 | 629 | | |
| 630 | + | |
630 | 631 | | |
| 632 | + | |
631 | 633 | | |
632 | 634 | | |
633 | 635 | | |
| |||
0 commit comments