Class AdvanceMessageManage

If the user is in the login status, IM SDK will send new messages through the callback set via this API.   Please note that the sent messages may be unread or read messages. They can also be messages that have not been displayed locally, such as when messages are read on another client and pulling recent contacts obtains the last messages of conversations. If not stored locally, these messages are sent by this method. After the user logs in, IM SDK pulls offline messages. To avoid missing message notifications, you need to register new message notifications before login.

The cb parameter must be the same as that sent by TIMAddRecvNewMsgCallback. Otherwise, the callback cannot be deleted.

Set the callback for the message element upload progress. When a message contains image, voice, file, and video elements, IM SDK will upload these files and trigger the callback set via this API. Users can learn the upload progress based on the callback.

When the sender sends a message, the recipient calls the TIMMsgReportReaded API to report that the message has been read. IM SDK at the sender's end will send the receipt using the callback set via this API.

If the sender calls the TIMMsgRevoke API to recall a message that it sends to the recipient, IM SDK at the recipient's end will send a message recall notification using the callback set via this API.

When the message you send is modified on the server, ImSDK will notify you through this callback You can intercept all instant messaging IM messages on your own server Callback Before Sending a One-to-One Message After the setting is successful, the instant messaging IM server will synchronously notify your business server of every message sent by your users. Your business server can modify the message (such as filtering sensitive words). If your server modifies the message, ImSDK will notify you through this callback.

This API is used to save a message. Generally, you can construct a message JSON string and save it to a specified conversation.

This API deletes both local and roaming messages. Pay attention to the following:

We recommend that you store the JSON string of the message array and then call this API to delete the messages, avoiding repeated construction of the message array. Up to 30 messages can be deleted at a time. This API can be called only once per second. If the account has pulled these messages from other devices, the messages will still be stored on those devices after this API is called to delete them. That is, the operation of message deletion cannot be synchronized across multiple devices.

Note:

This interface is used to send new messages, single chat messages and group messages. When sending a single chat message, conv_id is the other party's UserID, and conv_type is Conv_C2C When sending a group chat message, conv_id is the group ID, and conv_type is Conv_Group . When sending messages, kTIMElem_GroupTips and kTIMElem_GroupReport cannot be sent. They are sent by the background to update (notify) group information. Elements within a message can be sent Text message elements, please refer to TextElem Emoji message element, please refer to FaceElem Position message element, please refer to LocationElem Picture message element, please refer to ImageElem Sound message element, please refer to SoundElem custom message element, please refer to CustomElem File message element, please refer to FileElem Video message element, please refer to VideoElem

Compared with TIMMsgSendMessage, this API has a different return value and an additional callback parameter.

This API is used to import messages in batches. You can construct messages for importing. Alternatively, you can store the JSON string of the message array to be imported and call this API to import the JSON string, avoiding repeated construction of the message array.

This API is used to accurately locate a message of the specified conversation by using the message locator. It is often used to search for a specified message upon message recall. One message locator corresponds to one message.

This API is used to recall a message. The stored message JSON content or the message JSON content located by the message locator is used to avoid repeated construction of the message JSON content.

You can obtain the group message receiving option from the group profile GroupBaseInfo.

This API supports batch setting. You can use the userIDList field to specify up to 30 users for batch setting. This API can be called for up to 5 times per second.