messageCollection allows you to swiftly create a chat view that includes all data. This page explains how to make a view using the collection.
Note: Understand the differences between local caching and SyncManager, and learn how to migrate Message collection.
First, create a
messageCollection through the
createMessageCollection() method. Here, you need to set the message filter to determine the message order and the starting point of the message list in the chat view.
startingPoint is the reference point of the message retrieval for a chat view. This should be specified as a timestamp.
If you set the value of
startingPoint to the current time or
Long.MAX_VALUE, messages in the view will be retrieved in reverse chronological order, showing messages from the most recent to the oldest.
If you set the value of
startingPoint to the message last read by the current user, messages in the view will be fetched in chronological order, starting from the last message seen by the user to the latest.
When initializing a message collection, you must set the
MessageCollectionInitPolicy. The policy determines how initialization deals with the data retrieved from the local cache and API calls.
Then initialize a
messageCollection instance through the
initialize() method. Here, you need to set the
MessageCollectionInitPolicy determines how initialization deals with the message data retrieved from the local cache and API calls. Because we only support
CACHE_AND_REPLACE_BY_API as of now, an additional implementation is required to clear the messages in the local cache before adding the messages from the remote server to it.
Retrieves cached messages from the local cache and then replaces them with the messages pulled from Sendbird server through API calls.
loadNext() methods to retrieve messages from the previous page and the next page.
loadPrevious() method is called, the Chat SDK first checks whether there're more messages to load from the previous page through the
hasPrevious function. The same goes for the
These methods have to be called during initialization as well.
messageCollectionHandler to determine how the client app would react to message-related events.
The following table shows possible cases where each event handler can be called.
- A new message is created as a real-time event.
- A message is deleted as a real-time event.
- A message is updated as a real-time event.
- The channel information that is included in the user's current chat view is updated as a real-time event.
- The current channel is deleted as a rea-time event.
- A huge gap is detected through background sync. In this case, you need to dispose of the view and create a new
Depending on the online status, the client app could miss message events. Especially when new messages or new channels stored in Sendbird server don't reach the Chat SDK in the client app, a gap is created. A gap is a chunk of objects that are created and logged in the remote server but missing in the local cache.
small gaps can be filled in through changelog sync. However, if the client app has been disconnected for a while, too big of a gap can be created.
A gap can be created for many reasons, such as when a user has been offline for days. When the client app comes back online, the Chat SDK checks with Sendbird server to see if there are any new messages. If it detects more than 300 messages missing in the local cache compared to the remote server, the SDK determines that there is a huge gap and the
onHugeGapDetected is called.
Note: To adjust the number, see this page to learn how to contact support.
In this case, the existing
messageCollection should be cleared through the
dispose() method and a new one must be created for better performance.
dispose() should be called when you need to clear the current chat view. This can be used when the current user leaves the channel or when a huge gap is detected by the
onHugeGapDetected and a new collection needs to be created.