Initialization

V2TIMManager is a core class and also an entry class of the IM SDK. It implements features including IM SDK initialization and login, message sending and receiving, group creation, and group quitting. To complete initialization, call the initSDK API.

// 1. Obtain the SDKAppID of the app from the IM console. For more information, see SDKAppID.
// 2. Initialize the config object.
V2TIMSDKConfig config = new V2TIMSDKConfig();
// 3. Specify the log output level. For more information, see SDKConfig.
config.setLogLevel(V2TIMSDKConfig.V2TIM_LOG_INFO);
// 4. Initialize the SDK and set the listening object of V2TIMSDKListener.
// After you call initSDK, the SDK automatically connects to the network. The network connection status can be monitored in the V2TIMSDKListener callback.
V2TIMManager.getInstance().initSDK(context, sdkAppID, sdkConfig, new V2TIMSDKListener() {
    // 5. Monitor the V2TIMSDKListener callback.
    @Override
    public void onConnecting() {
        // The SDK is connecting to the Tencent CVM instance.
    }
    @Override
    public void onConnectSuccess() {
        // The SDK has successfully connected to the Tencent CVM instance.
    }
    @Override
    public void onConnectFailed(int code, String error) {
        // The SDK failed to connect to the Tencent CVM instance.
    }
});

The initialization API, initSDK (SDKAppID, SDKConfig, listener), contains three required parameters: SDKAppID, Config, and listener.

SDKAppID

SDKAppID indicates the app ID. It is a unique ID that the IM service uses to distinguish customer accounts. We recommend that you apply for a new SDKAppID for every independent app to automatically isolate messages between SDKAppIDs.
You can view all SDKAppIDs in the IM console. Alternatively, you can create an SDKAppID by clicking Add Application.

SDKConfig

The V2TIMSDKConfig parameter is used for initialization configuration of the SDK. It is often used to set the log level, that is, setLogLevel. The following table describes possible log levels.

• IM SDK logs are stored by default in /sdcard/tencenet/imsdklogs/<Application package name> for versions earlier than 4.8.50, or in /sdcard/Android/data/<Application package name>/files/log/tencent/imsdk for version 4.8.50 or later.
• Starting from V4.7.1, the xlog module of the WeChat team is used to output IM SDK logs. The xlogs are compressed by default and must be decompressed by using a Python script.
  • To obtain the decompression script, click Decode Log 27 if you are using Python 2.7, or click Decode Log 30 if you are using Python 3.0.
  • In the Windows or Mac console, you can run the following command to decompress the log files. The decompressed files are suffixed with "xlog.log" and can be directly opened in a text editor.

    python decode_mars_nocrypt_log_file.py imsdk_yyyyMMdd.xlog

Listener

V2TIMSDKListener is used to monitor the network status and user information changes.

If the onUserSigExpired callback is received, it indicates that the UserSig used for login has expired. In this case, you need to update the UserSig and then log in again. If you continue to use the expired UserSig, the SDK falls into an endless login loop.

Login

You can call the login(userID, userSig) function of V2TIMManager to log in to the SDK. The features of the IM SDK are available to you only after you successfully log in to the SDK.

• UserID: enter only letters (a-z and A-Z), digits (0-9), underscores, and hyphens. Its length cannot exceed 32 bytes.
• UserSig: indicates the login ticket of the IM SDK. It is calculated by your business server to ensure security. For more information on the calculation method, see Generating UserSig.

Login scenarios

You need to call the login function in the following scenarios:

• When you need to use features of the IM SDK for the first time after the app is started.
• When the IM SDK triggers an onUserSigExpired callback. That is, when the UserSig expires, you need to use the new UserSig for login.
• When the IM SDK triggers an onKickOffline callback. That is, when the current user is forced offline, the message stating "You have already logged in to the SDK on another device using the current account. Are you sure you want to log in again?" can be displayed on the UI. In this case, you can select "Yes" to log in again.

You do not need to call the login function in the following scenarios:

• When your network is disconnected and then reconnected, you do not need to call the login function as the SDK automatically goes online.
• When a login process is running, you do not need to log in to the SDK again.

Multi-device login

You cannot use the same account to log in on two mobile phones of the same model. For example, you cannot use the same account for login on two Apple mobile phones. However, one Android mobile phone and one Apple mobile phone will be considered as two different devices, and you can use the same account to log in on these two devices. For more information on configurations related to multi-device login, see Login Settings.

Logout

To log out of the SDK, call the logout function.