Skip to content
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

Closed
OrrinHatch opened this issue Oct 22, 2024 · 11 comments
Closed

[BUG] markConversationMessageAsRead fail #2765

OrrinHatch opened this issue Oct 22, 2024 · 11 comments
Assignees
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@OrrinHatch
Copy link

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

@OrrinHatch OrrinHatch added the bug Categorizes issue or PR as related to a bug. label Oct 22, 2024
@OpenIM-Robot
Copy link

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.

@OrrinHatch
Copy link
Author

WechatIMG225

@OrrinHatch
Copy link
Author

After refreshing the browser, IMSDK.getTotalUnreadMsgCount returns the original unread message count.

@OrrinHatch
Copy link
Author

2024-10-22.21.30.01.mov

@OpenIM-Robot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


2024-10-22.21.30.01.mov

@Bloomingg
Copy link
Member

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.

@OrrinHatch
Copy link
Author

In the video, the unread count for the conversation with '李四' can be cleared

@OrrinHatch
Copy link
Author

OrrinHatch commented Oct 23, 2024

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.

The code is fine, but some conversations cannot be cleared.

@Bloomingg
Copy link
Member

Complete logs of the client console must be collected in order to troubleshoot the issue

@skiffer-git
Copy link
Member

Which version are you using? Please try it with the latest version.

@skiffer-git
Copy link
Member

The new version has removed all scripts, so this issue will no longer exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

5 participants