• UIKit
  • SDK
  • 서버 API
React Native/
  • Run Demo
  • SDK 통합
  • 초기화
  • 로그인 및 로그아웃
  • 메시지
    • 메시지 개요
    • 메시지 보내기
    • 메시지 받기
    • 과거 메시지
    • 메시지 전달
    • 메시지 수정
    • 메시지 삽입
    • 메시지 삭제
    • 메시지 비우기
    • 메시지 철회
    • 온라인 메시지
    • 읽음 확인
    • 메시지 조회
    • 그룹 @ 메시지
    • 지향적 그룹 메시지
    • 알림 음소거
    • 메시지 확장
  • 그룹
    • 개요
    • 그룹 관리
    • 그룹 정보
    • 그룹 멤버 관리
    • 그룹 멤버 정보
    • 그룹 속성 사용자 정의
    • 커뮤니티 관리
  • 사용자
    • 사용자 정보
    • 친구 관리
    • 친구 목록
    • 블록리스트
  • 오프라인 푸시
    • 오프라인 푸시
  • 국부 검색
    • 메시지 검색
    • 친구 검색
    • 그룹 검색
    • 그룹 멤버 검색
  • 시그널링
    • 시그널링 관리
  • Changelog
  • Guideline for Beginners
  • 콘솔 안내
    • 애플리케이션 생성 및 업그레이드
    • 기본 구성
    • 기능 구성
    • 계정 관리
    • 그룹 관리
    • 콜백 구성
  • 제품 소개
    • 메시지 관리
      • 1대1 메시지
      • 메시지 저장
      • 오프라인 푸시
      • 그룹 메시지
      • 메시지 포맷
    • 계정 시스템
      • 로그인 인증
      • 온라인 상태 관리
    • 그룹 관련
      • 그룹 시스템
      • 그룹 관리
    • 사용자 정보 및 관계망
      • 정보 관리
      • 관계망 관리
  • 구매 가이드
    • 과금 개요
    • 가격
  • 에러코드
이 페이지는 현재 영어로만 제공되며 한국어 버전은 곧 제공될 예정입니다. 기다려 주셔서 감사드립니다.


Feature Description

You must initialize the IM SDK before using its features. In most scenarios, you need to initialize the IM SDK only once during the application lifecycle.


You can initialize the SDK in the following steps:
1. Prepare an SDKAppID.
2. Set the LogLevelEnum.
3. Set the SDK event listener.
4. Call initSDK to initialize the SDK.
The detailed steps are as follows.

Preparing an SDKAppID

To perform the initialization, you must have a correct SDKAppID. The SDKAppID uniquely identifies a Tencent Cloud IM account. We recommend you apply for a new SDKAppID for each application. Messages are naturally isolated and cannot communicate between different SDKAppID values. In the IM console, you can view all your SDKAppID values, and you can click Create Application to create an SDKAppID.

Setting the LogLevelEnum

Before initializing the SDK, you need to initialize the LogLevelEnum object, which is used to set the SDK log level.

Setting the log level

The IM SDK supports the following log levels:
Log Level
Log Output
No log is output.
Logs at the DEBUG, INFO, WARNING, and ERROR levels are output (default log levels).
Logs at the INFO, WARNING, and ERROR levels are output.
Logs at the WARNING and ERROR levels are output.
Logs at the ERROR level are output.
SDK log storage rules are as follows:
Local IM SDK logs are retained for seven days by default, after which the logs will be automatically cleared during the SDK initialization.
By default, IM SDK logs on Android are stored in the /sdcard/tencent/imsdklogs/application package name directory for versions earlier than v4.8.50 and in the /sdcard/Android/data/package name/files/log/tencent/imsdk directory for v4.8.50 or later.
Starting from v4.7.1, the xlog module is used to output IM SDK logs, which are compressed by default and must be decompressed by using the Python script.
To obtain the script for decompression, click Decode Log 27 (for Python 2.7) or Decode Log 30 (for Python 3.0).
In the Windows or macOS console, you can decompress log files by running the following command. After decompression, the file names end with "xlog.log", and you can use the text editor to open these files.
python decode_mars_nocrypt_log_file.py imsdk_yyyyMMdd.xlog

Setting the SDK event listener

After the initialization, the SDK will report such events as connection status and login ticket expiration through V2TimSDKListener. We recommend you pass in V2TimSDKListener (Details) when calling initSDK to add the SDK event listener and perform logic processing in the callback.
V2TimSDKListener callbacks are as follows:
Event Callback
Event Description
Recommended Operation
The SDK is connecting to the CVM instance.
Display the "connecting" status on the UI.
The SDK is successfully connected to the CVM instance.
The SDK failed to connect to the CVM instance.
Notify the user that the network connection is currently unavailable.
The current user is kicked offline.
Display the "You have already logged in to the current account on another device. Are you sure you want to log in again?" message on the UI.
The login ticket expired.
Log in with a new UserSig.
The current user's profile is updated.
Update the profile photo and nickname on the UI.
If you receive the onUserSigExpired callback, the UserSig that you use for login has expired. In this case, you need to use a new UserSig to log in again. If you continue to use the expired UserSig, the IM SDK will be in an infinite login loop.

Calling the initialization API

After performing the above steps, you can call initSDK (Details) to initialize the SDK.
Below is the sample code:
import { TencentImSDKPlugin, LogLevelEnum } from 'react-native-tim-js';

// 1. Get the `SDKAppID` from the IM console.
const sdkAppID = 0;
// 2. Add the `V2TimSDKListener` event listener.
const sdkListener = {
onConnectFailed: (code, error) {},
onConnectSuccess: () {},
onConnecting: () {},
onKickedOffline: () {},
onSelfInfoUpdated: (V2TimUserFullInfo info) {},
onUserSigExpired: () {},

// 3. Perform the initialization and register the event.
sdkAppID: sdkAppID,
loglevel: LogLevelEnum.V2TIM_LOG_ALL,
listener: sdkListener,


Generally, if your application's lifecycle is the same as the IM SDK's lifecycle, you don't need to uninitialize the IM SDK before exiting the application. However, you can uninitialize the IM SDK in special cases, for example, only after you enter a specific UI and no longer use it after exiting the UI.
You can perform the uninitialization by calling the uninitialization API unInitSDK (Details).
Below is the sample code:
import { TencentImSDKPlugin } from "react-native-tim-js";

// Uninitialize the SDK


1. What should I do if error code 6013 is returned along with the description "not initialized" when I call the login or another API?

You must initialize the IM SDK before using the login, message, group, conversation, relationship chain and profile, and signaling features.