Upgrade browser SDK from v3.5.0 to open-im-sdk-wasm@3.5.1-alpha.8.1 The normal login system retrieved the message session list. When loading the message, an error occurred when calling to mark the current message as read. The previous v3.5.0 version was normal (single chat session)
What did you expect to happen?
The previous version had no problem with duplicate tags, and after calling the message tag, it should run normally (single chat session)
How can we reproduce it (as minimally and precisely as possible)?
At present, it is caused by the upgrade version of the SDK on the browser side. I am not sure if it is related to the IM service version on the backend, which is release v3.5
What happened?
Upgrade browser SDK from v3.5.0 to open-im-sdk-wasm@3.5.1-alpha.8.1 The normal login system retrieved the message session list. When loading the message, an error occurred when calling to mark the current message as read. The previous v3.5.0 version was normal (single chat session)![微信截图_20240220155003](https://github.com/openimsdk/open-im-sdk-web-wasm/assets/58322844/f26d8af3-388d-4eb5-89e0-9d141cd368d7)
What did you expect to happen?
The previous version had no problem with duplicate tags, and after calling the message tag, it should run normally (single chat session)
How can we reproduce it (as minimally and precisely as possible)?
At present, it is caused by the upgrade version of the SDK on the browser side. I am not sure if it is related to the IM service version on the backend, which is release v3.5
Anything else we need to know?
No response
version
Cloud provider
OS version
Install tools