-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
didChangeCurrentUserUnreadCount not triggered after user deletion #2591
Comments
Hi @NatashaLavrinenko , We will be looking into it as soon as possible. Will keep you posted 😄 |
Hey @polqf, |
Hi @NatashaLavrinenko, sorry for the delay in the reponse. We identified the root cause of the issue, and it has been added to our backlog. We will be fixing it based on priority. |
Sorry for taking too long to respond, but this seems to be a bug on our Backend, not really related to the iOS SDK. This is reported to our backend, but if you want to bump the priority please reach out to our support team: https://getstream.io/contact/support/ Best, |
What did you do?
Precondition: user A and user B are members of the channel(as well as several more users)
User B left 2 messages in channel and afterwards was deleted by calling deleteUsers method on the backend side, please see all the parameters below:
User A got updates that 2 unread messages were received. After that user B was deleted from GetStream base.
What did you expect to happen?
It's expected that after the user was removed(as well as all his/her messages), didChangeCurrentUserUnreadCount will be called and unread counter will be cleared as the messages of user B were removed(in case the channel is opened, messages from user B are not shown).
What happened instead?
didChangeCurrentUserUnreadCount
method is not called, so the wrong unread counter for particular channel is shown.Please let me know in case more details are needed.
Thanks in advance!
GetStream Chat version: 4.28.0
GetStream Chat frameworks: StreamChat, StreamChatUI
iOS version: 16.2
Swift version: 5.6
Xcode version: 14.2
Device: iPhone 11
The text was updated successfully, but these errors were encountered: