Message Classification

IM messages are classified by message destination into two types: one-to-one messages (also called C2C messages) and group messages.

IM messages can also be classified by content into text messages, custom (signaling) messages, image messages, video messages, voice messages, file messages, location messages, and group tips.

Sending and Receiving a Simple Message

V2TIMManager.h provides a set of simple APIs for sending and receiving messages. Although these APIs can be used to send or receive text messages and custom (signaling) messages, they are easy to use and only a few minutes are needed to complete interfacing.

Sending text and signaling messages (simplified APIs)

To send text messages, call sendC2CTextMessage or sendGroupTextMessage. Text messages will be filtered by IM for sensitive words. If a message containing sensitive words is sent, the 80001 error code is returned.
To send C2C custom (signaling) messages, call sendC2CCustomMessage or sendGroupCustomMessage. A custom message is essentially a section of the binary buffer, and is often used to transfer custom signaling in your app. Its content is not filtered for sensitive words.

Receiving text and signaling messages (simplified APIs)

To listen to simple text and signaling messages, call addSimpleMsgListener. To listen to complex image, video, and voice messages, call addAdvancedMsgListener defined in V2TIMManager + Message.h.

Note：

Do not use addSimpleMsgListener together with addAdvancedMsgListener. Otherwise, logic bugs may occur.

Typical example: sending and receiving on-screen comments in a livestreaming group

In the livestreaming scenario, it is a common way of communication to send or receive on-screen comments in a livestreaming group. This can be easily implemented through the simple message APIs.

1. The anchor can call createGroup to create a livestreaming group (AVChatRoom) and record the group ID in the list of rooms in "Broadcasting" state.
2. A viewer can select an anchor that he/she likes, and call joinGroup to join the AVChatRoom created by this anchor.
3. The message sender can call sendGroupTextMessage to send a group text message as the on-screen comment.
4. The message recipient can call addSimpleMsgListener to register a simple message listener, and use the listener callback function onRecvGroupTextMessage to obtain text messages.

"FlyHeart" is an instruction. To configure the "FlyHeart" feature for an AVChatRoom, perform the steps below:

1. Define a custom message type, for example, a JSON string { "command": "favor", "value": 101 }.
2. Call sendGroupCustomMessage to send a message, and call onRecvGroupCustomMessage to receive the message.

Sending and Receiving Rich Media Messages

Image, video, voice, file, and location messages are called rich media messages. Compared with simple messages, it is more complex to send or receive rich media messages.

• Before sending a rich media message, use the create function to create a V2TIMMessage object. Then, call the corresponding send API to send this message.
• When receiving the rich media message, check elemType and perform secondary parsing on Elem obtained based on elemType.

Sending rich media messages

The following takes an image message as an example to describe the process of sending a rich media message.

1. The sender calls createImageMessage to create an image message and obtain the V2TIMMessage message object.
2. The sender calls sendMessage to send the previously created message object.

Receiving rich media messages

