Thread reply sending isn't triggering didChangeCurrentUserUnreadCount delegate

[NatashaLavrinenko]

What did you do?

Precondition: push notifications are setup as per the documentation, as well as the delegate method for listening to the changes of unread messages number.
Steps to reproduce:

Users A and B has a private chat. User A sent a message there.
User B left a reply into the thread to the message mentioned above.

What did you expect to happen?

Push notification with the info that a new message is sent is delivered to the user.
Number of unread messages in didChangeCurrentUserUnreadCount delegate method for user A is increased.

What happened instead?

Push notification with the info that a new message is sent is delivered to the user.
Number of unread messages in didChangeCurrentUserUnreadCount delegate method for user A is not increased.

For the implementation it's expected that push notifications and the counter from didChangeCurrentUserUnreadCount delegate method should be synchronized, which is currently not. That's why I wanted to clarify whether this behavior is expected? Could it be changed in such case? Or could we possibly miss some configuration parameters so that the thread reply could be included into didChangeCurrentUserUnreadCount delegate method?

Please let me know in case more details are needed.

Thanks in advance!

GetStream Environment

**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

[nuno-vieira]

Hi @NatashaLavrinenko,

At this moment, this is expected. Thread replies do not increase the channel unread count unless showReplyInChannel is true.

There is a plan to change this in the future, but there is not ETA yet, and it is also not clear how this will be implemented yet.

I'm converting this to a discussion, and we will let you know once we have more details.

Best,
Nuno

[NatashaLavrinenko]

Hi @nuno-vieira
Thanks for the information!

[NatashaLavrinenko]

Hey @nuno-vieira
Is there some updates regarding the issue? Is it planned to be fixed?
Thanks in advence!

[nuno-vieira]

Hi @NatashaLavrinenko! Not at the moment. It is probably better if you reach out to support so that the feature request is recorded. The more customers ask for this, the more likely it will get prioritised 👍