[Enhancement]Prevent WebSocket reconnection with expired tokens

[ipavlidakis]

Summary

Separates token-refresh recovery from automatic WebSocket reconnection.

When a WebSocket disconnects because its token expired, StreamCore now waits for the owning SDK to refresh the token and reconnect explicitly instead of retrying with the existing credentials.

Motivation

An expired token was previously considered automatically reconnectable. This allowed DefaultConnectionRecoveryHandler to call connect() while StreamChat or StreamVideo was still refreshing the token.

That created a race where the WebSocket could reconnect using stale credentials.

Changes

• Add WebSocketConnectionState.requiresTokenRefresh.
• Disable automatic reconnection for expired tokens.
• Preserve the existing invalid-token reconnection behavior.
• Keep ConnectionStatus as .connecting while token refresh is required.
• Add tests covering expired-token classification and connection-status mapping.

Recovery contract

• StreamCore automatically handles network, system, and health-check failures.
• Product SDKs handle authentication recovery.
• After successfully refreshing the token, the product SDK explicitly calls connect().

[github-actions]

	1 Message
📖	Skipping Danger since the Pull Request is classed as Draft/Work In Progress

Generated by 🚫 Danger

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
93.8% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud