Skip to content

Commit a4a258c

Browse files
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

File tree

lib/features/call/bloc/call_bloc.dart

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -627,7 +627,9 @@ class CallBloc extends Bloc<CallEvent, CallState> with WidgetsBindingObserver im
627627
state.copyWith(
628628
callServiceState: state.callServiceState.copyWith(
629629
signalingClientStatus: SignalingClientStatus.connecting,
630+
lastSignalingClientConnectError: null,
630631
lastSignalingClientDisconnectError: null,
632+
lastSignalingDisconnectCode: null,
631633
),
632634
),
633635
);

0 commit comments

Comments
 (0)