Unread Chat Not Removed from List After Reading Last Message Until Manual Refresh

[JAZZKIT]

What did you do?

Opened a chat from the unread chat list and read the last unread message, then navigated back.

What did you expect to happen?

Expected the chat to disappear from the list and see the “No unread chats” screen immediately.

What happened instead?

The chat remained visible in the unread list (with the unread badge), even though the unread count updated. The chat only disappeared after taking an additional action, like refreshing or navigating away and back.

GetStream Environment last one

**GetStream Chat version:4.80.0
GetStream Chat frameworks: StreamChat, StreamChatSwiftUI
**iOS version:18.2
Swift version:
**Xcode version:16.4
**Device:Simulator

Additional context

This issue only occurs when there is a single unread chat left. With multiple unread chats, the list updates as expected after reading one. Is there a way to make the UI update and remove the chat from the unread list immediately after it is read, without requiring extra actions? Or is this a bug?

[nuno-vieira]

Hi @JAZZKIT ,

We have no "unread chats" by default. You need to share your queries and what you are doing; otherwise, we can't reproduce your scenario.

Best,
Nuno

[JAZZKIT]

Hey @nuno-vieira, thanks for your reply. We’re actually using the default .hasUnread filter provided by GetStream to get unread chats. Here’s how we set it up:

let finalFilter: Filter<ChannelListFilterScope> = onlyUnread
    ? .and([baseQuery.filter, .hasUnread])
    : baseQuery.filter

So, the unread list is based on the standard .hasUnread filter from the SDK—no custom logic on our end for this part.

[nuno-vieira]

Hi @JAZZKIT,

I'm not able to reproduce this, here is a Demo of this working with our Demo App:

Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-07-04.at.14.42.05.mp4

[nuno-vieira]

Hi @JAZZKIT,

Nevermind, I was able to reproduce this on the SwiftUI Demo App. In the UIKit Demo app works fine. So something is wrong with the SwiftUI app, we will create a ticket and we will let you know once we fix this.

Best,
Nuno