-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[BUG] markConversationMessageAsRead fail #2765
Comments
Hello! Thank you for filing an issue. If this is a bug report, please include relevant logs to help us debug the problem. Join slack 🤖 to connect and communicate with our developers. |
After refreshing the browser, IMSDK.getTotalUnreadMsgCount returns the original unread message count. |
2024-10-22.21.30.01.mov |
2024-10-22.21.30.01.mov |
Please collect the complete logs of the client console (including logs after removing unreads and refreshing the page), ensuring that all logs printed by wasm_exec.js are included. |
In the video, the unread count for the conversation with '李四' can be cleared |
The code is fine, but some conversations cannot be cleared. |
Complete logs of the client console must be collected in order to troubleshoot the issue |
Which version are you using? Please try it with the latest version. |
The new version has removed all scripts, so this issue will no longer exist. |
OpenIM Server Version
3.8.0
Operating System and CPU Architecture
Linux (AMD)
Deployment Method
Docker Deployment
Bug Description and Steps to Reproduce
After the client successfully marks the message as read, it retrieves data from the server again, but it's still the previous data.
Screenshots Link
No response
The text was updated successfully, but these errors were encountered: