An open channel is a Twitch-style public chat where users can easily join without permission. Sendbird Chat SDK now supports two operation systems for open channels, which are classic and dynamic partitioning. These two systems offer the same features and functions, except that dynamic partitioning allows open channels to accommodate a massive number of users.
Open channels can be used in short-lived live events, such as streaming, news-feed type messaging to massive audience, or events that don't require a permanent membership.
Note: To learn about differences between open channels and group channels, see Channel types.
Classic open channels are the original open channels Sendbird has been providing, and a single classic open channel can handle up to 1,000 participants.
Note: Sendbird applications created before December 15, 2020, are using classic open channels. The classic open channels will be deprecated soon, but the classic channels created up until the deprecation date will remain and function the same way. When the deprecation takes place, all Chat SDK users will be automatically migrated to the new dynamic partitioning system. If you wish to convert to dynamic partitioning open channels beforehand, contact our support team.
On the other hand, dynamic partitioning open channels are designed to accommodate much greater number of users than the classic open channels. The dynamic partitioning open channels can have subchannels where you can divide users evenly.
Learn more about how dynamic partitioning open channel operates in the Open channel guide of Platform API.
An open channel is ideal for use cases that require a small and static number of channels. To create an open channel from the Sendbird Dashboard, do the following:
In your dashboard, go to the Chat > Open channels, and then click Create channel at the top-right corner.
In the dialog box that appears, specify the name, unique URL, cover image, and custom type of a channel.
You can also create a channel on demand or dynamically through the Chat SDK or the Chat API.
SwiftObjective-C
SBDOpenChannel.createChannel(withName: NAME, coverUrl: COVER_URL, data: DATA, operatorUsers: OPERATOR_USERS, completionHandler: { (openChannel, error) in
guard error == nil else {
// Handle error.
}
// An open channel is successfully created.
// Through the "openChannel" parameter of the callback method,
// you can get the open channel's data from the result object that Sendbird server has passed to the callback method.
let channelUrl = openChannel?.channelUrl
})
Otherwise, you can create an open channel by configuring a SBDOpenChannelParams object like the following.
SwiftObjective-C
var ops: [String] = []
ops.append("Jeff")
var params = SBDOpenChannelParams()
params.operatorUserIds = ops // Or .operators
params.name = NAME
params.channelUrl = UNIQUE_CHANNEL_URL // In an open channel, you can create a new channel by specifying its unique channel URL.
params.coverImage = FILE // Or .coverUrl
params.data = DATA
params.customType = CUSTOM_TYPE
SBDOpenChannel.createChannel(with: params, completionHandler: { (openChannel, error) in
guard error == nil else {
// Handle error.
}
// An open channel with detailed configuration is successfully created.
// By using openChannel.channelUrl, openChannel.data, openChannel.customType, and so on,
// you can access the result object from Sendbird server to check your SBDOpenChannelParams configuration.
let channelUrl = openChannel?.channelUrl
})
When creating a channel, you can also append additional information like cover image and description by passing several arguments to the corresponding parameters.
SwiftObjective-C
SBDOpenChannel.createChannel(withName: NAME, coverImage: COVER_IMAGE, coverImageName: "", data: DATA, operatorUsers: OPERATOR_USERS, customType: CUSTOM_TYPE, progressHandler: nil) { (openChannel, error) in
guard error == nil else {
// Handle error.
}
// An open channel with detailed configuration is successfully created.
let channelUrl = openChannel?.channelUrl
}
Type: NSString Specifies the channel topic, or the name of the channel.
COVER_IMAGE
Type: NSData Uploads a file for the cover image of the channel.
DATA
Type: NSString Specifies additional channel information such as a long description of the channel or JSON formatted string.
OPERATOR_USERS
Type: NSArray Specifies an array of one or more users to register as operators of the channel. Operators can delete any messages, and also view all messages in the channel without any filtering or throttling.
CUSTOM_TYPE
Type: NSString Specifies the custom channel type which is used for channel grouping.
Note: See the Advanced section for more information on cover images and custom types.
Note: By default, the Allow creating open channels option is turned on which means that open channels can be created by any user with Sendbird Chat SDK. This may grant access to unwanted data or operations, leading to potential security concerns. To manage your access control settings, you can turn on or off each option in Settings > Application > Security > Access control list on Sendbird Dashboard.
A user must enter an open channel to receive messages. The user can enter up to 10 open channels at once, but the connection is only valid within the current session. When a user who is disconnected from Sendbird server with the disconnectWithCompletionHandler: reconnects to the server with connectWithUserId:, you should make sure the user re-enters the channels in order to continue receiving messages.
When a user who is already a participant in an open channel moves the app to the background, the user will be disconnected from Sendbird server. But when the user's app returns to the foreground, the Chat SDK will automatically re-enter the user to the participating channel.
Note: When a user is reconnected by attempts of the SBDMain instance from a temporary unstable connection, the Chat SDK will automatically re-enter the user to the participating channel.
SwiftObjective-C
SBDOpenChannel.getWithUrl(CHANNEL_URL, completionHandler: { (openChannel, error) in
guard error == nil else {
// Handle error.
}
// Call the instance method of the result object in the "openChannel" parameter of the callback method.
openChannel?.enter(completionHandler: { (error) in
guard error == nil else {
// Handle error.
}
// The current user successfully enters the open channel,
// and can chat with other users in the channel by using APIs.
})
})
If a user exits an open channel, the user can't receive any messages from that channel.
SwiftObjective-C
SBDOpenChannel.getWithUrl(CHANNEL_URL, completionHandler: { (openChannel, error) in
guard error == nil else {
// Handle error.
}
// Call the instance method of the result object in the "openChannel" parameter of the callback method.
openChannel?.exitChannel(completionHandler: { (error) in
guard error == nil else {
// Handle error.
}
// The current user successfully exits the open channel.
})
})
An open channel can be freezed only with the Sendbird Dashboard or Chat API as opposed to a group channel which operators of the channel can do that via the Chat SDK.
To freeze a channel, go to Chat > Open channels on the dashboard, select an open channel, and click the Freeze icon at the upper right corner. To unfreeze, select the frozen channel and click the Freeze icon again.
Note : In a frozen channel, participants can't chat with each other but the operators can send a message to the channel.
You can retrieve a list of open channels by using the SBDOpenChannelListQuery's loadNextPageWithCompletionHandler: method which returns a list of SBDOpenChannel objects.
SwiftObjective-C
let listQuery = SBDOpenChannel.createOpenChannelListQuery()!
listQuery.loadNextPage(completionHandler: { (openChannels, error) in
guard error == nil else {
// Handle error.
}
// A list of open channels is successfully retrieved.
// Through the "openChannels" parameter of the callback method,
// you can access the data of each open channel from the result list that Sendbird server has passed to the callback method.
self.channels += openChannels!
...
})
Since a channel URL is a unique identifier of an open channel, you can use a URL when retrieving a channel object.
SwiftObjective-C
SBDOpenChannel.getWithUrl(CHANNEL_URL, completionHandler: { (openChannel, error) in
guard error == nil else {
// Handle error.
}
// Through the "openChannel" parameter of the callback method,
// the open channel object identified with the CHANNEL_URL is returned by Sendbird server,
// and you can get the open channel's data from the result object.
let channelName = openChannel?.name
...
})
Note: We recommend that you store a user's channel URLs to handle the lifecycle or state changes of your app, or any other unexpected situations. For example, when a user is disconnected from Sendbird server due to switching to another app temporarily, you can provide a smooth restoration of the user's state using a stored URL to fetch the appropriate channel instance.
In addition to these message types, you can further subclassify a message by specifying its custom type. This custom type takes on the form of a NSString and can be used to search or filter messages. It allows you to append information to your message and customize message categorization.
The following code shows several types of parameters that you can configure to customize text messages by using SBDUserMessageParams. Under the SBDUserMessageParams object, you can assign values to message, data and other properties. By assigning arbitrary string to the data property, you can set custom font size, font type or JSON object. To send your messages, you need to pass the SBDUserMessageParams object as an argument to the parameter in the sendUserMessageWithParams:completionHandler: method.
Through the completionHandler of the sendUserMessageWithParams:completionHandler: method, Sendbird server always notifies whether your message has been successfully sent to the channel. When there is a delivery failure due to network issues, an exception is returned through the callback method.
SwiftObjective-C
var params = SBDUserMessageParams()
params.message = MESSAGE
params.customType = CUSTOM_TYPE
params.data = DATA
params.mentionType = SBDMentionTypeUsers // Either SBDMentionTypeUsers or SBDMentionTypeChannel
params.mentionedUserIds = ["Jeff", "Julia"] // Or .mentionedUsers = LIST_OF_USERS_TO_MENTION
params.metaArrays = ["itemType": ["tablet"], "quality": ["best", "good"]] // A key-value pair
params.targetLanguages = ["fr", "de"] // French and German
params.pushNotificationDeliveryOption = .default
openChannel.sendUserMessage(with: params, completionHandler: { (userMessage, error) in
guard error == nil else {
// Handle error.
}
// A text message with detailed configuration is successfully sent to the channel.
// By using userMessage.messageId, userMessage.message, userMessage.customType, and so on,
// you can access the result object from Sendbird server to check your SBDUserMessageParams configuration.
// The current user can receive messages from other users through the didReceiveMessage() method of an event delegate.
let messageId = userMessage?.messageId;
})
A user can also send binary files through the Chat SDK. The two ways to send a binary file are: sending the file itself, or sending a URL.
Sending a raw file means you're uploading it to Sendbird server where it can be downloaded in client apps. When you upload a file directly to the server, there is a size limit imposed on the file depending on your plan. You can see the limit in your dashboard and adjust it with our sales team.
The other option is to send a file hosted on your server. You can pass the file's URL, which represents its location, as an argument to a parameter. In this case, your file is not hosted on Sendbird server and it can only be downloaded from your own server. When you send a file message with a URL, there is no limit on the file size since it's not directly uploaded to Sendbird server.
Note: You can use sendFileMessagesWithParams:progressHandler:sentMessageHandler:completionHandler:, which is another method that allows you to send up to 20 file messages per one method call. Refer to our API Reference to learn more about it.
The following code shows several types of parameters that you can configure to customize your file messages by using SBDFileMessageParams. Under the SBDFileMessageParams object, you can assign specific values to customType and other properties. To send your messages, you need to pass the SBDFileMessageParams object as an argument to the parameter in the sendFileMessageWithParams:completionHandler: method.
Through the completionHandler of the sendFileMessageWithParams:completionHandler: method, Sendbird server always notifies whether your message has been successfully sent to the channel. When there is a delivery failure due to network issues, an exception is returned through the callback method.
SwiftObjective-C
// Sending a file message with a raw file
var thumbnailSizes = [SBDThumbnailSize]()
thumbnailSizes.append(SBDThumbnailSize.make(withMaxCGSize: CGSize(width: 100.0, height: 100.0))!) // Allowed number of thumbnail images: 3
thumbnailSizes.append(SBDThumbnailSize.make(withMaxWidth: 200.0, maxHeight: 200.0)!)
var params = SBDFileMessageParams()
params.file = FILE // Or .fileUrl = FILE_URL (You can also send a file message with a file URL.)
params.fileName = FILE_NAME
params.fileSize = FILE_SIZE
params.mimeType = MIME_TYPE
params.thumbnailSizes = thumbnailSizes
params.customType = CUSTOM_TYPE
params.mentionType = SBDMentionTypeUsers // Either SBDMentionTypeUsers or SBDMentionTypeChannel
params.mentionedUserIds = ["Jeff", "Julia"] // Or .mentionedUsers = LIST_OF_USERS_TO_MENTION
params.pushNotificationDeliveryOption = SBDPushNotificationDeliveryOptionDefault
openChannel.sendFileMessage(with: params, completionHandler: { (fileMessage, error) in
guard error == nil else {
// Handle error.
}
// A file message with detailed configuration is successfully sent to the channel.
// By using fileMessage.messageId, fileMessage.fileName, fileMessage.customType, and so on,
// you can access the result object from Sendbird server to check your SBDFileMessageParams configuration.
// The current user can receive messages from other users through the didReceiveMessage() method of an event delegate.
let messageId = fileMessage?.messageId
})
If your app goes to the background while uploading a file such as a profile image or picture, the app can complete the uploading process using the application:handleEventsForBackgroundURLSession:completionHandler: method in your AppDelegate. To complete a file upload in progress on the background, a background event delegate should be added and implemented in the AppDelegate. If you don't want to upload a file on the background mode, remove the following delegation in the AppDelegate.
SwiftObjective-C
// AppDelegate.swift
class AppDelegate: UIResponder, UIApplicationDelegate {
func application(_ application: UIApplication, handleEventsForBackgroundURLSession identifier: String, completionHandler: @escaping () -> Void) {
debugPrint("method for handling events for background URL session is waiting to be process. background session id: \(identifier)")
completionHandler()
}
}
A critical alert is a notification that can be sent to iOS devices even when mute or Do Not Disturb is turned on. Critical alert messages can be sent to iOS devices through the sendUserMessageWithParams:completionHandler: and sendFileMessageWithParams:completionHandler: methods. To do so, create an SBDAppleCriticalAlertOptions instance and set it as an attribute of a SBDUserMessageParams instance. Then pass the created SBDUserMessageParams instance as an argument to a parameter in the sendUserMessageWithParams:completionHandler: or sendFileMessageWithParams:completionHandler: method.
The current user can receive messages sent by other participants through the channel:didReceiveMessage: method in the channel delegate. A SBDBaseMessage object for each received message is one of the following message types.
A text message sent by an admin through the Chat API
The UNIQUE_DELEGATE_ID is a unique identifier to register multiple concurrent delegates.
SwiftObjective-C
class OpenChannelChattingViewController: UIViewController, SBDChannelDelegate {
SBDMain.add(self, identifier: self.delegateIdentifier)
func channel(_ sender: SBDBaseChannel, didReceive message: SBDBaseMessage) {
// You can customize how to display the different types of messages with the result object in the "message" parameter.
if message is SBDUserMessage {
...
}
else if message is SBDFileMessage {
...
}
else if message is SBDAdminMessage {
...
}
}
}
If the UI isn't valid anymore, remove the channel delegate.
When replying to a message through the sendUserMessageWithParams:completionHandler: method, you should specify and pass a SBDUserMessageParams object to the method as a parameter.
SwiftObjective-C
// Create a `SBDUserMessageParams` object.
let params = SBDUserMessageParams(message: MESSAGE_TEXT)
params?.parentMessageId = PARENT_MESSAGE_ID
...
// Pass the params to the parameter in the `sendUserMessageWithParams:completionHandler:` method.
openChannel?.sendUserMessage(with: params!, completionHandler: { (message, error) in
if error != nil {
// Handle error.
}
// A reply to a specific message in the form of a text message is successfully sent.
...
})
Type: long long Specifies the unique ID of a parent message which has a thread of replies. If the message sent through the sendUserMessageWithParams:completionHandler: method is a parent message, the value of this property is 0. If the message is a reply to a parent message, the value is the message ID of the parent message.
When replying with a file message through the sendFileMessageWithParams:completionHandler: method, you should specify and pass a SBDFileMessageParams object to the method as a parameter.
SwiftObjective-C
// Create a `SBDFileMessageParams` object.
let params = SBDFileMessageParams(file: FILE!)
params?.parentMessageId = PARENT_MESSAGE_ID // This specifies the unique ID of a parent message which has a thread of replies. If the message sent through the `sendFileMessageWithParams:completionHandler:` method is a parent message, the value of this property is 0.
...
// Pass the params to the parameter in the `sendFileMessageWithParams:completionHandler:` method.
openChannel?.sendFileMessage(with: params!, completionHandler: { (message, error) in
if error != nil {
// Handle error.
}
// A reply to a specific message in the form of a file message is successfully sent.
...
})
Type: long long Specifies the unique ID of a parent message which has a thread of replies. If the message sent through the sendFileMessageWithParams:completionHandler: method is a parent message, the value of this property is 0. If the message is a reply to a parent message, the value is the message ID of the parent message.
When a participant wants to call the attention of other participants in an open channel where push notifications are not allowed by default, they can mention those participants in a message. To do so, you should:
By using the loadPreviousMessagesWithLimit:reverse:completionHandler: method of a SBDPreviousMessageListQuery instance which returns a list of SBDBaseMessage objects, you can retrieve a set number of previous messages in an open channel. With a returned list, you can display the past messages in your UI once they have loaded.
SwiftObjective-C
// There should be only one single instance per channel.
let listQuery = openChannel.createPreviousMessageListQuery()
listQuery?.customTypeFilter = "greeting"
// Retrieving previous messages
listQuery?.loadPreviousMessages(withLimit: LIMIT, reverse: REVERSE, completionHandler: { (messages, error) in
guard error == nil else {
// Handle error.
}
})
Type: NSInteger Specifies the number of results to return per call. Acceptable values are 1 to 100, inclusive. The recommended value for this parameter is 30.
REVERSE
Type: BOOL Determines whether to sort the retrieved messages in reverse order. If set to YES, returns a list of messages which the latest comes at first and the earliest at last. the results are sorted in reverse order. If set to NO, returns a list of messages which the earliest comes at first and the latest at last.
A limit parameter determines how many messages to be included in a returned list. A SBDPreviousMessageListQuery instance itself does pagination of a result set according to the value of the limit parameter, and internally manages a token to retrieve the next page in the result set.
Each time the loadPreviousMessagesWithLimit:reverse:completionHandler: method is called, the instance retrieves a set number of messages in the next page and then updates the token's value to complete the current call and prepare a next call.
If you create a new query instance and call the loadPreviousMessagesWithLimit:reverse:completionHandler: method, a set number of the most recent messages are retrieved because its token has nothing to do with the previously created instance. So we recommend that you create a single query instance and store it as a member variable for traversing through the entire message history.
Note: Before calling the loadPreviousMessagesWithLimit:reverse:completionHandler: method again, you should receive a success callback through the completionHandler first.
The following code shows several types of parameters that you can configure to customize a message query by using SBDMessageListParams. Under the SBDMessageListParams object, you can assign specific values to previousResultSize, messageType, and other properties. To retrieve messages in a channel, you need to pass the SBDMessageListParams object as an argument to the parameter in the getMessagesByTimestamp:params:completionHandler: method.
SwiftObjective-C
var params = SBDMessageListParams()
params.isInclusive = IS_INCLUSIVE
params.previousResultSize = PREVIOUS_RESULT_SIZE
params.nextResultSize = NEXT_RESULT_SIZE
params.reverse = REVERSE
params.messageType = MESSAGE_TYPE
params.customType = CUSTOM_TYPE
...
openChannel.getMessagesByTimestamp(TIMESTAMP, params: params, completionHandler: { (messages, error) in
guard error == nil else {
// Handle error.
}
// A list of previous and next messages on both sides of a specified timestamp is successfully retrieved.
// Through the "messages" parameter of the callback method,
// you can access and display the data of each message from the result list that Sendbird server has passed to the callback method.
self.messages += messages!
...
})
Type: long long Specifies the timestamp to be the reference point of a retrieval, in Unix milliseconds.
IS_INCLUSIVE
Type: BOOL Determines whether to include the messages sent exactly on the TIMESTAMP.
PREVIOUS_RESULT_SIZE
Type: NSInteger Specifies the number of messages to retrieve, which are sent previously before a specified timestamp. Note that the actual number of results may be larger than the set value when there are multiple messages with the same timestamp as the earliest message.
NEXT_RESULT_SIZE
Type: NSInteger Specifies the number of messages to retrieve, which are sent later after a specified timestamp. Note that the actual number of results may be larger than the set value when there are multiple messages with the same timestamp as the latest message.
REVERSE
Type: BOOL Determines whether to sort the retrieved messages in reverse order.
MESSAGE_TYPE
Type: SBDMessageTypeFilter Specifies the message type to filter the messages with the corresponding type. Acceptable values are SBDMessageTypeFilterAll, SBDMessageTypeFilterUser, SBDMessageTypeFilterFile, and SBDMessageTypeFilterAdmin.
CUSTOM_TYPE
Type: NSString Specifies the custom message type to filter the messages with the corresponding custom type.
var params = SBDMessageListParams()
params.isInclusive = IS_INCLUSIVE
params.previousResultSize = PREVIOUS_RESULT_SIZE
params.nextResultSize = NEXT_RESULT_SIZE
params.reverse = REVERSE
params.messageType = MESSAGE_TYPE
params.customType = CUSTOM_TYPE
openChannel.getMessages(byMessageId: MESSAGE_ID, params: params, completionHandler: { (messages, error) in
guard error == nil else {
// Handle error.
}
// A list of previous and next messages on both sides of a specified message ID is successfully retrieved.
// Through the "messages" parameter of the callback method,
// you can access and display the data of each message from the result list that Sendbird server has passed to the callback method.
self.messages += messages!
})
Type: long long Specifies the unique ID of the message to be the reference point of a retrieval.
IS_INCLUSIVE
Type: BOOL Determines whether to include the message identified with a specified message ID.
PREVIOUS_RESULT_SIZE
Type: NSInteger Specifies the number of messages to retrieve, which are sent previously before a specified message ID.
NEXT_RESULT_SIZE
Type: NSInteger Specifies the number of messages to retrieve, which are sent later after a specified timestamp.
REVERSE
Type: BOOL Determines whether to sort the retrieved messages in reverse order.
MESSAGE_TYPE
Type: SBDMessageTypeFilter Specifies the message type to filter the messages with the corresponding type. Acceptable values are SBDMessageTypeFilterAll, SBDMessageTypeFilterUser, SBDMessageTypeFilterFile, and SBDMessageTypeFilterAdmin.
CUSTOM_TYPE
Type: NSString Specifies the custom message type to filter the messages with the corresponding custom type.
Type: NSInteger Specifies the number of results to return per call. Acceptable values are 1 to 100, inclusive. The recommended value for this parameter is 30.
REVERSE
Type: BOOL Determines whether to sort the retrieved messages in reverse order. If false, the results are in ascending order.
INCLUDE_THREAD_INFO
Type: BOOL Determines whether to include the thread information of the messages in the results when the results contain parent messages.
REPLY_TYPE
Type: ENUM
Specifies the type of message to include in the results. - NONE (default): All messages that are not replies. These message may or may not have replies in its thread. - ALL: All messages including threaded and non-threaded parent messages as well as its replies. - ONLY_REPLY_TO_CHANNEL: Messages that are not threaded. It only includes the parent messages and replies that were sent to the channel.
INCLUDE_PARENT_MESSAGE_INFO
Type: BOOL
Determines whether to include the information of the parent messages in the result. (Default: false)
INCLUDE_REPLIES
(Deprecated)Type: BOOL Determines whether to include replies in the results.
INCLUDE_PARENT_MESSAGE_TEXT
Type: BOOL Determines whether to include the parent message text in the results when the retrieved messages are replies in a thread. If the type of the parent message is SBDUserMessage, the value is a message property. If it is a SBDFileMessage, the value is the name of the uploaded file.
Type: NSInteger Specifies the number of messages to retrieve that were sent before the specified timestamp or message ID.
nextResultSize
Type: NSInteger Specifies the number of messages to retrieve that were sent after the specified timestamp or message ID.
isInclusive
Type: BOOL Determines whether to include the messages with the matching timestamp or message ID in the results.
reverse
Type: BOOL Determines whether to sort the retrieved messages in reverse order. If false, the results are in ascending order.
includeThreadInfo
Type: BOOL Determines whether to include the thread information of the messages in the results when the results contain parent messages.
replyType
Type: ENUM
Specifies the type of message to include in the results. - NONE (default): All messages that are not replies. These message may or may not have replies in its thread. - ALL: All messages including threaded and non-threaded parent messages as well as its replies. - ONLY_REPLY_TO_CHANNEL: Messages that are not threaded. It only includes the parent messages and replies that were sent to the channel.
includeParentMessageInfo
Type: BOOL
Determines whether to include the information of the parent messages in the result. (Default: false)
includeReplies
(Deprecated)Type: BOOL Determines whether to include replies in the results.
includeParentMessageText
(Deprecated)Type: BOOL Determines whether to include the parent message text in the results when the messages are replies in a thread. If the type of the parent message is SBDUserMessage, the value is a message property. If it is SBDFileMessage, the value is the name of the uploaded file.
The getMessagesByTimestamp:params:completionHandler: method returns a set number of messages of previous and next messages on both sides of a specific timestamp in a channel.
SwiftObjective-C
openChannel?.getMessagesByTimestamp(TIMESTAMP, params: params, completionHandler: { (messages, error) in
if error != nil {
// Handle error.
}
// A list of previous and next messages on both sides of a specified timestamp is successfully retrieved.
// Through the "messages" parameter of the callback method,
// you can access and display the data of each message from the result list that Sendbird server has passed to the callback method.
self.messages += messages!
...
})
Type: Long Specifies the timestamp to be the reference point for messages to retrieve, in Unix milliseconds format. Messages sent before or after the timestamp can be retrieved.
The getMessagesByMessageId:params:completionHandler: method returns a set number of previous and next messages on both sides of a specific message ID in a channel.
SwiftObjective-C
openChannel?.getMessagesByMessageId(MESSAGE_ID, params: params, completionHandler: { (messages, error) in
if error != nil {
// Handle error.
}
// A list of previous and next messages on both sides of a specified message ID is successfully retrieved.
// Through the "messages" parameter of the callback method,
// you can access and display the data of each message from the result list that Sendbird server has passed to the callback method.
self.messages += messages!
...
})
Type: long long Specifies the message ID to be the reference point for messages to retrieve. Messages sent before or after the message with the matching message ID can be retrieved.
// Create a `SBDThreadedMessageListParams` object.
let params = SBDThreadedMessageListParams()
params.previousResultSize = PREV_RESULT_SIZE
params.nextResultSize = NEXT_RESULT_SIZE
params.isInclusive = INCLUSIVE
params.reverse = REVERSE
params.includeParentMessageInfo = INCLUDE_PARENT_MESSAGE_INFO
...
// Pass the params to the parameter in the `getThreadedMessagesByTimestamp:params:completionHandler:` method.
parentMessage.getThreadedMessages(byTimestamp: TIMESTAMP, params: params) { (parentMessage, threadedReplies, error) in
if error != nil {
// Handle error.
}
// A list of replies of the specified parent message timestamp is successfully retrieved.
// Through the "threadedReplies" parameter of the callback method,
// you can access and display the data of each message from the result list that Sendbird server has passed to the callback method.
...
}
Type: long long Specifies the timestamp to be the reference point of the retrieval, in Unix milliseconds format.
PREV_RESULT_SIZE
Type: NSInteger Specifies the number of messages to retrieve that were sent before the specified timestamp.
NEXT_RESULT_SIZE
Type: NSInteger Specifies the number of messages to retrieve that were sent after the specified timestamp.
INCLUSIVE
Type: BOOL Determines whether to include the messages with the matching timestamp in the results.
REVERSE
Type: BOOL Determines whether to sort the retrieved messages in reverse order. If false, the results are in ascending order.
INCLUDE_PARENT_MESSAGE_INFO
Type: BOOL
Determines whether to include the information of the parent messages in the result. (Default: false)
INCLUDE_PARENT_MESSAGE_TEXT
(Deprecated)Type: BOOL Determines whether to include the parent message text in the results when the messages are replies in a thread. If the type of the parent message is SBDUserMessage, the value is a message property. If it is SBDFileMessage, the value is the name of the uploaded file.
// Create a `SBDMessageRetrievalParams` object.
let params = SBDMessageRetrievalParams()
params.messageId = MESSAGE_ID
params.channelType = CHANNEL_TYPE
params.channelUrl = CHANNEL_URL
...
// Pass the params to the parameter of the `getMessageWithParams:completionHandler:` method.
SBDBaseMessage.getWith(params) { (message, error) in
if error != nil {
// Handle error.
}
// The specified message is successfully retrieved.
...
}
A user can update any of their own text and file messages sent. An error is returned if a user attempts to update another user's messages. In addition, channel operators can update any messages sent in the channel.
SwiftObjective-C
// For a text Message
var params = SBDUserMessageParams(message: NEW_TEXT_MESSAGE)
params.customType = NEW_CUSTOM_TYPE
params.data = NEW_DATA
// The USER_MESSAGE_ID below indicates the unique message ID of a UserMessage object to update.
openChannel.updateUserMessage(withMessageId: USER_MESSAGE_ID, userMessageParams: params, completionHandler: { (userMessage, error) in
guard error == nil else {
// Handle error.
}
// The message is successfully updated.
// Through the "userMessage" parameter of the callback method,
// you could check if the update operation has been performed right.
let text = userMessage?.message
...
})
// For a file message
var params = SBDFileMessageParams(fileUrl: NEW_FILE_URL)
params.fileName = NEW_FILE_NAME
params.fileSize = NEW_FILE_SIZE
params.customType = NEW_CUSTOM_TYPE
// The FILE_MESSAGE_ID below indicates the unique message ID of a FileMessage object to update.
openChannel.updateFileMessage(withMessageId: FILE_MESSAGE_ID, fileMessageParams: params, completionHandler: { (fileMessage, error) in
guard error == nil else {
// Handle error.
}
// The message is successfully updated.
// Through the "fileMessage" parameter of the callback method,
// you could check if the update operation has been performed right.
let customType = fileMessage?.customType
...
})
If a message is updated, the channel:didUpdateMessage: method in the channel delegate will be invoked on all channel participants' devices except the one that updated the message.
A user can delete any messages sent by themselves. An error is returned if a user attempts to delete the messages of other participants. Also operators of an open channel can delete any messages in a channel.
SwiftObjective-C
// The BASE_MESSAGE below indicates a BaseMessage object to delete.
openChannel.delete(BASE_MESSAGE, completionHandler: { (error) in
guard error == nil else {
// Handle error.
}
// The message is successfully deleted from the channel.
...
})
If a message is deleted, the channel:messageWasDeleted: method in the channel delegate will be invoked on all channel participants' devices including the one that deleted the message.
To retrieve the latest and updated information on each online participant in an open channel, you need another SBDParticipantListQuery instance for the channel. Like the Retrieve a list of participants section above, create a new query instance using the createParticipantListQuery(), and then call its loadNextPageWithCompletionHandler: method consecutively to retrieve the latest.
You can also retrieve the latest and updated information on users at the application level. Like the Retrieve a list of users section, create a SBDApplicationUserListQuery instance using the SBDMain's createApplicationUserListQuery(), and then call its loadNextPageWithCompletionHandler: method consecutively to retrieve the latest.
When retrieving the online (connection) status of a user, by checking the connectionStatus of each SBDUser object in a returned list, you can get the user's current connection status. The connectionStatus has one of the following two values:
Note: If you need to keep track of the connection status of some users in real time, we recommend that you call periodically the loadNextPageWithCompletionHandler: method of a SBDApplicationUserListQuery instance after specifying its userIdsFilter filter, perhaps in intervals of one minute or more.
You can register participants as an operator of an open channel.
SwiftObjective-C
openChannel.addOperators(withUserIds: [USER_ID_1, USER_ID_2]) { (error) in
guard error == nil else {
// Handle error.
}
// The participants are successfully registered as operators of the channel.
...
}
You can cancel the registration of operators from an open channel but leave them as participants.
SwiftObjective-C
openChannel.removeOperators(withUserIds: [USER_ID_1, USER_ID_2]) { (error) in
guard error == nil else {
// Handle error.
}
// The cancel operation is succeeded,
// and you could display some message to those who are not operators anymore.
...
}
If you want to cancel the registration of all operators in a channel at once, use the following code.
You can create a query to retrieve a list of banned or muted users from an open channel. This query is only available for users who are registered as operators of an open channel.
Operators of an open channel can remove any users that behave inappropriately in the channel by using our Ban feature. Banned users are immediately expelled from a channel and allowed to participate in the channel again after the time period set by the operators. Operators can ban and unban users from open channels using the following code.
SwiftObjective-C
SBDOpenChannel.getWithUrl(CHANNEL_URL, completionHandler: { (openChannel, error) in
guard error == nil else {
// Handle error.
}
if openChannel!.isOperator(with: SBDMain.getCurrentUser()!) {
// Ban a user.
openChannel?.ban(USER, seconds: SECONDS, completionHandler: { (error) in
guard error == nil else {
// Handle error.
}
// The user is successfully banned from the channel.
// You could notify the user of being banned by displaying a prompt.
...
})
// Unban a user.
openChannel?.unbanUser(USER, completionHandler: { (error) in
guard error == nil else {
// Handle error.
}
// The user is successfully unbanned for the channel.
// You could notify the user of being unbanned by displaying a prompt.
...
})
}
})
Operators of an open channel can prohibit selected users from sending messages using our Mute feature. Muted users remain in the channel and are allowed to view the messages, but can't send any messages until the operators unmute them. Operators can mute and unmute users in open channels using the following code:
SwiftObjective-C
SBDOpenChannel.getWithUrl(CHANNEL_URL, completionHandler: { (openChannel, error) in
guard error == nil else {
// Handle error.
}
if openChannel?.isOperator(with: USER) ?? false {
// Mute a user.
openChannel?.muteUser(USER, completionHandler: { (error) in
guard error == nil else {
// Handle error.
}
// The user is successfully muted in the channel.
// You could notify the user of being muted by displaying a prompt.
...
})
// Unmute a user.
openChannel?.unmuteUser(USER, completionHandler: { (error) in
guard error == nil else {
// Handle error.
}
// The user is successfully unmuted in the channel.
// You could notify the user of being unmuted by displaying a prompt.
...
})
}
})
In an open channel, a user can report suspicious or harassing messages as well as the other users who use abusive language. The user can also report channels if there are any inappropriate content or activity within the channel. Based on this feature and our report API, you can build your own in-app system for managing objectionable content and subject.
Specifies the message to report for its suspicious, harassing, or inappropriate content.
OFFENDING_USER
object
Specifies the user who uses offensive or abusive language such as sending explicit messages or inappropriate comments.
REPORT_CATEGORY
enum
Specifies a report category which indicates the reason for reporting. Acceptable values are SBDReportCategorySuspicious, SBDReportCategoryHarassing, SBDReportCategoryInappropriate, and SBDReportCategorySpam.
DESCRIPTION
string
Specifies additional information to include in the report.