fix: channel list stale last message#3534
Merged
isekovanic merged 1 commit intoV8-releasefrom Apr 6, 2026
Merged
Conversation
isekovanic
commented
Apr 6, 2026
| const [forceUpdate, setForceUpdate] = useState(0); | ||
| const [lastMessage, setLastMessageInner] = useState<LastMessageType>( | ||
| () => channel.state.messages[channel.state.messages.length - 1], | ||
| () => channel.state.latestMessages[channel.state.latestMessages.length - 1], |
Contributor
Author
There was a problem hiding this comment.
This has been wrong for years it seems, as we found with @MartinCupela . It's a pretty nasty edge case where if your first load of a channel is to a message in a different message set than the latest one (i.e through a deeplink let's say), the channel list would basically show the last message of that page only (and not the actual latest message in the channel).
Contributor
SDK Size
|
MartinCupela
approved these changes
Apr 6, 2026
oliverlaz
approved these changes
Apr 6, 2026
6 tasks
isekovanic
added a commit
that referenced
this pull request
Apr 6, 2026
## 🎯 Goal This PR is a port of [this change](#3534) to V9. ## 🛠 Implementation details <!-- Provide a description of the implementation --> ## 🎨 UI Changes <!-- Add relevant screenshots --> <details> <summary>iOS</summary> <table> <thead> <tr> <td>Before</td> <td>After</td> </tr> </thead> <tbody> <tr> <td> <!--<img src="" /> --> </td> <td> <!--<img src="" /> --> </td> </tr> </tbody> </table> </details> <details> <summary>Android</summary> <table> <thead> <tr> <td>Before</td> <td>After</td> </tr> </thead> <tbody> <tr> <td> <!--<img src="" /> --> </td> <td> <!--<img src="" /> --> </td> </tr> </tbody> </table> </details> ## 🧪 Testing <!-- Explain how this change can be tested (or why it can't be tested) --> ## ☑️ Checklist - [ ] I have signed the [Stream CLA](https://docs.google.com/forms/d/e/1FAIpQLScFKsKkAJI7mhCr7K9rEIOpqIDThrWxuvxnwUq2XkHyG154vQ/viewform) (required) - [ ] PR targets the `develop` branch - [ ] Documentation is updated - [ ] New code is tested in main example apps, including all possible scenarios - [ ] SampleApp iOS and Android - [ ] Expo iOS and Android
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎯 Goal
This PR fixes an issue where regaining connection (or just loading the app with offline mode enabled) would not properly update the last message for any channels that've changed in the interim.
The reason for this was a very old (seemingly) problem with how
channel.lastMessage()is calculated, completely bypassing the actual last message and not reloading the state at all (even though the channels would actually swap places as they should and their internal state would be correct).This will be ported to V9 as well soon after.
🛠 Implementation details
🎨 UI Changes
iOS
Android
🧪 Testing
☑️ Checklist
developbranch