Retrieve the conversation list

The conversation list belongs to the current logged-in user. Each ConversationInfo contains state such as the conversation identifiers, unread count, latest message, pin state, and draft. Retrieve conversations with the paginated API; do not load the entire list with a non-paginated API.

Retrieve conversations by page

Use getConversationListSplit() for pagination. The first page starts with offset: 0.

const pageSize = 50;

Future<List<ConversationInfo>> loadConversationPage(int offset) async {
  final page = await OpenIM.iMManager.conversationManager
      .getConversationListSplit(offset: offset, count: pageSize);
  mergeConversations(page);
  return page;
}

Parameters

A successful Future returns the current page as List<ConversationInfo>. For subsequent pages, advance offset by the number of items already requested and deduplicate by conversationID. Receiving fewer than count items means that the end has been reached. For a manual refresh, clear pagination state and reload from 0.

Keep the list synchronized

getConversationListSplit() establishes a snapshot only and does not trigger conversation callbacks. Add the following handlers to the application's single OnConversationListener:

void handleNewConversations(List<ConversationInfo> conversations) {
  mergeConversations(conversations);
}

void handleConversationsChanged(List<ConversationInfo> conversations) {
  mergeConversations(conversations);
}

Both onNewConversation and onConversationChanged carry List<ConversationInfo>. Merge their items by conversationID. See Events overview for listener composition and the single setup entry point.

Do not substitute the joined-group list for the conversation list. A user may have joined a group without creating its conversation yet, or may retain a historical conversation after leaving a group.