As a core component of the IM SDK, TIMManager works for the initialization, login, conversation creation, and push management of the IM SDK.
- Initialization: is the prerequisite for using the IM SDK. You need to call the init API before calling other APIs.
- Login: you need to configure SDKAppID, UserID, and UserSig before using IM.
- Conversation: each time you start a conversation, you open a conversation window. A conversation can be a C2C chat or a group chat.
- Push: you can configure and manage features related to offline push, including tokens and feature enabling and disabling.
Conversation management APIs
APIs for configuring offline push
||Configures the client token and the certificate busiID.
||Initializes the offline push configuration. Use this API after you have logged in to ensure that the configuration takes effect.
||Obtains the offline push configuration. Use this API after you have logged in.
||Configures the message notification listener that works when the app is running at the backend. (This API has been deprecated.)
||Reports that the app is running at the backend.
||Reports that the app is running at the frontend.
APIs for querying local conversations and messages without login
||Loads the local storage without login.
Each time you start a conversation, you open a conversation window. A conversation can be a C2C chat or a group chat.
All API functions provided by TIMConversation are related to message operations, including sending messages, obtaining the message history, setting read receipts, recalling messages, and deleting messages.
APIs for sending messages