TIMSDK is a router first, and its newest release tag is from April 2024

The newest release tag is from 2024, the branch moved in 2026

The three newest releases all carry the same shape of name: [email protected], [email protected] and [email protected], published on 2024-04-22, 2024-04-11 and 2024-03-04. Each title also carries an internal build date that sits one to three days before the publish date, written as Latest Enhanced Version 7.9.5680 @2024.04.19.

The branch did not stop there. The last push to master is dated 2026-09-21, roughly two and a half years after the newest tag. So the repository gives two different answers to the question of what the current code is, and they disagree by a wide margin. Anyone who pins a release gets 2024 code; anyone who clones master gets 2026 code, with no statement in the README about which one is meant for production.

Two details make the tags awkward to use as version references. The word Latest is written into the release title itself, so it was already out of date once 7.9.5680 was superseded, and the native@ prefix says nothing about the Web or Flutter packages, which are distributed through npm and pub.dev rather than as tags.

A hub repository where only Mac and Windows still live

The README calls this the central hub repository for Tencent Chat SDK, and its main job is routing. Two tables sit under Get Started. The first is UIKit by platform: Android View, Android Compose, iOS UIKit, iOS SwiftUI, Web React, Web Vue, Flutter and React Native, each pointing at its own repository and its own integration guide on trtc.io. The second covers the Core SDK for Android, iOS, Mac, Windows, Flutter, React Native and Web (JS).

Only two entries in either table point back into this repository. Mac resolves to a path on master inside TIMSDK itself, with its own README_CHAT.md beside it, and Windows resolves to the Windows/IMSDK directory on the same branch. Everything else is served from elsewhere: the Android and iOS Core SDK live in directories called ChatSDK inside the chat-uikit-android and chat-uikit-ios repositories.

The two tables therefore mix branch conventions. Mac and Windows read tree/master or blob/master, while the Android and iOS Core SDK links read tree/main. Neither is broken, but the path you copy is not a reliable signal of which convention a platform follows.

React Native and Web share one npm package

The Core SDK table mixes three ways of obtaining the same kind of artifact. Android and iOS are subdirectories inside other repositories, Mac and Windows are subdirectories inside this one, Flutter is a package on pub.dev named tencent_cloud_chat_sdk, and React Native and Web are both the same npm package, @tencentcloud/chat.

That overlap is the part worth pausing on. React Native and Web (JS) name an identical package, so an app in React Native and an app in the browser take the same dependency and differ only in which integration guide you follow, one at trtc.io/document/48865 and the other at 34309. Flutter is the single platform distributed through a language package registry rather than a git URL.

The UIKit side uses a third pattern, with all eight entries being git repositories, including one React Native entry that is a demo rather than a library, chat-demo-react-native. Neither table pins a version or shows an install command, so which build a platform resolves to is decided by the registry or by the head of another repository, not by anything written here.

Six platform directories in the tree, and no row in either table

The root of the repository holds more platforms than either table mentions. Alongside Android, iOS, Web, Flutter, ReactNative, Mac and Windows there are Electron, HarmonyOS, MiniProgram, UE5, Unity and uni-app, thirteen platform directories in all.

None of those six appears in the UIKit table or the Core SDK table. The repository description does name uni-app and HarmonyOS among the supported platforms, and then adds and more. So a directory in the tree and a documented integration path are two different things here: the description counts a platform as supported because code for it is present, while the tables only route the eight UIKit and seven Core SDK combinations that have a repository and a guide behind them.

Two root files carry the same split. README_ZH.md is the Simplified Chinese version of the same document, and the version history is divided between update_log_EN.md and a file named in Chinese, so the English changelog and the Chinese one do not share a filename convention.

For anyone integrating, that means choosing a platform from the directory listing lands you on a folder with no guide in this repository, while choosing from the tables lands you in a different repository entirely.

No license file sits at the root

There is no license file at the root of this repository. The tree holds .github/, .gitignore, thirteen platform directories, two README files, an English update log and a Chinese version history, and nothing that names a license. The metadata attached to the repository carries no license value either.

That is an unusual position for a commercial SDK whose own description leads with a free plan of 1,000 monthly active users, no concurrency limits, push notifications included and free forever. A free allowance describes what you can do, not what you are permitted to do with the code. A team shipping chat inside a closed source product needs a written grant, and there is none in the files here. The README's own route for that kind of question is the contact block at the bottom: a Stack Overflow tag named trtc.io, a Telegram group, a WhatsApp chat and GitHub issues.

None of those four is a license text. If the licensing terms matter to your decision, the product home page and the console are where to resolve them, not this repository.

The free plan is one sentence and a link

The pricing story is a single sentence: Tencent Chat SDK offers a free plan of 1,000 MAU per month, no concurrency limits, push notifications included, free forever, with a link to trtc.io/free-chat-api. The rest of the commercial picture lives off the repository. The product home page carries an overview, pricing and enterprise features, and the console is where applications are managed and usage monitored.

So the number a developer meets first is a headline, and the terms behind it, including what happens above 1,000 monthly active users and what the enterprise features cost, are documented somewhere this repository does not mirror.

The claims in the About section are of the same order. The SDK is described as powering billions of messages daily across Tencent's ecosystem, and the UIKit as shipping a complete chat experience in under ten minutes. Both are the vendor's own figures, offered without a method, a benchmark or a date, and the Core Capabilities section repeats the ten-minute claim as its first bullet. The console and the live demo are the two places in this document where you can check either claim against the product rather than take it on trust.

A million member communities, threads, reactions and red packets

The feature list is where the concrete numbers sit, and there are few of them. Communities are supported up to 1,000,000 members with topic-based sub-channels. Messages cover text, images, audio and video. Message status means real-time read receipts, online and offline status and typing indicators. Conversation management exposes unread, recent, pinned and deleted chats.

The four use cases are more specific about what they model. Official Channel is a WhatsApp Channel-style broadcast and subscription for brand engagement. Discord-style Community means servers, channels, threads and reactions. AI Chatbot means LLM-powered bots for customer service and companionship. Red Packet means sending red packets in one-to-one and group chats, built on custom messages and a payment integration, which is the only entry in the whole document that assumes you already have a payments relationship to plug into.

Three more capabilities sit under advanced features: cloud-based message search, real-time text translation and message merging. The Quick Links block points at a REST API reference for server-side user management and messaging, a browser demo, and a Chat SDK V2 API upgrade guide hosted on a separate document site. That last link sits oddly next to a release history that stopped in 2024, so it is the document to read before writing integration code.

Editorial conclusion

Tencent's SDK is a routing table first and a codebase second. It fits a team building a chat feature on one of the platforms the two tables actually cover, willing to write its own permission prompts and account model, and able to accept a dependency whose release history stops in April 2024 while its branch keeps moving. Check three things before a product depends on it. Get the license in writing, because no license file exists in this repository at all. Confirm the integration path for your platform, since six of the thirteen platform directories in the tree have no row in either table. And confirm what happens above 1,000 monthly active users with the vendor, because the free allowance is stated as a headline with the terms one click away.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. Releases
5. TencentCloud/TIMSDK on GitHub