@tencent-rtc/mcp 1.6.7 → 1.7.0

package/resource/knowledge/push/integration/flutter.md

@@ -13,8 +13,6 @@ flutter pub add tencent_cloud_chat_push
 
 Please upload the iOS APNs push certificate you obtained in the manufacturer configuration step to the Chat console.
 
-The Chat console will allocate a Certificate ID for you, see the image below:
-
 To register for push notifications, you need to pass in this Certificate ID (apnsCertificateID):
 ``` java
 TencentCloudChatPush().registerPush(apnsCertificateID: Your configured Certificate ID);
@@ -24,10 +22,6 @@ TencentCloudChatPush().registerPush(apnsCertificateID: Your configured Certifica
 
 After completing the console manufacturer push information, download and add the configuration file to the project. Add the downloaded timpush-configs.json file to the `android/app/src/main/assets` directory of the project. If the directory does not exist, please create it manually.
 
-|1.Choose to download the configuration file timpush-configs.json|2.Add to the project|
-|---------|---------|
-|||
-
 ### Step 3: Client Code Configuration
 
 In this step, you will need to write some native code, such as Swift, Java, XML, etc.
@@ -38,8 +32,6 @@ Please do not worry. Just follow the instructions and copy the provided code int
 
 You can edit using Xcode, or directly in Visual Studio Code or Android Studio.
 
-Open the `ios/Runner/AppDelegate.swift` file, paste the highlighted code as shown in the image below. The code is attached after the image.
-
 ``` swift
 import UIKit
 import Flutter
@@ -83,7 +75,6 @@ import tencent_cloud_chat_push
 ```
 
 > **Note:**
->
 > 1. For the iOS console, please set the certificate ID to use businessID. The offlinePushCertificateID is deprecated.
 > 2. The old field offlinePushCertificateID is still supported, but you need to add the @objc keyword.
 
@@ -110,12 +101,9 @@ public class MyApplication extends TencentCloudChatPushApplication {
 ```
 
 > **Note:**
->
 > If you have already created your own Application for other purposes, directly `extend TencentCloudChatPushApplication` and ensure that the `onCreate()` function calls `super.onCreate();`.
 >
 
-Open the `android/app/src/main/AndroidManifest.xml` file and add an `<application>` tag to specify an `android:name` parameter, pointing to the custom `Application` class you just created. As shown in the figure:
-
 ### Step 4: Client Manufacturer Configuration
 
 【iOS】
@@ -325,7 +313,6 @@ If you need to customize the parsing of received remote push notifications, you
 【Custom click redirect implementation】
 
 > **Note:**
->
 > 1. It is recommended to register the callback in the main() function at the program entry.
 > 2. For console configuration, click on 'Subsequent Actions' and configure as follows, choose **Open the specified interface within the app**, and the plugin users will by default fill in the jump parameters.
 >
@@ -398,7 +385,6 @@ Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/huawei
 China: https://api.im.qcloud.com/v3/offline_push_report/huawei
 
 > **Note:**
->
 > Huawei Push Certificate ID <= 11344, using Huawei Push v2 interface, does not support Reach and Click Receipt, please regenerate and update Certificate ID.
 >
 
@@ -425,10 +411,6 @@ China: https://api.im.qcloud.com/v3/offline_push_report/honor
 
 【Meizu】
 
-|Enable Receipt Switch|Configure Receipt Address|
-|---------|---------|
-|||
-
 Receipt Address:
 
 Singapore : https://apisgp.im.qcloud.com/v3/offline_push_report/meizu
@@ -444,7 +426,6 @@ Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/meizu
 China: https://api.im.qcloud.com/v3/offline_push_report/meizu
 
 > **Note:**
->
 > After turning on the receipt toggle, please make sure the receipt address is correctly configured. Not configuring it or configuring the wrong address will affect the push notification feature.
 >
 

package/resource/knowledge/push/integration/harmonyos.md

@@ -41,7 +41,6 @@ For detailed API instructions, see RESTful APIs - Initiate Push to All Users/Tag
 After receiving the push message and clicking the notification, the component will Webhook the click event and offline message pass-through.
 
 > **Note:**
->
 > - Register the callback timing in the oncreate() function of the application [UIAbility](https://developer.huawei.com/consumer/cn/doc/harmonyos-guides/uiability-lifecycle).
 > - Console configuration click subsequent actions with the following configuration, select **open specified in-app page**, do not modify use default values.
 >
@@ -59,6 +58,5 @@ TIMPushManager.getInstance().addPushListener(pushListener);
 Congratulations on completing the Push Plugin access. Remind you: **After trial or purchase expiry, the Push Plugin will automatically stop providing push service (including offline push for regular messages, Tag Push, etc.)**. To avoid affecting normal business operation, please [proceed to purchase](https://buy.tencentcloud.com/avc) or [renew](https://buy.tencentcloud.com/avc) in advance.
 
 > **Note:**
->
 > - Integration completed but not receiving push notifications? Please first use the [troubleshooting tool](https://cloud.tencent.com/document/product/269/100629) to check the reason. To view push metrics data, use [data statistics](https://cloud.tencent.com/document/product/269/100628) for querying.
 > - For push notification feature to all users/Tag Push, please refer to: [RESTful APIs - Initiate Push to All Users/Tag Push](https://cloud.tencent.com/document/product/269/100634).

package/resource/knowledge/push/integration/ios.md

@@ -1,5 +1,4 @@
 > **Note:**
->
 > If you need to use products like Chat, CallKit, RoomKit, LiveKit simultaneously, please refer to [Chat Quick Integration Solution](https://www.tencentcloud.com/document/product/1047/50033).
 >
 
@@ -27,7 +26,6 @@
    ```
 
 ### Step 2: Set push parameters
-1. After you upload a certificate to the Chat console, the Chat console will assign a certificate ID to you, as shown below.
 
 2. You need to implement the `- businessID` protocol method in AppDelegate to return the certificate ID.
 
@@ -168,7 +166,6 @@ If you need to customize the parsing of received remote push notifications, you
 【Custom click redirect implementation】
 
 > **Note:**
->
 > It is recommended to place the registration callback timing in the didFinishLaunchingWithOptions function of the AppDelegate.
 >
 

package/resource/knowledge/push/integration/react-native.md

@@ -24,7 +24,6 @@ yarn add @tencentcloud/react-native-push
 Copy the following code to `App.tsx` and replace `SDKAppID` and `appKey` with your application's information.
 
 > **Note:**
->
 > After successfully registering the push service with `registerPush`, you can obtain the push ID, namely RegistrationID, through `getRegistrationID`. You can push messages to the specified RegistrationID.
 >
 
@@ -74,7 +73,6 @@ if (Push) {
 ### Step 4: Configuring Vendor Push
 
 【Android】
-1. After completing the vendor push information in the console, download the `timpush-configs.json` file from the console and add it to the `MyReactNativeApp/android/app/src/main/assets` directory of the project. If this directory does not exist, please create it manually. As shown in the figure:
 
 2. Huawei, HONOR, vivo, FCM.
 
@@ -85,7 +83,6 @@ When you need to support FCM push, you must configure the  `google-services.json
 【Huawei】
 
 【HONOR】
-1. To support HONOR Push, you need to configure `appID` in the `MyReactNativeApp/android/app/build.gradle` file. As shown in the figure:
 
 ``` bash
 ......
@@ -100,15 +97,10 @@ android {
 }
 ```
 
-|Obtain HONOR appID|Configure HONOR appID|
-|---------|---------|
-|||
-
 2. Download the `mcs-services.json` file from the [Honor Developer Management Center](https://developer.honor.com/en/), and configure it in the `MyReactNativeApp/android/app` directory (**Please note! Not in the** `MyReactNativeApp/android/app/src/main/assets directory` directory).
 
 【vivo】
 
-To support vivo Push, you need to configure `appID` and `appKey` in the `MyReactNativeApp/android/app/build.gradle` file. As shown in the figure:
 ``` bash
 ......
 android {
@@ -123,14 +115,7 @@ android {
 }
 ```
 
-|Obtain vivo appID && appKey|Configure vivo appID && appKey|
-|---------|---------|
-|||
-
 【iOS】
-1. Please upload the iOS APNs Push Certificate obtained in the manufacturer configuration step to the Chat Console. The Chat Console will assign a Certificate ID to you, as shown in the figure:
-
-2. In the `MyReactNativeApp/ios/MyReactNativeApp` directory, create a new `Resources` folder and a new `timpush-configs.json` file. Edit `timpush-configs.json` and enter the certificate ID obtained from the console, as shown below:
 
 ``` javascript
 {
@@ -138,14 +123,11 @@ android {
 }
 ```
 
-3. Open the MyReactNativeApp project in XCode, right-click the project > **Add Files to "MyReactNativeApp"**, and add the `timpush-configs.json` directory to the project. As shown in the figure:
-
 ### Step 5: **Configuring Native Modules and Dependencies**
 
 【Android】
 
 > **Note:**
->
 > Please ensure the package name in `timpush-configs.json` matches the `applicationId` value in `MyReactNativeApp/android/app/build.gradle`. Inconsistency will result in offline push notifications being unavailable.
 >
 
@@ -307,7 +289,6 @@ If you need to collect data on delivery, please complete the setup as follows:
 - China: https://api.im.qcloud.com/v3/offline_push_report/huawei
 
 > **Note:**
->
 > Huawei Push Certificate ID <= 11344, using Huawei Push v2 version interface does not support reach and click receipt, please regenerate and update the certificate ID.
 >
 
@@ -333,10 +314,6 @@ If you need to collect data on delivery, please complete the setup as follows:
 
 【Meizu】
 
-|Enable Receipt Switch|Configure Receipt Address|
-|---------|---------|
-|||
-
 **Receipt Address:**
 - Singapore : https://apisgp.im.qcloud.com/v3/offline_push_report/meizu
 
@@ -351,7 +328,6 @@ If you need to collect data on delivery, please complete the setup as follows:
 - China: https://api.im.qcloud.com/v3/offline_push_report/meizu
 
 > **Note:**
->
 > After enabling the Receipt Switch, please make sure the Receipt Address is configured correctly. Failing to configure or configuring the wrong address will affect the push feature.
 >
 

package/resource/knowledge/push/integration/uni-app.md

@@ -16,7 +16,6 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
 ### Step 2. Offline push configuration
 
 > **Note:**
->
 > 1. HBuilderX 4.36 has released non-backward compatible updates. If you are using HBuilderX 4.36 or higher and need vendor push for vivo/Honor, please upgrade the push version to 1.1.0 or higher and refer to the documentation to correctly configure `manifestPlaceholders.json` and `mcs-services.json`.
 > 2. You need to configure push notifications in the `nativeResources` directory. If this folder is not yet created in the project root directory, please create a new folder named `nativeResources`.
 > 3. Ensure that the `nativeResources` directory exists in the project opened with HBuilderX and is at the same level as the `uni_modules` directory.
@@ -24,12 +23,9 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
 【Android】
 1. Create the directory `nativeResources/android/assets`.
 
-2. Configure `timpush-configs.json` (download from [Push Service > Access Settings > One-click Quick Configuration](https://console.trtc.io/chat/push-plugin-push-identifier)) to the `nativeResources/android/assets/` directory. As shown in the figure:
-
 3. Huawei, HONOR, vivo, FCM.
 
 【FCM】
-1. Configure `com.google.gms.google-services` to `uni_modules/TencentCloud-Push/utssdk/app-android/config.json`  in `project.plugins`, as shown below:
 
 ``` json
 "project": {
@@ -45,8 +41,6 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
 }
 ```
 
-2. Configure the `google-services.json` file to the `nativeResources/android/` directory (Note! Do not configure it to the `nativeResources/android/assets`  directory). As shown in the figure:
-
 【Huawei】
 
 【HONOR】
@@ -97,8 +91,6 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
 
 2. Create a `timpush-configs.json` file in `nativeResources/ios/Resources`.
 
-3. Add the certificate ID obtained from [Chat Console > Push Service > Access Settings](https://console.trtc.io/chat/push-plugin-push-identifier) to the `timpush-configs.json` file. As shown below:
-
 ``` json
 {
     "businessID":"xxx"
@@ -107,8 +99,6 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
 
 ### Step 3. Introduce and register Tencent Cloud Push Service (Push)
 
-Replace `SDKAppID` and `appKey` with the application information obtained from [Chat Console - Push Service - Access Settings page](https://console.trtc.io/chat/push-plugin-push-identifier). As shown in the figure:
-
 ``` javascript
 // Integration of TencentCloud-Push
 import * as Push from '@/uni_modules/TencentCloud-Push';
@@ -159,7 +149,7 @@ Before testing the push, please make sure to turn on notifications and the statu
 
 ## Push Result Callback
 
-After enabling the push service, the push results can be forwarded to the App backend by configuring basic callbacks. For details, see:
+After enabling the push service, the push results can be forwarded to the App backend by configuring basic callbacks.
 - [Normal push result callback](https://www.tencentcloud.com/document/product/1047/67553)
 
 - [All-member push result callback](https://www.tencentcloud.com/document/product/1047/60561)

package/resource/knowledge/push/integration/unity.md

@@ -18,8 +18,6 @@ Adjust the `Packages/manifest.json` file and add relevant dependencies:
 
 Upload the iOS APNs Push Certificate obtained from the manufacturer configuration process to the Chat console.
 
-The Chat console will allocate a certificate ID for you, as shown below:
-
 You need to create file `UnityIMPush.mm` under the directory `Assets/Plugins/iOS` (if the directory does not exist, create it manually), and implement the `- businessID` protocol method in the file to return the certificate ID. See the implementation as follows:
 ``` objectivec
 #import "TPush/TPush.h"
@@ -244,7 +242,6 @@ apply plugin: 'com.hihonor.mcs.asplugin'
 If you need to customize the parsing of received remote push, you can implement it by the following method.
 
 > **Note:**
->
 > 1. Register the callback timing in the program entry function.
 > 2. Configure the console to click subsequent actions with the following configuration, select **open specified in-app page,** do not modify and use default values.
 >
@@ -266,7 +263,6 @@ PushManager.AddPushListener(listener);
 Upon success of calling the `PushManager.RegisterPush` method, you can receive offline push notifications.
 
 > **Note:**
->
 > Note: If you have already integrated the Chat product and call this API after successful log-in, set the appKey parameter to null. Otherwise, the Chat account will be taken offline.
 >
 
@@ -299,7 +295,6 @@ Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/huawei
 China: https://api.im.qcloud.com/v3/offline_push_report/huawei
 
 > **Note:**
->
 > Note: Huawei Push certificate ID <= 11344 uses Huawei Push v2 version interface with no support for reachability and Receipt Click. Please regenerate the certificate ID.
 >
 
@@ -325,9 +320,6 @@ China: https://api.im.qcloud.com/v3/offline_push_report/honor
 | Receipt Address:<br>Singapore :https://apisgp.im.qcloud.com/v3/offline_push_report/vivo<br>Korea:<br>https://apikr.im.qcloud.com/v3/offline_push_report/vivo<br>USA: https://apiusa.im.qcloud.com/v3/offline_push_report/vivo<br>Germany: https://apiger.im.qcloud.com/v3/offline_push_report/vivo<br>Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/vivo<br>China:<br>https://api.im.qcloud.com/v3/offline_push_report/vivo |  |
 
 【Meizu】
-| Enable Receipt Switch | Configure Receipt Address |
-| --- | --- |
-|  |  |
 
 Receipt Address:
 
@@ -344,7 +336,6 @@ Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/meizu
 China: https://api.im.qcloud.com/v3/offline_push_report/meizu
 
 > **Note:**
->
 > Note: After enabling the receipt switch, please ensure the receipt address is configured correctly. Without configuring or with an incorrect address, it will impact the push notification feature.
 >
 

package/resource/knowledge/push/integration/unreal-engine.md

@@ -3,9 +3,6 @@
 ### Step 1: TIMPush Integration
 
 Download [TIMPush](https://github.com/TencentCloud/TIMSDK/tree/master/UE5/Push/pushdemo/Plugins/TIMPush) and copy to the `Plugins` directory under the project. In the Build.cs file of the main module, introduce TIMPush.
-| copy directory | Introduce plug-in |
-| --- | --- |
-|  |  |
 
 ### Step 2: Push Parameter Configuration
 
@@ -13,8 +10,6 @@ Download [TIMPush](https://github.com/TencentCloud/TIMSDK/tree/master/UE5/Push/p
 
 Upload the obtained iOS APNs Push Certificate to the IM console during the manufacturer configuration process.
 
-The IM console will allocate a certificate ID for you, as shown below:
-
 Set businessID:
 
 Open "Project Settings" in UE4 Editor, search for `Additional Plist Data`, modify the following text and copy it into the textbox. `YourBusinessID` is required, while `YourGroupID` needs to be modified when you need to count push reach and click data.
@@ -39,9 +34,6 @@ bEnableRemoteNotificationsSupport=True
 【Android】
 
 After completing the console manufacturer push information, download and add the configuration file to the project. Place the downloaded `timpush-configs.json` file under the `Source/ThirdParty/TIMPushLibrary/Android/TIMPush/Assets` directory.
-| download configuration file | copy path |
-| --- | --- |
-|  |  |
 
 ### Step 3: Client Vendor Configuration
 
@@ -99,7 +91,6 @@ According to the vivo and Honor vendor access guide, you need to add APPID and A
 Integrate the corresponding plugin and json configuration file using the vendor method.
 
 > **Note:**
->
 > Note: The following Honor adaptation requires configuration for version 7.7.5283 and above.
 >
 
@@ -163,7 +154,6 @@ Integrate the corresponding plugin and json configuration file using the vendor
 If you need custom parsing for received remote push, you can implement it by the following method.
 
 > **Note:**
->
 > 1. Register callback timing is recommended to be placed in the program entry function.
 > 2. Configure the console and click subsequent actions with the following configuration. Select **open specified in-app page**. Do not modify and use default values.
 >
@@ -290,7 +280,6 @@ Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/huawei
 China: https://api.im.qcloud.com/v3/offline_push_report/huawei
 
 > **Note:**
->
 > Note: Huawei Push certificate ID <= 11344 uses Huawei Push v2 API. Reach and Receipt Click are unsupported. Please regenerate and update the certificate ID.
 >
 
@@ -316,9 +305,6 @@ China: https://api.im.qcloud.com/v3/offline_push_report/honor
 | Receipt Address:<br>Singapore :https://apisgp.im.qcloud.com/v3/offline_push_report/vivo<br>Korea:<br>https://apikr.im.qcloud.com/v3/offline_push_report/vivo<br>USA: https://apiusa.im.qcloud.com/v3/offline_push_report/vivo<br>Germany: https://apiger.im.qcloud.com/v3/offline_push_report/vivo<br>Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/vivo<br>China:<br>https://api.im.qcloud.com/v3/offline_push_report/vivo |  |
 
 【Meizu】
-| Enable Receipt Switch | Configure Receipt Address |
-| --- | --- |
-|  |  |
 
 Receipt Address:
 
@@ -335,14 +321,13 @@ Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/meizu
 China: https://api.im.qcloud.com/v3/offline_push_report/meizu
 
 > **Note:**
->
 > Note: After enabling the receipt switch, please ensure the receipt address is configured correctly. Without configuring or with an incorrect address, it will impact the push notification feature.
 >
 
 【iOS】
 1. If you need to track push notification reach and click data, you need to change "YourGroupID" to your own App Group ID in the "project setting" (see manufacturer configuration - generate App GroupID).
 
-2. After configuring the App Group ID, you need to use Xcode to open the xcworkspace file generated by UE in the project directory, and refer to the method in Manufacturer Configuration - Generate App Group ID - Step 4 to configure your App Group ID. Then, enable the Notification Service Extension Target in `Editor - Add Target` in the Xcode project.
+2. After configuring the App Group ID, you need to use Xcode to open the xcworkspace file generated by UE in the project directory, and . Then, enable the Notification Service Extension Target in `Editor - Add Target` in the Xcode project.
 
 3. You also need to unzip the two framework compressed packages in the `Plugins-TIMPush-Source-ThirdParty-TIMPushLibrary-iOS` path of the project root directory, and add the internal .framework folder to your pushservice target in the Xcode project.
 
@@ -379,7 +364,6 @@ Other manufacturers support it with no need to configure. FCM does not currently
 Congratulations on completing the access of the push plugin. Remind you: the push plugin **will automatically stop providing push service (including regular message offline push, all users/tag push, etc.) after trial or purchase expiry**. To avoid affecting normal business operation, please advise in advance to [purchase](https://buy.cloud.tencent.com/avc)/[renew](https://console.cloud.tencent.com/account/renewal).
 
 > **Note:**
->
 > 1. Manufacturer offline channels have a [message categorization mechanism](https://cloud.tencent.com/document/product/269/100649), and different types will also have different push strategies.
 > - If the push demand belongs to IM type push and requires timely delivery, set your own app to the corresponding push type according to the vendor's rules. It will be categorized as a high-priority system message type or important message type.
 > - Conversely, offline push has quantity and frequency limits and may not reach devices in time.

package/resource/knowledge/roomkit/best-practice/common/room-ghost-member.md

@@ -0,0 +1,70 @@
+---
+title: "Why Abnormally Exited Members Still Appear in TUIRoomKit Member List and How to Clean Up（TUIRoomKit / 异常退出 / 幽灵成员 / 心跳检测 / 离线检测）"
+product: room
+frameworks: [react, vue, web, android, ios, flutter]
+scope: platform_common
+tags: [TUIRoomKit, abnormal exit, ghost member, heartbeat detection, offline detection, kick from room, kick_user_out, disconnect callback, member list, room cleanup]
+version_range: ">=2.0.0"
+---
+
+# Why Abnormally Exited Members Still Appear in TUIRoomKit Member List and How to Clean Up
+
+## 1. Key Takeaways
+
+- When a user exits abnormally (process killed, network disconnected, page closed without calling leave), the member still appears in the remote member list. This is the expected behavior of the **video conferencing SDK backend heartbeat offline detection**.
+- Current rule: the backend removes an abnormally exited user from the room approximately **5–6 minutes** after heartbeat loss. Only then do remote participants receive the leave notification and update the member list.
+- **The heartbeat interval cannot be set very short by default**: short heartbeat intervals increase the risk of false kicks during network jitter, disrupting normal meeting experience.
+- If your business requires faster ghost member cleanup: Option 1 (submit a ticket to shorten heartbeat to ~2 minutes) or Option 2 (use IM disconnect callback + `kick_user_out` to kick immediately).
+
+## 2. Field / API Reference
+
+| Field / Capability | Purpose | Notes |
+|---|---|---|
+| Heartbeat offline detection | Detects user online status | Backend checks whether user heartbeat is lost |
+| Heartbeat loss | Signal of abnormal exit | Heartbeat stops when process is killed / network disconnected / page closed without leave |
+| Ghost member | Abnormally exited user still displayed | Removed from room after ~5–6 minutes |
+| `kick_user_out` | Kick a room member | Business backend calls this to immediately clean up |
+| `disconnect` callback | Disconnection callback | IM server detects user offline |
+| Heartbeat interval adjustment | Backend configuration | Can be shortened to ~2 minutes via support ticket |
+
+## 3. Mechanism & Sequence
+
+User exits abnormally (process killed, network disconnected, page closed without leave) -> Backend detects heartbeat loss -> After ~5–6 minutes, removes user from room -> Remote participants receive leave notification and update member list.
+
+The default heartbeat interval cannot be too short to avoid false kicks caused by network jitter. If the business requires faster cleanup:
+
+- **Option 1**: Submit a support ticket to shorten the backend heartbeat detection interval to ~2 minutes.
+- **Option 2**: Business backend listens for the IM `disconnect` callback to detect offline status, then calls `kick_user_out` to immediately remove the ghost member.
+
+## 4. Standard Usage
+
+1. **Option 1 (adjust heartbeat interval)**: Submit a support ticket to have the backend heartbeat detection interval shortened to ~2 minutes.
+2. **Option 2 (server-side proactive cleanup)**:
+   - Business backend listens for the IM server `disconnect` (disconnection) callback.
+   - Upon receiving the offline signal, calls `kick_user_out` to kick the room member.
+
+## 5. Expected Results
+
+- Abnormally exited users are removed from the room after ~5–6 minutes, and remote member list updates accordingly.
+- After adjusting heartbeat to ~2 minutes via support ticket, cleanup is faster.
+- Option 2 using `disconnect` callback + `kick_user_out` immediately removes ghost members.
+- Setting heartbeat too short increases the risk of false kicks during network jitter.
+
+## 6. Common Pitfalls
+
+- Pitfall 1: Expecting abnormally exited users to disappear from the member list immediately (heartbeat detection takes ~5–6 minutes).
+- Pitfall 2: Assuming the heartbeat interval can be set arbitrarily short (network jitter causes false kicks, disrupting normal meetings).
+- Pitfall 3: Overlooking that the business side can proactively kick members (`disconnect` callback + `kick_user_out`).
+
+## 7. Problem Definition (retrieval hint)
+
+Why an abnormally exited user still appears in the remote member list in TUIRoomKit, and how to clean up ghost members faster.
+
+## 8. Alternative Queries (retrieval recall)
+
+- What to do when an abnormally exited user still shows in the member list?
+- How to clean up ghost members in TUIRoomKit?
+- How long until a disconnected user is removed from the room?
+- Can the heartbeat detection interval be shortened?
+- Abnormally exited user keeps showing in the list?
+- How to kick an offline user?

package/resource/knowledge/roomkit/best-practice/common/room-limit-and-multi.md

@@ -0,0 +1,83 @@
+---
+title: "TUIRoomKit Concurrent Room Limits and Multi-Room Support（TUIRoomKit / 并发房间 / 房间上限 / 同时进多个房间 / 单房间人数）"
+product: room
+frameworks: [react, vue, web, android, ios, flutter]
+scope: platform_common
+tags: [TUIRoomKit, concurrent rooms, room limit, joining multiple rooms, single room capacity, peak group count, TUIRoomTypeConference, useRoomState, multi-device login, mutual kick, conference, room management]
+version_range: ">=2.0.0"
+---
+
+# TUIRoomKit Concurrent Room Limits and Multi-Room Support
+
+## 1. Key Takeaways
+
+- The number of concurrent rooms has an upper limit, determined by the **TUIRoomKit (multi-party audio/video) plan version + IM capabilities**.
+- **A single client / single SDK instance cannot be in multiple conference rooms simultaneously**: for conference-type rooms, the per-device concurrent room limit is 1. Exceeding this causes the earliest joined room to be exited.
+- **The same userId on multiple devices joining the same room results in mutual kick by default** (later entry kicks earlier entry). To have multi-device access to the same meeting, configure "multi-device login" according to your plan, or assign different userIds to different devices.
+
+## 2. Field / API Reference
+
+| Field / Capability | Purpose | Notes |
+|---|---|---|
+| `TUIRoomTypeConference` | Conference-type room | Per-device concurrent room limit is 1 |
+| `useRoomState` | Room state (Atomicx no-UI path) | Singleton; a user can only be in one room at a time |
+| Room count limit | Room/group resource peak | Billed by natural month peak, not unlimited room creation |
+| Single room capacity | Max participants per meeting | Hard limit by plan (20/50/200/300) |
+| Multi-device login | Same userId on multiple devices | Only supported in higher-tier plans |
+
+## 3. Mechanism & Sequence
+
+### Concurrent Room Limit
+
+After activating a TUIRoomKit (multi-party audio/video) plan, the number of concurrent meetings is constrained by **room count limit + single room capacity**:
+
+| Capability Dimension | Trial | Basic Interactive | Advanced Interactive | Ultra-Large Room Interactive |
+|---|---|---|---|---|
+| **Room count limit** (billing metric) | Follows IM version | 100,000/month | 100,000/month | 100,000/month |
+| **Single room participant capacity** | 20 | 50 | 200 | 300 (submit ticket for expansion) |
+
+- Single room capacity is the hard upper limit on "max participants per meeting."
+- Room count limit (peak group count) is the IM-side group/room resource peak included in the plan (billed by natural month peak), not "unlimited rooms at any moment."
+- The actual number of simultaneous meetings also depends on IM plan, TRTC resources, and business architecture. Ultra-large rooms have an expansion channel.
+- Multi-device login to meetings / same-platform multi-device login requires a higher-tier plan.
+
+### Same User Joining Multiple Rooms
+
+When a single client / single SDK instance calls `joinRoom` to enter a new room while already in a conference-type room, the earliest joined room is exited (per-device concurrent room limit is 1).
+
+## 4. Standard Usage
+
+When evaluating concurrent room requirements, follow these steps:
+
+1. Confirm your TUIRoomKit plan version and check the room count limit and single room capacity in the [Features & Billing Documentation](https://cloud.tencent.com/document/product/269/104946).
+2. Evaluate whether the per-meeting participant count exceeds the plan limit; submit a ticket for ultra-large room expansion.
+3. When the business needs to host multiple meetings simultaneously, evaluate whether the room count limit (peak group count) is sufficient, combined with IM plan and TRTC resources.
+4. When the business needs the same user on multiple devices in the same meeting, confirm the plan supports multi-device login; otherwise assign different userIds to different devices.
+
+## 5. Expected Results
+
+- Concurrent meeting count is constrained by plan room count limit and single room capacity.
+- When a single SDK instance joins multiple conference rooms, exceeding 1 causes the earliest joined room to be exited.
+- The same userId on multiple devices joining the same room results in mutual kick (later kicks earlier).
+- Multi-device access to the same meeting requires plan support for multi-device login, or assigning different userIds to different devices.
+
+## 6. Common Pitfalls
+
+- Pitfall 1: Assuming room count limit (peak group count) means "unlimited rooms at any time" (billed by natural month peak, not unlimited concurrency).
+- Pitfall 2: Assuming a single SDK instance can be in multiple conference rooms simultaneously (per-device limit is 1).
+- Pitfall 3: Assuming the same userId on multiple devices can join the same room simultaneously (mutual kick by default).
+- Pitfall 4: Ignoring plan version differences (multi-device login only supported in higher-tier plans).
+
+## 7. Problem Definition (retrieval hint)
+
+Whether TUIRoomKit has an upper limit on the number of concurrent meetings, and whether a single user can join multiple rooms simultaneously.
+
+## 8. Alternative Queries (retrieval recall)
+
+- What is the TUIRoomKit concurrent room limit?
+- How many meetings can run simultaneously?
+- Can the same user join two rooms at the same time?
+- What is the maximum number of participants per room?
+- Does TUIRoomKit support multi-device login?
+- Will the same userId on multiple devices cause mutual kick?
+- How to expand the meeting room capacity?

package/resource/knowledge/roomkit/best-practice/common/room-screen-share-preview.md

@@ -0,0 +1,83 @@
+---
+title: "TUIRoomKit Screen Sharing Local Preview and Avoiding Infinite Mirroring（TUIRoomKit / 屏幕共享 / 本地预览 / 无限套娃）"
+product: room
+frameworks: [react, vue, web]
+scope: platform_common
+tags: [TUIRoomKit, screen sharing, local preview, startScreenSharing, startScreenShare, full-screen sharing, infinite mirroring, infinite recursion, window sharing, external monitor, useDeviceState, view parameter]
+version_range: ">=2.0.0"
+---
+
+# TUIRoomKit Screen Sharing Local Preview and Avoiding Infinite Mirroring
+
+## 1. Key Takeaways
+
+- The `view` parameter enables local display of the shared content: passing a valid `view` renders the shared screen in a local container (local preview); omitting it or passing `null` skips local preview rendering.
+- Full-screen sharing with local preview causes "infinite mirroring/recursion": the local preview area is within the captured full screen/current page, so the preview image re-enters the capture, creating recursive mirroring.
+- **Preferred solution: share a "window" instead of the full screen**, preventing the meeting page from being captured and causing recursion.
+  - **Note for sharing WPS**: typically you cannot capture the "slideshow window" independently (the slideshow window and editor window behave inconsistently in the capture list). In this case, have the user connect an **external monitor**: place the slideshow on the external screen, then share that monitor/corresponding window. The main meeting screen continues operating, and the preview is less likely to recurse.
+- **Fallback solution**: when window sharing is not possible and no external monitor is available, make the local preview container as small as possible (shrink the `view` container) to significantly reduce the recursive mirroring impact; or do not pass `view` / pass `null` for local preview, using only a "sharing in progress" status indicator.
+
+## 2. Field / API Reference
+
+| Field / Capability | Purpose | Notes |
+|---|---|---|
+| `view` | Local screen share preview container | Pass a valid DOM element or id to render local preview; pass `null` to skip |
+| `startScreenSharing` | Screen sharing API | TRTC Web / Room screen sharing; `view` specifies local preview |
+| `startScreenShare` | Underlying screen sharing | TRTC `startScreenShare`, consistent with Atomicx |
+| `useDeviceState().startScreenShare` | Atomicx no-UI path | Screen sharing entry; local preview determined by preview view/container |
+
+## 3. Mechanism & Sequence
+
+### Local Preview
+
+Call screen sharing API with a valid `view` -> local container renders the shared screen (local preview) -> omitting `view` or passing `null` skips local preview rendering.
+
+## 4. Standard Usage
+
+### Screen Sharing with Local Preview
+
+```javascript
+// TRTC Web / Room screen sharing, view specifies local preview container (element or id)
+startScreenShare({
+  view: 'local-preview-container',   // 传入有效 view，本地渲染分享画面
+  // 传 null 则不渲染本地预览
+});
+```
+
+### Avoiding Infinite Mirroring
+
+```javascript
+// 方案 1：优先分享窗口而非整屏，从源头避免套娃
+startScreenShare({ view: 'local-preview-container' });  // 选择窗口采集源
+
+// 方案 2（兜底）：无法分享窗口时，缩小本地预览容器或本地不传 view
+startScreenShare({ view: null });  // 不渲染本地预览，仅用"正在共享"状态提示
+```
+
+## 5. Expected Results
+
+- Passing a valid `view`: local container renders the shared screen, enabling local preview.
+- Omitting / passing `null`: no local preview rendering; only remote participants see the shared screen.
+- Full-screen sharing + local preview: may cause infinite mirroring; switch to window sharing or shrink the preview.
+- Sharing WPS slideshow: use the external monitor approach to avoid mirroring.
+
+## 6. Common Pitfalls
+
+- Pitfall 1: Assuming `view` is a remote rendering parameter (`view` specifies the local screen share preview).
+- Pitfall 2: Giving up local preview entirely because full-screen sharing causes mirroring (switch to window sharing or shrink the preview instead).
+- Pitfall 3: Assuming you can capture the WPS slideshow window independently (typically not possible; use an external monitor).
+- Pitfall 4: Confusing `startScreenSharing` with `startScreenShare` (they are consistent at the underlying level; both use `view` for local preview).
+
+## 7. Problem Definition (retrieval hint)
+
+Whether the `view` parameter in TUIRoomKit screen sharing enables local preview of the shared content, and how to avoid infinite mirroring/recursion when sharing the full screen with local preview enabled.
+
+## 8. Alternative Queries (retrieval recall)
+
+- Can screen sharing show a local preview?
+- What is the TUIRoomKit screen sharing startScreenShare view parameter?
+- How to avoid infinite mirroring when sharing full screen?
+- What to do about recursive mirroring in screen sharing?
+- Is it better to share a window or the full screen?
+- How to shrink the local preview window?
+- How to hide local preview for screen sharing?