The Chat SDK stores historical messages on the chat server. When a chat user logs in from a different device, you can retrieve the historical messages from the server, so that the user can also browse these messages on the new device.
This page introduces how to use the Chat SDK to retrieve and delete messages from the server.
The Chat SDK uses
ChatManager to retrieve historical messages from the server. The followings are the core methods:
asyncFetchConversationsFromServer: Retrieves a list of conversations stored on the server.
asyncFetchHistoryMessage: Retrieves the historical messages in the specified conversation from the server.
removeMessagesFromServer: Deletes historical messages from the server unidirectionally.
deleteConversationFromServer: Deletes conversations and their historical messages from the server.
Before proceeding, ensure that you meet the following requirements:
- You have integrated the Chat SDK, initialized the SDK and implemented the functionality of registering accounts and login. For details, see Chat SDK quickstart.
- You understand the API call frequency limits as described in Limitations.
This section shows how to implement retrieving conversations and messages.
asyncFetchConversationsFromServer to retrieve conversations from the server with pagination. Each retrieved conversation contains one last historical message. We recommend calling this method when the app is first installed, or when there is no conversation on the local device. Otherwise, you can call
getAllConversations to retrieve conversations on the local device.
This retrieves up to 100 conversations per API call by default. Contact email@example.com if you want to adjust this limit.
If you still use the
asyncFetchConversationsFromServer method to retrieve the conversations from the server without pagination, the SDK, by default, retrieves the last ten conversations in the past seven days, and each conversation contains one last historical message. To adjust the time limit or the number of conversations retrieved, contact firstname.lastname@example.org.
After retrieving conversations, you can retrieve historical messages by pagination from the server.
You can set the search direction to retrieve messages in the chronological or reverse chronological order of when the server receives them.
To ensure data reliability, we recommend retrieving less than 50 historical messages for each method call. To retrieve more than 50 historical messages, call this method multiple times. Once the messages are retrieved, the SDK automatically updates these messages in the local database.
removeMessagesFromServer to delete historical messages one way from the server. You can remove a maximum of 50 messages from the server each time. Once the messages are deleted, you can no longer retrieve them from the server. The deleted messages are automatically removed from your local device. Other chat users can still get the messages from the server.
deleteConversationFromServer to delete conversations and their historical messages unidirectionally from the server. After the conversations and messages are deleted from the server, you can no longer get them from the server. The deleted conversations still exist on your local device, but the messages are automatically removed from the device. Other chat users can still get the conversations and their historical messages from the server.
After implementing retrieving messages, you can refer to the following documents to add more messaging functionalities to your app: