Skip to content

Bug: <ConversationInfo.latestMsg.isRead & status not synchronized> #39

@DevilSummer

Description

@DevilSummer

What happened?

Background:

  1. Message sending failed (message.status == .sendFailure), and then back to the Chatlist page, the conversationInfo.latestMsg.status is still ".sending".
  2. 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:

  1. conversationInfo.latestMsg.status is ".sendFailure".
  2. 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)?

  1. 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".
  2. 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

Details ``` OpenimSDKCore: v3.4.1-e OpenIMSDK: v3.4.1-e OpenIMSDKUIKit: v3.4.0 ```

Cloud provider

Details

OS version

Details ```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 ```

Install tools

Details

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions