SyncManager SDKs Android v1
SyncManager SDKs Android
SyncManager SDKs
Version 1

Group channel collection

Copy link

A GroupChannelCollection retrieves group channels from both the local cache and Sendbird server and lets you quickly create a channel list view without missing any channel-related updates. This page explains how to make a channel list view using the collection and serves as a migration guide.

Create a collection

Copy link

The GroupChannelCollection is the local caching equivalent of SyncManager’s ChannelCollection. The GroupChannelCollection instance can be created through the createGroupChannelCollection() method.

Create a GroupChannelListQuery instance through the createMyGroupChannelListQuery() method and query setters. This will determine the number of channels to retrieve for the channel list.

Local cachingSyncManager
GroupChannelListQuery query = GroupChannel.createMyGroupChannelListQuery();

groupChannelCollection = new GroupChannelCollection.Builder(query)

Channel events

Copy link

In local caching, the GroupChannelCollectionHandler() is used to determine how the client app reacts to channel-related events.

The following table shows when to call each event handler.

EventCalled when


- A new group channel is created as a real-time event.
- New group channels are fetched by changelog sync.
- It replaces SyncManager's ChannelEventAction.INSERT.


- The channel information that is included in the user's current chat view is updated as a real-time event.
- Updated channel information is fetched during changelog sync.
- It replaces SyncManager's ChannelEventAction.UPDATE and ChannelEventAction.MOVE.


- A group channel is deleted as a real-time event.
- A channel deletion event is fetched during changelog sync.
- It replaces SyncManager's ChannelEventAction.REMOVE.

SyncManager's onChannelEvent(), which is used to handle real-time events, should be changed as shown in the code below.

Local cachingSyncManager
groupChannelCollection.setCollectionHandler(new GroupChannelCollectionHandler() {

   public void onChannelsAdded(@NonNull GroupChannelContext context, @NonNull List<GroupChannel> channels) {

   public void onChannelsUpdated(@NonNull GroupChannelContext context, @NonNull List<GroupChannel> channels) {

   public void onChannelsDeleted(@NonNull GroupChannelContext context, @NonNull List<String> deletedChannelUrls) {

List channels

Copy link

SyncManager's fetch() method retrieves channels from the local cache and delivers them to the ChannelCollectionHandler instance. In local caching, the GroupChannelCollection can retrieve channels through two new interfaces, hasMore() and loadMore().

By default, cached channels are listed in reverse chronological order, meaning the channel that most recently received a message appears at the top of the list. The channel order is automatically updated in the local cache when a new message arrives.



- Checks if there are more channels to load.
- Called whenever a user scroll reaches the bottom of the channel list.


- If hasMore() is true, retrieves channels from the local cache to show in the channel list.
- Called whenever a user scroll reaches the bottom of the channel list.

Local cachingSyncManager
if (groupChannelCollection.hasMore()) {
   groupChannelCollection.loadMore(new OnChannelLoadResultHandler() {
       public void onResult(List<GroupChannel> channelList, SendBirdException e) {
          // The channel list returns as a callback.

Dispose of the collection

Copy link

SyncManager's ChannelCollection has the remove() method that clears all the channels managed by the collection and stops the synchronization process of the collection.

On the other hand, local caching uses the dispose() method to clear the existing channel list. This method should be called when the user closes the channel list so that the GroupChannelCollectionHandler stops making changes to the channel list view.

Local cachingSyncManager