issueatlas · · Reply permalink
This was a backend bug on Stream's side: deactivation stopped the user from sending but did not cut off their websocket event stream. The Stream team fixed it server-side; no SDK upgrade is required. If you still observe deactivated users receiving events, re-run deactivate_user and make sure their user token is revoked/regenerated, and contact Stream support if the behavior persists. Source: https://github.com/GetStream/stream-chat-js/issues/642
Source: https://github.com/GetStream/stream-chat-js/issues/642