-
Notifications
You must be signed in to change notification settings - Fork 306
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[馃悰] MessageList is not updated even though messages received over WS #2305
Labels
Comments
Hey @Jolville, is this working fine now? |
@khushal87 sorry this was closed automatically after I referenced it in a PR in a private repo. I've just bumped our stream package in the hopes that its fixed by #2479 - will give it a test and get back to you |
Yes, please give it a look and let us know. Thanks 馃槃 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue
New messages (sometimes) aren't being rendered after reconnection events. We've looked into this on our side a fair bit and added some logging to check this wasn't a connection issue, and we can see
connection:onmessage() - onmessage callback
logs, but the message list component doesn't show them.Steps to reproduce
Steps to reproduce the behavior:
This doesn't happen consistently, but we were able to reproduce by
Occasionally, the messages sent from device B while device A was offline, as well as after it was back online, are never shown, until the component is unmounted/remounted by closing the screen.
Expected behavior
Messages should be shown.
Project Related Information
Customization
Click To Expand
No custom components, but here is how we're rendering the channel:
Offline support
Environment
Click To Expand
package.json
:react-native info
output:stream-chat-react-native
version you're using that has this issue:[email protected]
Additional context
We're also seeing some
connection:_errorFromWSEvent() - WS failed with code 1006
/connection:_errorFromWSEvent() - WS failed with code undefined
logs from our customers around the same time they were reporting this issue (the connection does seem to re-establish fine though)Screenshots
N./A
The text was updated successfully, but these errors were encountered: