Bug: <ConversationInfo.latestMsg.isRead & status not synchronized>
Opened this issue · 0 comments
DevilSummer commented
What happened?
Background:
- Message sending failed (message.status == .sendFailure), and then back to the Chatlist page, the conversationInfo.latestMsg.status is still ".sending".
- UserA sended a message to UserB, UserB has readed this message, and this message's isRead property has been changed to "true" , but the conversationInfo.latestMsg.isRead is still "false" at the chatlist page.
What did you expect to happen?
Expect:
- conversationInfo.latestMsg.status is ".sendFailure".
- conversationInfo.latestMsg.isRead is "true".
In summary, the data of the conversationInfo.latestMsg needs to be synchronized with the data of the original message.
How can we reproduce it (as minimally and precisely as possible)?
- Message sending failed under weak/no network conditions. After restarting the app, entering the chat interface may display failed message. When returning to the chat list, the conversation.latestMsg.status may be "sending".
- step1:UserA send a message to UserB. --> step2: UserB readed this message. --> step3: UserA return to chat list.
Anything else we need to know?
No response
version
```
OpenimSDKCore: v3.4.1-e
OpenIMSDK: v3.4.1-e
OpenIMSDKUIKit: v3.4.0
```
Cloud provider
OS version
```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```