1. The recipient calls addAdvancedMsgListener to set the advanced message listener.
2. The recipient obtains the V2TIMMessage image message through the onRecvNewMessage listener callback.
3. The recipient parses elemType in [V2TIMMessage](http://doc.qcloudtrtc.com/im/interfaceV2TIMMessage.html, and performs secondary parsing based on the message type to obtain the content of Elem in the message.

Typical example: sending and receiving image messages

The sender creates and sends an image message.

// Obtain the local image path.
NSString *imagePath = [[NSBundle mainBundle] pathForResource:@"test" ofType:@"png"];
// Create an image message.
V2TIMMessage *msg = [[V2TIMManager sharedInstance] createImageMessage:imagePath];
// Send the image message.
[[V2TIMManager sharedInstance] sendMessage:msg receiver:@"userA" groupID:nil 
priority:V2TIM_PRIORITY_DEFAULT 
onlineUserOnly:NO offlinePushInfo:nil progress:^(uint32_t progress) {
   // Image upload progress (0-100)
} succ:^{
   // The image message is successfully sent.
} fail:^(int code, NSString *msg) {
   // The image message fails to be sent.
}];

The recipient identifies the image message, and parses the message to obtain the original image, large image, and thumbnail contained in the message.

- (void)onRecvNewMessage:(V2TIMMessage *)msg {
  if (msg.elemType == V2TIM_ELEM_TYPE_IMAGE) {
    V2TIMImageElem *imageElem = msg.imageElem;
    // An image message contains an image in three different sizes: original image, large image, and thumbnail. (The SDK automatically generates the large image, and thumbnail.)
    - A large image is an image obtained after the original image is proportionally compressed. After the compression, the smaller one of the height and width is equal to 720 pixels.
    - A thumbnail is an image obtained after the original image is proportionally compressed. After the compression, the smaller one of the height and width is equal to 198 pixels.
    NSArray<V2TIMImage *> *imageList = imageElem.imageList;
    for (V2TIMImage *timImage in imageList) {
        NSString *uuid = timImage.uuid; // Image ID
        V2TIMImageType type = timImage.type; // Image type
        int size = timImage.size; // Image size (bytes)
        int width = timImage.width; // Image width
        int height = timImage.height; // Image height
        // Set the image download path `imagePath`. Here, `uuid` can be used as an identifier to avoid repeated download.
        NSString *imagePath = [NSTemporaryDirectory() stringByAppendingPathComponent:
                            [NSString stringWithFormat: @"testImage%@",timImage.uuid]];
        if (![[NSFileManager defaultManager] fileExistsAtPath:imagePath]) {
                [timImage downloadImage:imagePath 
                                progress:^(NSInteger curSize, NSInteger totalSize) {
                    NSLog(@"Image download progress: curSize: %lu,totalSize:%lu",curSize,totalSize);
                } succ:^{
                    NSLog(@"Image download completed");
                } fail:^(int code, NSString *msg) {
                    NSLog(@"Image download failed: code: %d,msg:%@",code,msg);
                }];
        } else {
                // The image already exists.
        }
    }
  }
}

Note：

For more information on the message parsing sample code, see FAQs > 5. How can I parse different types of messages.

Sending and Receiving Group @ Messages

For a group @ message, the sender can listen to the input of the @ character in the input bar and call the group member selection interface. After selection is completed, the format "@A @B @C......" is displayed in the input box, and then the sender can continue to edit the message content and send the message. On the group chat list of the recipient’s conversation interface, the identifier "someone@me" or "@all members" will be displayed to remind the user that the user was mentioned by someone in the group.

Note：

Currently, only text @ messages are supported.

Sending group @ messages

1. The sender listens to the text input box on the chat interface and launches the group member selection interface. After selection is completed, the ID and nickname of the selected member are returned. The ID is used to construct the message object V2TIMMessage, and the nickname is displayed in the text box.
2. The sender calls createTextAtMessage of V2TIMManager+Message to create an @ text message and obtain the message object V2TIMMessage.
3. The sender calls sendMessage to send the previously created @ message object.

Receiving group @ messages

1. During conversation loading and update, the groupAtInfolist API of V2TIMConversation needs to be called to obtain the @ data list of the conversation.
2. Through the atType API of the V2TIMGroupAtInfo object on the list, the @ data type is obtained and updated to the @ information of the current conversation.

Typical examples: sending and receiving group @ messages

• Sending a group @ message:
  The sender creates a group @ message and sends it:

// Obtain the ID data of the @ group member.
TUITextMessageCellData *text = (TUITextMessageCellData *)data;
NSMutableArray<NSString *> *atUserList = text.atUserList;

// Create a group @ message.
V2TIMMessage *atMsg = [[V2TIMManager sharedInstance] createTextAtMessage:text.content atUserList:atUserList];

// Send the group @ message.
[[V2TIMManager sharedInstance] sendMessage:atMsg
                                  receiver:nil
                                   groupID:@"toGroupId"
                                  priority:V2TIM_PRIORITY_DEFAULT
                            onlineUserOnly:NO
                           offlinePushInfo:nil
                                  progress:nil
                                      succ:^{
    NSLog(@"group @ message is sent successfully");
}
                                      fail:^(int code, NSString *desc) {
    NSLog(@"group @ message failed to be sent");
}];

• Receiving a group @ message:
  During conversation loading and update, obtain the group @ data list, parse the current @ type, and display the prompt text based on the @ type.

// Obtain the group @ data list.
NSArray<V2TIMGroupAtInfo *> *atInfoList = conversation.groupAtInfolist;

// Parse the @ type (@me, @all members, @me, and @all members).
BOOL atMe = NO;         // Whether it’s @me
BOOL atAll = NO;        // Whether it’s @all members
NSString *atTipsStr = @"";
for (V2TIMGroupAtInfo *atInfo in atInfoList) {
    switch (atInfo.atType) {
        case V2TIM_AT_ME:
            atMe = YES;
            break;
        case V2TIM_AT_ALL:
            atAll = YES;
            break;
        case V2TIM_AT_ALL_AT_ME:
            atMe = YES;
            atAll = YES;
            break;
        default:
            break;
    }
}

// Based on the @ type, prompt:
if (atMe && !atAll) {
    atTipsStr = @"[someone@me]";
}
if (!atMe && atAll) {
    atTipsStr = @"[@all members]";
}
if (atMe && atAll) {
    atTipsStr = @"[someone@me][@all members]";
}

Setting APNs Offline Push (offlinePushInfo)

When the recipient's app is killed or when the recipient switches to the backend, the IM SDK cannot receive new messages through the normal network connection. In this scenario, the APNs service provided by Apple must be used to notify the recipient of new messages. For more information, see Offline Push (iOS).

Setting the title and voice for APNs Offline Push

When sending messages, you can use the offlinePushInfo field in the sendMessage API to set the title and voice for APNs offline push.

// Create and send an image message to groupA, and customize the title and voice for offline push.
NSString *imagePath = [[NSBundle mainBundle] pathForResource:@"test" ofType:@"png"];
// Create an image message.
V2TIMMessage *msg = [[V2TIMManager sharedInstance] createImageMessage:imagePath];
V2TIMOfflinePushInfo *pushInfo = [[V2TIMOfflinePushInfo alloc] init];
// Customize the title and voice for offline push. `01.caf` is a sample file, which must be linked to the Xcode project. Here, you only need to enter the file name with the extension.
pushInfo.title = @"Customize the title displayed";
pushInfo.iOSSound = @"01.caf";
[[V2TIMManager sharedInstance] sendMessage:msg receiver:nil groupID:@"groupA" priority:V2TIM_PRIORITY_DEFAULT 
onlineUserOnly:NO offlinePushInfo:pushInfo progress:^(uint32_t progress) {
} succ:^{
    // The message is sent successfully.
} fail:^(int code, NSString *msg) {
    // The message failed to be sent.
}];

Clicking a pushed message to go to the corresponding chat window

To implement this feature, the sender needs to set ext, which is the extended field of the offline push object offlinePushInfo, when sending a message. When the recipient opens the app, the recipient can obtain ext through the didReceiveRemoteNotification system callback, and then go to the corresponding chat window based on the content of ext.

The following example assumes that Denny sends a message to Vinson.

• Sender: Denny needs to set ext before sending a message.

  // Denny sets `offlinePushInfo` and specifies `ext` before sending a message.
  V2TIMMessage *msg = [[V2TIMManager sharedInstance] createTextMessage:@"Text message"];
  V2TIMOfflinePushInfo *info = [[V2TIMOfflinePushInfo alloc] init];
  info.ext = @"jump to denny";
  [[V2TIMManager sharedInstance] sendMessage:msg receiver:@"vinson" groupID:nil priority:V2TIM_PRIORITY_DEFAULT
  onlineUserOnly:NO offlinePushInfo:info progress:^(uint32_t progress) {
  } succ:^{
  } fail:^(int code, NSString *msg) {
  }];

Recipient: although Vinson's app is not online, it can still receive an APNs offline message notification. When Vinson clicks this notification, the app is started.

// Vinson receives the following callback after starting the app.
- (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo 
fetchCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler {
    // Parse `desc`, which is the extended field for online push.
    if ([userInfo[@"ext"] isEqualToString:@"jump to denny"]) {
        // Go to the chat window with Denny.
    }
}

Setting onlineUserOnly so that Messages Can Be Received Only Online

In some scenarios, you may wish that sent messages can only be received by online users, that is, a recipient is not aware of the message when the recipient is offline. For this purpose, you can set
onlineUserOnly to YES when calling sendMessage. After the setting, the sent messages differ from common messages in the following ways:

• Messages cannot be stored offline. That is, the recipient cannot receive messages unless he/she is online.
• Messages do not support multi-device roaming. That is, if the recipient has received messages on one terminal, these messages cannot be received on any other terminal no matter whether these messages are read or not.
• Messages cannot be stored locally. That is, these messages cannot be retrieved from the local history messages in the cloud.

Typical example: displaying "The other party is typing...
In the one-to-one chat scenario, you can call sendMessage to send the "I am typing..." message. When the recipient receives this message, "The other party is typing..." is displayed on the UI. The sample code is as follows:

// Sending the "I am typing..." message to userA.
NSString *customStr = @"{\"command\": \"textInput\"}";
NSData *customData = [customStr dataUsingEncoding:NSUTF8StringEncoding];
V2TIMMessage *msg = [[V2TIMManager sharedInstance] createCustomMessage:customData];
[[V2TIMManager sharedInstance] sendMessage:msg receiver:@"userA" groupID:nil
priority:V2TIM_PRIORITY_DEFAULT onlineUserOnly:YES offlinePushInfo:nil progress:^(uint32_t progress) {
} succ:^{
    // The message is sent successfully.
} fail:^(int code, NSString *msg) {
    // The message failed to be sent.
}];

Recalling Messages

The sender can call the revokeMessage API to recall a successfully sent message. By default, the sender can recall a message that is sent within 2 minutes. You can change the time limit for message recall. For detailed operations, see Message recall settings。
Message recall requires cooperation of the UI code at the recipient side. When the sender recalls a message, the recipient will receive a message recall notification, onRecvMessageRevoked. This notification contains the msgID of the recalled message. Based on this msgID, you can identify the message that has been recalled and change the corresponding message bubble to the "Message recalled" state on the UI.

The sender recalls a message

[[V2TIMManager sharedInstance] revokeMessage:msg succ:^{
     // The message is successfully recalled.
} fail:^(int code, NSString *msg) {
     // The message fails to be recalled.
}];

The recipient learns that the message is recalled

1. Call addAdvancedMsgListener to set the advanced message listener.
2. Call onRecvMessageRevoked to receive the message recall notification.

- (void)onRecvMessageRevoked:(NSString *)msgID {
      // `msgList` is the message list on the current chat window.
      for(V2TIMMessage *msg in msgList){
         if ([msg.msgID isEqualToString:msgID]) {
             // `msg` is the recalled message. You need to change the corresponding message bubble state on the UI.
         }
     }
 }

Adding Read Receipts for Messages

In the one-to-one chat scenario, when the recipient calls the markC2CMessageAsRead API to mark an incoming message as read, the message sender will receive a read receipt, indicating that the recipient has read his/her message.

Note：

Currently, only one-to-one chats support the read receipt feature, and group chats do not support this feature. Although the markGroupMessageAsRead API is also available in group chats, the group message senders currently cannot receive any read receipts.

The recipient marks messages as read

// Mark messages coming from Haven as read.
[[V2TIMManager sharedInstance] markC2CMessageAsRead:@"haven" succ:^{
} fail:^(int code, NSString *msg) {
}];

The sender learns that the messages are read

The event notification of the message receipt is located in the advanced message listener V2TIMAdvancedMsgListener. To learn that a message is already read, the sender must call addAdvancedMsgListener to set the listener. Then, the sender can receive a read receipt from the recipient through the onRecvC2CReadReceipt callback.

- (void)onRecvC2CReadReceipt:(NSArray<V2TIMMessageReceipt *> *)receiptList {
      // The sender may receive multiple read receipts at a time. Therefore, the array callback mode is used here.
      for (V2TIMMessageReceipt *receipt in receiptList) {
          // Message receiver
          NSString * receiver = receipt.userID;
          // Time of the read receipt. A message is considered as read if the timestamp in the chat window is not later than `timestamp` here.
          time_t timestamp = receipt.timestamp;
      }
}
@end

Viewing History Messages

You can call getC2CHistoryMessageList to obtain history messages of one-to-one chats, or call getGroupHistoryMessageList to obtain history messages of group chats. If the network connection of the current device is normal, the IM SDK pulls history messages from the server by default. If the network connection is unavailable, the IM SDK directly reads history messages from the local database.

Pulling history messages by page

The IM SDK supports the feature of pulling history messages by page. The number of messages pulled per page cannot be too large; otherwise, the pulling speed is affected. We recommend that you pull 20 messages per page.
The following example assumes that history messages of groupA are pulled by page, and the number of messages per page is 20. The sample code is as follows:

// The value `nil` of `lastMsg` is passed in for the first pulling, indicating that starting from the latest message, a total of 20 messages are pulled.
[[V2TIMManager sharedInstance] getGroupHistoryMessageList:@"groupA" count:20 
lastMsg:nil succ:^(NSArray<V2TIMMessage *> *msgs) {
    // Messages that are pulled by page are listed from new to old by default.
    if (msgs.count > 0) {
        // Obtain the start message for the next pulling by page.
        V2TIMMessage *lastMsg = msgs.lastObject;
        // Pull the remaining 20 messages.
        [[V2TIMManager sharedInstance] getGroupHistoryMessageList:@"groupA" count:20 
                lastMsg:lastMsg succ:^(NSArray<V2TIMMessage *> *msgs) {
            // Message pulling is completed.
        } fail:^(int code, NSString *msg) {
            // Messages fail to be pulled.
        }];
    }
} fail:^(int code, NSString *msg) {
    // Messages fail to be pulled.
}];

In actual scenarios, pulling by page is often triggered by your swipe operation. Each time when you swipe on the message list, pulling by page is triggered once. However, the principle is similar to the preceding sample code. In either case, lastMsg specifies the start message for pulling, and count specifies the number of messages pulled each time.

Precautions

• The storage period of history messages is as follows:
  • Trial edition: free storage for 7 days, no extension supported.
  • Pro edition: free storage for 7 days, extension supported.
  • Flagship edition: free storage for 30 days, extension supported.
  It is a value-added service to extend the storage period of history messages. You can log in to the IM console to modify the relevant configuration. For more information about billing, see Value-added Service Pricing.
• Only the meeting group (corresponding to the ChatRoom of the earlier version) supports pulling history messages of members before members join the group.
• Messages in the AVChatRoom do not support local storage and multi-device roaming. Therefore, the getGroupHistoryMessageList API does not take effect on an AVChatRoom.

Deleting Messages

You can call the deleteMessages API to delete historical messages. After deletion, historical messages cannot be recovered.

Setting Message Permissions

Allowing message sending and receiving only among friends

By default, the IM SDK does not prevent message sending and receiving among strangers. If you wish that C2C messages can be sent or received only among friends, you can log in to the IM console, choose Feature Configuration > Login and Messages > Relationship Check, and enable Check Relationship for One-to-One Messages. After this feature is enabled, you can send messages only to friends. When you try to send messages to strangers, the IM SDK returns the 20009 error code.

Blocking messages from a specified user

If you want to block messages from a specified user, call the addToBlackList API to add this user to the blocklist.
When a user is added to the blocklist, the user does not know that he/she is in the blocklist by default. That is, after this user sends a message, the prompt still indicates that the message is sent successfully, but in fact the recipient will not receive the message. If you want a user in the blocklist to know that his/her message fails to be sent, you can log in to the IM console, choose Feature Configuration > Login and Messages > Blocklist Check, and disable Show "Sent successfully" After Sending Messages. After this feature is disabled, the IM SDK will return the 20007 error code when a user in the blocklist sends a message.

Blocking messages from a specified group

To block messages from a specified group, you can call the setReceiveMessageOpt API to set the group message receiving option to the V2TIM_GROUP_NOT_RECEIVE_MESSAGE state.

Filtering Sensitive Words

Text messages sent by the IM SDK are filtered by IM for sensitive words. If a sent text message contains sensitive words, the IM SDK will return the 80001 error code.

FAQs

1. Why am I receiving duplicate messages?

• Check whether addSimpleMsgListener is used together with addAdvancedMsgListener. If yes, when text or custom messages are received, both listeners trigger callback, and consequently duplicate messages are received.
• Check whether the same listener object is added repeatedly. If a listener object is no longer needed, call the corresponding removeSimpleMsgListener or removeAdvancedMsgListener API to remove this listener.

2. Why do the read receipts become invalid after the app is uninstalled and then reinstalled?

In the one-to-one chat scenario, if the recipient calls markC2CMessageAsRead to mark a message as read, the read receipt received by the sender contains timestamp. Based on timestamp, the SDK determines whether the other party reads the message. Currently, timestamp is stored locally, and will be lost when the app is reinstalled.

3. How is a message containing multiple Elem objects parsed?

To reduce the message complexity, the SDK API 2.0 no longer supports creation of a message containing multiple Elem objects. If you receive a message containing multiple Elem objects from the API of an earlier version, perform the steps below:

1. Parse the first Elem object as usual.
2. Use the nextElem method of the first Elem object to obtain the next Elem object. If the next Elem object exists, the Elem object instance is returned. Otherwise, nil is returned.

- (void)onRecvNewMessage:(V2TIMMessage *)msg {
    // View the first `Elem` object.
    if (msg.elemType == V2TIM_ELEM_TYPE_TEXT) {
        V2TIMTextElem *textElem = msg.textElem;
        NSString *text = textElem.text;
        NSLog(@"Text information: %@", text);
        // Check whether `textElem` is followed by more `Elem` objects.
        V2TIMElem *elem = textElem.nextElem;
        while (elem != nil) {
            // Identify the Elem type.
            if ([elem isKindOfClass:[V2TIMCustomElem class]]) {
                V2TIMCustomElem *customElem = (V2TIMCustomElem *)elem;
                NSData *customData = customElem.data;
                NSLog(@"Custom information: %@",customData);
            }
            // Continue to check whether current `Elem` is followed by more `Elem` objects.
            elem = elem.nextElem;
        }
        // If `elem` is `nil`, all `Elem` objects have been parsed.
    }
}

4. How are different types of messages parsed?

It is complex to parse a message. We provide the sample code for parsing different types of messages. You can copy the code to your project, and perform secondary development based on your actual needs.