You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug:channelList doesn't stop watching channels that we are removed from #2599
A clear and concise description of what the bug is.
Render a Channel List with the filter to have us as part of the members
Leave a Channel
Make a User B (some other user that is not you) to send a message to this channel that you just left
Now you'll see this channel popping in the list again even tho you're not part of. (Channel persists as watched even tho we are no longer part of it)
But what's funny is that if you refresh, on a initial state we don't listen on channels that we aren't part of so it solves if you refresh.
To Reproduce
Steps to reproduce the behavior:
Render a Channel List with the filter to have us as part of the members
Leave a Channel
Make a User B (some other user that is not you) to send a message to this channel that you just left
Now you'll see this channel popping in the list again even tho you're not part of. (Channel persists as watched even tho we are no longer part of it)
But what's funny is that if you refresh, on a initial state we don't listen on channels that we aren't part of so it solves if you refresh.
Expected behavior
A clear and concise description of what you expected to happen.
When a channel that's on the list, we stop being part of. We shouldn't be watching that channel anymore (because is doesn't match the query anymore)
Screenshots
If applicable, add screenshots to help explain your problem.
Package version
stream-chat-react:^12.8.1
stream-chat-css:
stream-chat-js:^8.48.0
Desktop (please complete the following information):
OS: [e.g. iOS]Mac OS
Browser [e.g. chrome, safari] Chrome
Version [e.g. 22] 131.0.6778.265
Smartphone (please complete the following information):
My web app calls my backend (to do some specific validation and after that. the backend removes the channel member by using the method channel.removeMembers([userId], { skip_push: true });
and that's it.
is this helpful? does it affect on the current buggy behavior? should we do this different? please let us know :)
Hey, @kennyvallejodev, thank you for clarifying, this issue is now being investigated by our BE team, I'll share an update once there's any progress. :)
Activity
MartinCupela commentedon Jan 14, 2025
Hello @kennyvallejodev , could you please be more specific code-wise on how you
2. Leave the channel?kennyvallejodev commentedon Jan 14, 2025
My web app calls my backend (to do some specific validation and after that. the backend removes the channel member by using the method channel.removeMembers([userId], { skip_push: true });
and that's it.
is this helpful? does it affect on the current buggy behavior? should we do this different? please let us know :)
arnautov-anton commentedon Jan 16, 2025
Hey, @kennyvallejodev, thank you for clarifying, this issue is now being investigated by our BE team, I'll share an update once there's any progress. :)
revert: drop ChannelList stopWatching-on-removal fix (#2599)
test(ChannelList): assert removed channels are evicted from activeCha…
chore(release): 9.49.0 [skip ci]
fix(deps): require stream-chat ^9.49.0 to evict removed channels (#2599)
fix: bug bashing ChannelList + Channel (#2474, #2441, #2393) (#3227)
chore(release): 14.6.1 [skip ci]