Extensions on V2TIMManager

• Each conversation corresponds to a chat window. For example, a one-to-one chat or a chat group is a conversation.

• Since there may be a large number of historical conversations, you are advised to call this API in query-by-page mode and pull 100 historical conversations per page at a time.

• This API pulls locally cached conversations. If conversations on the server are updated, the SDK automatically synchronizes the updates internally and then notifies users via @ref V2TIMConversationListener callback.

• If all conversations are pulled, the value of the isFinished field in V2TIMConversationResult in the success callback is true.

• For 5.5.892 and later versions, conversations on the conversion list obtained by this API are sorted by orderKey by default. The larger the orderKey value, the higher the order of the conversation.

• For versions earlier than 5.5.892, conversations on the conversion list obtained by this API are sorted by "lastMessage -> timestamp" by default. The later the timestamp, the higher the order of the conversation.

• When a conversation is deleted from local storage, it is also deleted from the server.

• When messages in a conversation are deleted from local storage, they are also deleted from the server.

If existing marks do not meet your needs, you can customize extension marks. Extension marks need to meet the following two conditions:

1、Extended mark values ​​must not conflict with existing mark values ​​in TIIMConversationMarkType.

2、Extended mark values must be a 0x1L << n (32 <= n < 64, that is, n must be greater than or equal to 32 and less than 64). For example, you can use the extension mark "0x1L << 32" to mean "iPhone online". - Parameters: - conversationIDList : conversation list - markType : mark type of the conversation. For the valid values, see the V2TIMConversationMarkType definition. - enableMark : true：mark false：unmark - Warning: The extension mark value cannot be set to 0x1 << 32, it must be set to 0x1LL << 32, which explicitly tells the compiler that it is a 64-bit integer constant.

• After you call this API to obtain the total count of unread messages for all conversations, the newest value will be notified to you through the onTotalUnreadMessageCountChanged callback when unread message count of any conversation changed.

• The total unread message count excludes muted conversations (conversations whose message receiving option is V2TIM_NOT_RECEIVE_MESSAGE or V2TIM_RECEIVE_NOT_NOTIFY_MESSAGE or V2TIM_RECEIVE_NOT_NOTIFY_MESSAGE_EXCEPT_AT).

• The total unread message count excludes muted conversations (conversations whose message receiving option is V2TIM_NOT_RECEIVE_MESSAGE or V2TIM_RECEIVE_NOT_NOTIFY_MESSAGE or V2TIM_RECEIVE_NOT_NOTIFY_MESSAGE_EXCEPT_AT).

• After you call this API, the newest value of total unread message count for conversations that match the filter parameter will be notified to you through the onUnreadMessageCountChangedByFilter callback.

• If you want to clear the unread messages of all a one-to-one conversation, set conversationID to "c2c", i.e., don't specify the userID.

• If you want to clear the unread messages of all group conversations, set conversationID to "group", i.e., don't specify the groupID.

• If you want to clear the unread messages of all conversations, set conversationID to "" or nil.

• After the API is successfully called, you will receive the onConversationChanged callback that carries the latest unread message number of the corresponding conversation.