@tencent-rtc/mcp 1.6.7 → 1.6.8

package/resource/knowledge/callkit/faq/android.md

@@ -1,19 +1,19 @@
 ### The error message "The package you purchased does not support this ability"?
 
-If you encounter the above error message, it is because the audio and video call capability package of your current application has expired or has not been activated. You can refer to the service activation guide to claim or activate the audio and video call capability, and then continue to use the TUICallKit component.
+If you encounter the above error message, it is because the audio and video call capability package of your current application has expired or has not been activated. You can .
 
 ### When the application is offline, Will it can pop up the call view?
 
 During a one-to-one call, if you come online within the timeout period, an incoming call view will be triggered;  For group calls, if you come online within the timeout period, the last 20 unprocessed group messages will be pulled up, and if a call invitation exists, it will trigger an incoming call. The display strategy for incoming calls see: Incoming call display policy for the callee.
 
 ### When the application is in the background, Will it can pop up the call view?
-1. TUICallKit has two different display policy for the callee, see below: Incoming call display policy for the callee.
+1. TUICallKit has two different display policy for the callee.
 
 2. Before version 2.3 of TUICallKit, to automatically bring the application from the background to the foreground, it was necessary to check whether the app had enabled the "Background self-start" or "Floating window" permission.
 
    Different manufacturers, or even the same manufacturer with different Android versions, offer varying permissions and permission names for applications. For instance, Xiaomi 6 requires only the "Background pop-ups" permissions , while Redmi needs both the "Background pop-ups"  and "Display over other applications" permissions.
 
-   How to enable permissions, see below: Relevant permissions enabled.
+ How to enable permissions.
 
 3. If you encounter the following scenarios where the call interface cannot be pulled up, the reason is that changes in the application's launch stack caused the CallKitActivity interface to be obscured or removed.
 
@@ -23,7 +23,7 @@ During a one-to-one call, if you come online within the timeout period, an incom
 
    Scenario Three: When the app is in the background and an offline push notification is received, not clicking the push notification but entering the app via the desktop icon will either fail to bring up the CallKitActivity or cause the CallKitActivityto flash momentarily.
 
-   In the above scenarios, you need to add the following code to the default Activity of your app. Each app's default Activity may differ. Refer to the AndroidManifest.xml configuration for more details. Taking the launch page SplashActivity for most applications as an example:
+ In the above scenarios, you need to add the following code to the default Activity of your app. Each app's default Activity may differ. .xml configuration for more details. Taking the launch page SplashActivity for most applications as an example:
 
 【Code】
 ``` java
@@ -40,10 +40,6 @@ if (!isTaskRoot() && getIntent() != null && getIntent().hasCategory(Intent.CATEG
 
 To make TUICallKit adaptable to different business needs, add product features, and improve user experience, TUICallKit **version 2.3 and above** (Release Log) optimized the call page display pop-up strategy after receiving a call, as detailed below:
 
-|Full screen display of incoming call|Banner display of incoming call|
-|---------|---------|
-|||
-
 1. If you want the callee to pull up the full-screen call view when receiving a call, you can integrate the [tuicallkit-kt](https://github.com/Tencent-RTC/TUICallKit/tree/main/Android/tuicallkit-kt) code. By default, the incoming call display strategy for the callee is as follows:
 
 2. If you prefer to show a banner when receiving a call and then pull up the full-screen  as needed, you can enable this feature by calling the following interface.
@@ -52,8 +48,6 @@ To make TUICallKit adaptable to different business needs, add product features,
      TUICallKit.createInstance(context).enableIncomingBanner(true);
    ```
 
-   Once enabled, the callee's incoming call strategy is as shown below, as long as the **floating window permission** is enabled, the call banner will be displayed as much as possible.
-
    > **Note:**
    >
    > For information on how to enable related permissions, see below: Relevant permissions enabled.
@@ -69,10 +63,6 @@ To ensure a good calling experience, it is recommended to enable "notification"
 
 After the application is installed, you can long-press the application Icon, select "Application Information", then enable "notification" permission, "Display over other applications" and "Background pop-ups" permissions. Alternatively, you can go to `Mobile Phone > System Settings > Application Management > Application` to manually enable these permissions.
 
-|Pixel 4a|VIVO|
-|---------|---------|
-|||
-
 【Code guidance】
 - **Notification permissions**: For showcasing push notifications: please refer to [Notification runtime permissions](https://developer.android.com/develop/ui/views/notifications/notification-permission) and [Request runtime permissions](https://developer.android.com/training/permissions/requesting#request-permission) and implement according to business needs.
 

package/resource/knowledge/callkit/faq/common.md

@@ -16,8 +16,6 @@ After the call is connected, you can obtain the call room number (RoomId) throug
 
 ### Encounter error code "-3301" with the message "Services are not available in your region" after entering the room
 
-If you receive this error code, [contact us](https://trtc.io/contact) for support.
-
 ### In the TUIChat + TUICallKit Integrated Scenarios, after Upgrading the TUICallKit Version, New Version Calls Old Version and Old Version Is Unable to Receive Call Issues
 
 Starting from TUICallKit version 3.1, in the TUIChat + TUICallKit integrated scenarios, initiating a call through the call button in TUIChat by default uses the new calls API. Therefore, if your business has already gone live, you can use the advanced API to switch the call interface to call or groupCall to maintain interconnectivity with users of the online edition.

package/resource/knowledge/callkit/faq/error-code.md

@@ -28,7 +28,6 @@ Video and audio calls use Tencent Cloud's Chat SDK as the basic service for comm
 |8010|The signaling request ID is invalid or has been processed.|
 
 > **Note：**
->
 > More Chat SDK error codes are available at：[Chat Error Code](https://www.tencentcloud.com/document/product/1047/34348)
 >
 
@@ -46,10 +45,9 @@ Video and audio calls use Tencent Cloud's Chat SDK as the basic service for call
 |ERR_MIC_NOT_AUTHORIZED|-1317|No permission to access to the mic. This usually occurs on mobile devices and may be because the user denied access.|
 |ERR_MIC_SET_PARAM_FAIL|-1318|Failed to set mic parameters.|
 |ERR_MIC_OCCUPY|-1319|The mic is being used. The mic cannot be turned on when, for example, the user is having a call on the mobile device.|
-|ERR_TRTC_ENTER_ROOM_FAILED|-3301|Failed to enter the room. For the reason, refer to the error message for -3301.|
+|ERR_TRTC_ENTER_ROOM_FAILED|-3301|Failed to enter the room. For the reason.|
 
 > **Note：**
->
 > More TRTC SDK error codes are available at：[TRTC Error Code](https://www.tencentcloud.com/document/product/647/35130)
 >
 
@@ -60,6 +58,6 @@ New version of CallKit REST API error codes, for example, when retrieving call s
 |Error Code|Description|
 |---------|---------|
 |101001|Internal server error, please try again.|
-|101002|Invalid parameter, check if parameters meet requirements. Refer to error message for specific invalid field.|
+|101002|Invalid parameter, check if parameters meet requirements. .|
 |101004|Call does not exist or has already ended.|
 |101050|Call record does not exist.|

package/resource/knowledge/callkit/faq/ios.md

@@ -1,6 +1,6 @@
 ### The error message "The package you purchased does not support this ability"?
 
-If you encounter the above error message, it is because the audio and video call capability package of your current application has expired or has not been activated. You can refer to the service activation guide to claim or activate the audio and video call capability, and then continue to use the TUICallKit component.
+If you encounter the above error message, it is because the audio and video call capability package of your current application has expired or has not been activated. You can .
 
 ### How to modify TUICallKit source code?
 
@@ -88,8 +88,6 @@ Tencent Cloud's audio and video libraries cannot be integrated at the same time,
 
 ### Does TUICallKit support background operation?
 
-Yes, if you need to continue running related functions in the background, you can select the current project, and in the Background Modes section under Capabilities, check **Audio, AirPlay, and Picture in Picture**, as shown in the following image:
-
 ### How to view TRTC logs?
 
 TRTC logs are compressed and encrypted by default, with the extension .xlog. Whether the log is encrypted can be controlled by setLogCompressEnabled. The file name containing C(compressed) is encrypted and compressed, and the file name containing R(raw) is plaintext.
@@ -97,6 +95,5 @@ TRTC logs are compressed and encrypted by default, with the extension .xlog. Whe
 iOS：Sandbox's `Documents/log`
 
 > **Note:**
->
 > - To view the .xlog file, you need to download the [decryption tool](https://dldir1.qq.com/hudongzhibo/log_tool/decode_mars_log_file.py) and run it directly in the Python 2.7 environment with the xlog file in the same directory using python decode_mars_log_file.py.
 > - To view the .clog file (new log format after version 9.6), you need to download the [decryption tool](http://dldir1.qq.com/hudongzhibo/log_tool/decompress_clog.py) and run it directly in the Python 2.7 environment with the clog file in the same directory using python decompress_clog.py.

package/resource/knowledge/callkit/preset/android/api.md

@@ -241,7 +241,6 @@ fun enableVirtualBackground(enable: Boolean);
 This API is used to make a (one-to-one) call.
 
 > **Note:**
->
 > **It is recommended to use the** [calls](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-store/calls.html) **API.**
 >
 
@@ -267,7 +266,6 @@ The parameters are described below:
 This API is used to make a (one-to-one) call, Support for custom room ID, call timeout, offline push content, etc.
 
 > **Note:**
->
 > **It is recommended to use the** [calls](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-store/calls.html) **API.**
 >
 
@@ -298,7 +296,6 @@ The parameters are described below:
 This API is used to make a group call.
 
 > **Note:**
->
 > - It is recommended to use the [calls](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-store/calls.html) API.
 > - Before making a group call, you need to create an Chat group first.
 > - For details about how to create a group, see [Chat Group Management](https://www.tencentcloud.com/zh/document/product/1047/48466#.E5.88.9B.E5.BB.BA.E7.BE.A4.E7.BB.84), or you can use [Chat UIKit](https://www.tencentcloud.com/en/document/product/1047/50057) to integrate chat, call and other scenarios.
@@ -326,7 +323,6 @@ The parameters are described below:
 This API is used to make a group call, Support for custom room ID, call timeout, offline push content, etc.
 
 > **Note:**
->
 > - It is recommended to use the [calls](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-store/calls.html) API.
 > - Before making a group call, you need to create an Chat group first.
 > - For details about how to create a group, see [Chat Group Management](https://www.tencentcloud.com/zh/document/product/1047/48466#.E5.88.9B.E5.BB.BA.E7.BE.A4.E7.BB.84), or you can use [Chat UIKit](https://www.tencentcloud.com/en/document/product/1047/50057) to integrate chat, call and other scenarios.
@@ -360,7 +356,6 @@ The parameters are described below:
 This API is used to join a group call.
 
 > **Note:**
->
 > - It is recommended to use the [join](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.call/-call-store/join.html) API.
 > - Before joining a group call, you need to create or join an Chat group in advance, and there are already users in the group who are in the call.
 > - For details about how to create a group, see [Chat Group Management](https://www.tencentcloud.com/zh/document/product/1047/48466#.E5.88.9B.E5.BB.BA.E7.BE.A4.E7.BB.84), or you can use [Chat UIKit](https://www.tencentcloud.com/en/document/product/1047/50057) to integrate chat, call and other scenarios.
@@ -388,7 +383,6 @@ The parameters are described below:
 Hide the specified button.
 
 > **Note：**
->
 > - Currently supports hiding the following buttons:
 > Camera, Microphone, Audio Device, Switch Camera, Invite User
 >

package/resource/knowledge/callkit/preset/ios/api.md

@@ -136,7 +136,6 @@ public func setScreenOrientation(orientation: Int, completion: CompletionClosure
 This API is used to make a (one-to-one) call.
 
 > **Note：**
->
 > It is recommended to use the [calls](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callstore/calls(participantids:callmediatype:params:completion:)) API
 >
 
@@ -154,7 +153,6 @@ public func call(userId: String, callMediaType: TUICallMediaType)
 This API is used to make a (one-to-one) call, support for custom room ID, call timeout, offline push content, etc.
 
 > **Note：**
->
 > It is recommended to use the [calls](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callstore/calls(participantids:callmediatype:params:completion:)) API
 >
 
@@ -174,7 +172,6 @@ public func call(userId: String, callMediaType: TUICallMediaType, params: TUICal
 This API is used to make a group call.
 
 > **Note:**
->
 > - It is recommended to use the [calls](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callstore/calls(participantids:callmediatype:params:completion:)) API
 > - Before making a group call, you need to create a Chat group first.
 > - For details about how to create a group, see [Chat Group Management](https://www.tencentcloud.com/en/document/product/1047/48466#.E5.88.9B.E5.BB.BA.E7.BE.A4.E7.BB.84), or you can use [Chat UIKit](https://www.tencentcloud.com/document/product/1047/50056) to integrate chat, call and other scenarios.
@@ -194,7 +191,6 @@ public func groupCall(groupId: String, userIdList: [String], callMediaType: TUIC
 This API is used to make a group call, support for custom room ID, call timeout, offline push content, etc.
 
 > **Note:**
->
 > - It is recommended to use the [calls](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callstore/calls(participantids:callmediatype:params:completion:)) API.
 > - Before making a group call, you need to create a Chat group first.
 > - For details about how to create a group, see [Chat Group Management](https://www.tencentcloud.com/en/document/product/1047/48466#.E5.88.9B.E5.BB.BA.E7.BE.A4.E7.BB.84), or you can use [Chat UIKit](https://www.tencentcloud.com/document/product/1047/50056) to integrate chat, call and other scenarios.

package/resource/knowledge/callkit/preset/react/api.md

@@ -36,7 +36,7 @@ The TUICallKit API is the **audio and video call component that includes a UI in
 |afterCalling|This function will be executed after the termination of the call|function()|No|-|√|√|
 |onMinimized|This function will be executed when the component switches to a minimized state. The explanation for the STATUS value is|function(oldStatus, newStatus)|No|-|√|√|
 |kickedOut|The events thrown by the component occur when the current logged-in user is ejected. The call will also automatically terminate|function()|No|-|√|×|
-|statusChanged|Event thrown by the component; this event is triggered when the call status changes. For detailed types of call status, refer to STATUS value description|function({oldStatus, newStatus})|No|-|√|×|
+|statusChanged|Event thrown by the component; this event is triggered when the call status changes. For detailed types of call status,
 
 ### Sample code
 
@@ -83,9 +83,9 @@ try {
 The parameters are described below:
 | Parameter | Type | Required | Meaning |
 | --- | --- | --- | --- |
-| SDKAppID | Number | Yes | The SDKAppID of your app, you can find your SDKAppID in the Live Audio and Video console. For details, see Activating Services |
+| SDKAppID | Number | Yes | The SDKAppID of your app, you can find your SDKAppID in the Live Audio and Video console.
 | userID | String | Yes | The current user's ID is of string type, only allowing for the inclusion of English letters (a-z and A-Z), digits (0-9), hyphens (-) and underscores (_) |
-| userSig | String | Yes | Use SDKSecretKey to encrypt SDKAppID, UserID and other information to obtain userSig.<br>It is an authentication ticket used by Tencent Cloud to identify whether the current user can use TRTC services. For how to obtain it, please refer to How to Calculate UserSig |
+| userSig | String | Yes | Use SDKSecretKey to encrypt SDKAppID, UserID and other information to obtain userSig.<br>It is an authentication ticket used by Tencent Cloud to identify whether the current user can use TRTC services. For how to obtain it, please
 | tim | TencentCloudChat | No | tim is an instance of <a href="https://www.npmjs.com/package/@tencentcloud/chat">TencentCloudChat</a> SDK. |
 
 ### calls
@@ -151,7 +151,6 @@ The parameters are described below:
 Set your own nickname and avatar.
 
 > **Note:**
->
 > **If you use this interface to modify user information during a call, the UI will not be updated immediately, and you will need to wait until the next call to see the changes.**
 >
 

package/resource/knowledge/callkit/preset/react/uikit-api-reference.md

@@ -36,7 +36,7 @@ The TUICallKit API is the **audio and video call component that includes a UI in
 |afterCalling|This function will be executed after the termination of the call|function()|No|-|√|√|
 |onMinimized|This function will be executed when the component switches to a minimized state. The explanation for the STATUS value is|function(oldStatus, newStatus)|No|-|√|√|
 |kickedOut|The events thrown by the component occur when the current logged-in user is ejected. The call will also automatically terminate|function()|No|-|√|×|
-|statusChanged|Event thrown by the component; this event is triggered when the call status changes. For detailed types of call status, refer to STATUS value description|function({oldStatus, newStatus})|No|-|√|×|
+|statusChanged|Event thrown by the component; this event is triggered when the call status changes. For detailed types of call status,
 
 ### Sample code
 
@@ -83,9 +83,9 @@ try {
 The parameters are described below:
 | Parameter | Type | Required | Meaning |
 | --- | --- | --- | --- |
-| SDKAppID | Number | Yes | The SDKAppID of your app, you can find your SDKAppID in the Live Audio and Video console. For details, see Activating Services |
+| SDKAppID | Number | Yes | The SDKAppID of your app, you can find your SDKAppID in the Live Audio and Video console.
 | userID | String | Yes | The current user's ID is of string type, only allowing for the inclusion of English letters (a-z and A-Z), digits (0-9), hyphens (-) and underscores (_) |
-| userSig | String | Yes | Use SDKSecretKey to encrypt SDKAppID, UserID and other information to obtain userSig.<br>It is an authentication ticket used by Tencent Cloud to identify whether the current user can use TRTC services. For how to obtain it, please refer to How to Calculate UserSig |
+| userSig | String | Yes | Use SDKSecretKey to encrypt SDKAppID, UserID and other information to obtain userSig.<br>It is an authentication ticket used by Tencent Cloud to identify whether the current user can use TRTC services. For how to obtain it, please
 | tim | TencentCloudChat | No | tim is an instance of <a href="https://www.npmjs.com/package/@tencentcloud/chat">TencentCloudChat</a> SDK. |
 
 ### calls
@@ -151,7 +151,6 @@ The parameters are described below:
 Set your own nickname and avatar.
 
 > **Note:**
->
 > **If you use this interface to modify user information during a call, the UI will not be updated immediately, and you will need to wait until the next call to see the changes.**
 >
 

package/resource/knowledge/callkit/preset/vue/api.md

@@ -36,7 +36,7 @@ The TUICallKit API is the **audio and video call component that includes a UI in
 |afterCalling|This function will be executed after the termination of the call|function()|No|-|√|√|
 |onMinimized|This function will be executed when the component switches to a minimized state. The explanation for the STATUS value is|function(oldStatus, newStatus)|No|-|√|√|
 |kickedOut|The events thrown by the component occur when the current logged-in user is ejected. The call will also automatically terminate|function()|No|-|√|×|
-|statusChanged|Event thrown by the component; this event is triggered when the call status changes. For detailed types of call status, refer to STATUS value description|function({oldStatus, newStatus})|No|-|√|×|
+|statusChanged|Event thrown by the component; this event is triggered when the call status changes. For detailed types of call status,
 
 ### Sample code
 
@@ -103,9 +103,9 @@ try {
 The parameters are described below:
 | Parameter | Type | Required | Meaning |
 | --- | --- | --- | --- |
-| SDKAppID | Number | Yes | The SDKAppID of your app, you can find your SDKAppID in the Live Audio and Video console. For details, see Activating Services |
+| SDKAppID | Number | Yes | The SDKAppID of your app, you can find your SDKAppID in the Live Audio and Video console.
 | userID | String | Yes | The current user's ID is of string type, only allowing for the inclusion of English letters (a-z and A-Z), digits (0-9), hyphens (-) and underscores (_) |
-| userSig | String | Yes | Use SDKSecretKey to encrypt SDKAppID, UserID and other information to obtain userSig.<br>It is an authentication ticket used by Tencent Cloud to identify whether the current user can use TRTC services. For how to obtain it, please refer to How to Calculate UserSig |
+| userSig | String | Yes | Use SDKSecretKey to encrypt SDKAppID, UserID and other information to obtain userSig.<br>It is an authentication ticket used by Tencent Cloud to identify whether the current user can use TRTC services. For how to obtain it, please
 | tim | TencentCloudChat | No | tim is an instance of <a href="https://www.npmjs.com/package/@tencentcloud/chat">TencentCloudChat</a> SDK. |
 
 ### calls
@@ -171,7 +171,6 @@ The parameters are described below:
 Set your own nickname and avatar.
 
 > **Note:**
->
 > **If you use this interface to modify user information during a call, the UI will not be updated immediately, and you will need to wait until the next call to see the changes.**
 >
 

package/resource/knowledge/callkit/preset/vue/uikit-api-reference.md

@@ -36,7 +36,7 @@ The TUICallKit API is the **audio and video call component that includes a UI in
 |afterCalling|This function will be executed after the termination of the call|function()|No|-|√|√|
 |onMinimized|This function will be executed when the component switches to a minimized state. The explanation for the STATUS value is|function(oldStatus, newStatus)|No|-|√|√|
 |kickedOut|The events thrown by the component occur when the current logged-in user is ejected. The call will also automatically terminate|function()|No|-|√|×|
-|statusChanged|Event thrown by the component; this event is triggered when the call status changes. For detailed types of call status, refer to STATUS value description|function({oldStatus, newStatus})|No|-|√|×|
+|statusChanged|Event thrown by the component; this event is triggered when the call status changes. For detailed types of call status,
 
 ### Sample code
 
@@ -103,9 +103,9 @@ try {
 The parameters are described below:
 | Parameter | Type | Required | Meaning |
 | --- | --- | --- | --- |
-| SDKAppID | Number | Yes | The SDKAppID of your app, you can find your SDKAppID in the Live Audio and Video console. For details, see Activating Services |
+| SDKAppID | Number | Yes | The SDKAppID of your app, you can find your SDKAppID in the Live Audio and Video console.
 | userID | String | Yes | The current user's ID is of string type, only allowing for the inclusion of English letters (a-z and A-Z), digits (0-9), hyphens (-) and underscores (_) |
-| userSig | String | Yes | Use SDKSecretKey to encrypt SDKAppID, UserID and other information to obtain userSig.<br>It is an authentication ticket used by Tencent Cloud to identify whether the current user can use TRTC services. For how to obtain it, please refer to How to Calculate UserSig |
+| userSig | String | Yes | Use SDKSecretKey to encrypt SDKAppID, UserID and other information to obtain userSig.<br>It is an authentication ticket used by Tencent Cloud to identify whether the current user can use TRTC services. For how to obtain it, please
 | tim | TencentCloudChat | No | tim is an instance of <a href="https://www.npmjs.com/package/@tencentcloud/chat">TencentCloudChat</a> SDK. |
 
 ### calls
@@ -171,7 +171,6 @@ The parameters are described below:
 Set your own nickname and avatar.
 
 > **Note:**
->
 > **If you use this interface to modify user information during a call, the UI will not be updated immediately, and you will need to wait until the next call to see the changes.**
 >
 

package/resource/knowledge/chat/preset/android/features/chat-setting.md

@@ -3,9 +3,6 @@
 ChatSetting is a set of chat settings components built with Jetpack Compose. It includes two main components: C2CChatSetting (C2C Chat Settings) and GroupChatSetting (Group Chat Settings).
 
 These components offer comprehensive chat session management features, such as user information management, permission controls, group management, and other essential capabilities.
-| <strong>C2C Chat Settings Interface</strong> | <strong>Group Chat Settings Interface</strong> |
-| --- | --- |
-|  |  |
 
 ## Component Integration
 
@@ -40,7 +37,6 @@ ChatSetting consists of two main components: C2CChatSetting (C2C Chat Settings)
 
 ## Basic Usage
 
-To display the C2C Chat Settings page, initialize C2CChatSetting as shown below:
 ``` swift
 Box {
     C2CChatSetting(
@@ -55,7 +51,6 @@ Box {
 }
 ```
 
-To display the Group Chat Settings page, initialize GroupChatSetting as shown below:
 ``` swift
 Box {
     GroupChatSetting(

package/resource/knowledge/chat/preset/android/features/contact-list.md

@@ -1,9 +1,6 @@
 ## Component Overview
 
 ContactList is a Jetpack Compose-based contact list component that provides users with robust contact management features. It supports displaying friends, handling friend requests, managing group lists, managing blacklists, and offers a comprehensive set of interactive webhook interfaces.
-| <strong>Contact List</strong> | <strong>Group List</strong> | <strong>Friend Request List</strong> |
-| --- | --- | --- |
-|  |  |  |
 
 ## Component Integration
 
@@ -19,15 +16,11 @@ The `ContactList` component is included in TUIKit Compose. To use `ContactList`,
 | <code>onContactClick: (ContactInfo) -> Unit</code> | Webhook triggered when a contact is clicked; this parameter is optional. |  |
 | <code>contactListViewModelFactory: ContactListViewModelFactory</code> | Factory for creating the internal ContactListViewModel. Typically, you do not need to provide this manually, as a default implementation is included. |  |
 
-The top section of `ContactList` provides entry points for subviews such as friend requests, group chat requests, group chat list, and blacklist. The bottom section displays the contact list, as shown below:
-
 ## Basic Usage
 - When you tap the entry points for friend requests, group chat requests, group chat list, or blacklist in `ContactList`, the component automatically handles navigation—no extra configuration is required.
 
 - When you tap a group in the group chat list or a contact in the contact list or blacklist, the corresponding webhook (`onGroupClick` or `onContactClick`) is triggered. You must handle these webhooks to implement custom navigation. See the routing example below:
 
-   To display the contact list directly, initialize `ContactList` as shown below:
-
    ``` swift
    Box(
        modifier = Modifier

package/resource/knowledge/chat/preset/android/features/conversation-list.md

@@ -1,9 +1,6 @@
 ## Component Overview
 
 ConversationList is a Jetpack Compose component designed to display and manage user chat conversations. It offers a comprehensive set of features for viewing and interacting with conversations.
-| <strong>Conversation List</strong> | <strong>Conversation Actions</strong> |
-| --- | --- |
-|  |  |
 
 ## Component Integration
 
@@ -112,6 +109,3 @@ ConversationList() {
 ```
 
 The following images show the customization effects:
-| <strong>Conversation Actions</strong><br><strong>(Default Options)</strong> | <strong>Conversation Actions</strong><br><strong>(Delete Option Hidden)</strong> | <strong>Conversation Actions</strong><br><strong>(Share Option Added)</strong> |
-| --- | --- | --- |
-|  |  |  |

package/resource/knowledge/chat/preset/android/features/language.md

@@ -4,10 +4,6 @@
 
 You can use these default language packs, customize translation strings, or add additional language packs as needed.
 
-|**English**|**Arabic**|**Simplified Chinese**|
-|---------|---------|---------|
-||||
-
 ## Using Built-in Languages
 
 If your application only needs to support **English**, **Simplified Chinese**, **Traditional Chinese**, or **Arabic**, follow the instructions in this section.
@@ -29,7 +25,6 @@ AppCompatDelegate.setApplicationLocales(LocaleListCompat.forLanguageTags("zh"))
 ```
 
 > **Notice：**
->
 > The `setApplicationLocales` method requires a dependency on androidx.appcompat:appcompat, version 1.6.0 or higher.
 >
 
@@ -74,7 +69,6 @@ atomic-x/src/main/
 Use the default `strings.xml` file in each module as a reference and translate each `key` into Korean.
 
 > **Note：**
->
 > 1. Multilingual resources for `TUIKit Compose` are distributed across multiple modules: `app`, `uikit`, and `atomic-x`. Add `values-ko` to all relevant modules.
 > 2. The `res-emoji-picker` module includes both `strings.xml` and `strings-emoji.xml`. When adding a new language, complete both files.
 > 3. For language codes, see Resource Qualifier Rules.
@@ -107,8 +101,6 @@ To set the interface language of `TUIKit Compose` to Korean, use `setApplication
 AppCompatDelegate.setApplicationLocales(LocaleListCompat.forLanguageTags("ko"))
 ```
 
-Once these steps are complete, the interface displays in Korean, as shown below:
-
 ## Appendix: Resource Qualifier Rules
 
 |Language|Code|Language|Code|

package/resource/knowledge/chat/preset/android/features/message-input.md

@@ -1,9 +1,6 @@
 ## Component Overview
 
 MessageInput is a Jetpack Compose component that provides a full-featured message input interface for users. It supports composing and sending various message types, including text, images, videos, files, and voice messages. Additional features include emoji selection, flexible style configuration, and extensive customization options.
-| <strong>Message Input Interface</strong> | <strong>Emoji Picker</strong> |
-| --- | --- |
-|  |  |
 
 ## Component Integration
 
@@ -52,6 +49,3 @@ MessageInput(
 ```
 
 See the customization results below:
-| <strong>Default Input Box</strong> | <strong>Audio Recording Hidden</strong> | <strong>All Features Hidden</strong> |
-| --- | --- | --- |
-|  |  |  |

package/resource/knowledge/chat/preset/android/features/message-list.md

@@ -7,10 +7,6 @@ MessageList is a Jetpack Compose component designed to display and manage chat m
 
 - Highly customizable: configure styles (bubble color, corner radius, font, etc.) and custom action items.
 
-| <strong>Chat Message List</strong> | <strong>Message Long-Press Menu</strong> |
-| --- | --- |
-|  |  |
-
 ## Component Integration
 
 MessageList is part of TUIKit Compose. To use MessageList, integrate TUIKit Compose into your project. For integration instructions, see the [TUIKit Compose documentation](https://www.tencentcloud.com/document/product/1047/77459).
@@ -131,11 +127,7 @@ MessageList(
 ```
 
 > **Note：**
->
 > Local configuration takes precedence over global configuration.
 >
 
 Customization examples:
-| <strong>Message List Actions</strong><br><strong>(Default Options)</strong> | <strong>Message List Actions</strong><br><strong>(Copy Option Hidden)</strong> | <strong>Message List Actions</strong><br><strong>(Share Option Added)</strong> |
-| --- | --- | --- |
-|  |  |  |

package/resource/knowledge/chat/preset/android/features/search.md

@@ -3,14 +3,9 @@
 Search component provides users with a complete set of features, including a search box, search results display, and navigation within the interface. The component supports user search, group search, and message search, and offers a comprehensive set of interactive webhook interfaces.
 
 > **Note：**
->
 > Search function is available in the Pro edition or Enterprise edition. You can use this feature after purchasing the Pro edition or Enterprise edition package. For details, see [Pricing Information](https://trtc.io/document/67650).
 >
 
-| <strong>Search Entry</strong> | <strong>Search Results</strong> |
-| --- | --- |
-|  |  |
-
 ## Component Integration
 
 The Search component is included in TUIKit Compose. To use the Search component, integrate TUIKit Compose into your project. For integration instructions, refer to the [TUIKit Compose documentation](https://www.tencentcloud.com/document/product/1047/77459) and complete the login process.
@@ -36,8 +31,6 @@ The routing logic for search results in `SearchScreen` is as follows:
 
     Example:
 
-    Initialize the `SearchScreen` component as shown below:
-
    ``` java
    SearchScreen(
        modifier = Modifier.Companion

package/resource/knowledge/chat/preset/android/features/theme.md

@@ -1,9 +1,6 @@
 TUIKit Compose offers flexible appearance customization with support for Light, Dark, and System theme modes, along with customizable primary colors. A simple configuration enables theme switching and brand color application throughout your app.
 
 For example, in the message list, you can see how different theme modes and primary colors affect the UI:
-| <strong>Light + Default Color</strong> | <strong>Light + Orange</strong> | <strong>Dark + Default Color</strong> | <strong>Dark + Green Theme</strong> |
-| --- | --- | --- | --- |
-|  |  |  |  |
 
 ## Key Features
 
@@ -41,7 +38,6 @@ All theme configuration and queries are handled through concise APIs in `ThemeSt
 |`clearPrimaryColor`|None|`Unit`|Resets the primary color to the default blue.|
 
 > **Note：**
->
 > - When you call setThemeMode or setPrimaryColor, your settings are automatically saved to persistent storage. No manual saving is required. The configuration will be loaded automatically the next time the app starts.
 > - Changing theme settings automatically clears the cache to ensure real-time color updates. You do not need to manage the cache manually.
 > - Avoid frequent theme switching in your code (for example, do not call these APIs in a loop).

package/resource/knowledge/chat/preset/android-view/integration.md

@@ -162,7 +162,6 @@ LoginStore.shared.login(
 ```
 
 > **Note:**
->
 > In a production environment, we recommend generating UserSig on your server. When needed, your app should request a dynamic UserSig from your business server for authentication. For details, see [Generating UserSig on the Server](https://intl.cloud.tencent.com/document/product/1047/34385).
 >
 
@@ -232,7 +231,6 @@ class ChatActivity : AppCompatActivity() {
 ```
 
 > **Note:**
->
 > The Activity that hosts the chat page **must** use a Material Components theme, such as `setTheme(com.google.android.material.R.style.Theme_MaterialComponents_Light_NoActionBar)`. Otherwise, Material controls used inside `ChatPageView` may crash at runtime because required theme attributes are missing.
 >
 
@@ -286,7 +284,3 @@ ThemeStore.shared(context).setTheme(Theme.lightTheme(context))
 ##### Using Emoji Packs
 
 To respect emoji design copyrights, the Chat Demo/TUIKit project does not include large emoji image assets. Before commercial release, replace them with emoji packs designed by you or otherwise licensed to you. The default **smiley emoji pack shown below is copyrighted by Tencent Cloud**, and you can use it for free by upgrading to [Chat Pro Plus or Enterprise Edition](https://console.trtc.io/subscription/buy/chat).
-
-## Contact Us
-
-If you have any questions or suggestions during integration or use, [contact us](https://trtc.io/contact) to submit feedback.

package/resource/knowledge/chat/preset/flutter/features/chat-setting.md

@@ -3,9 +3,6 @@
 ChatSetting is a suite of chat settings components, featuring two primary modules: C2CChatSetting for one-on-one chat settings and GroupChatSetting for group chat settings.
 
 These components offer a complete set of tools for managing chat sessions, including user information management, permission controls, group management, and other essential features.
-| C2C Chat Settings Interface | Group Chat Settings Interface |
-| --- | --- |
-|  |  |
 
 ## Component Integration
 
@@ -37,7 +34,6 @@ ChatSetting provides two main components: C2CChatSetting for one-on-one chat set
 
 ## Basic Usage
 
-To display the one-on-one chat settings page, initialize C2CChatSetting as shown below:
 ``` swift
 C2CChatSetting(
   userID: userID,

package/resource/knowledge/chat/preset/flutter/features/contact-list.md

@@ -1,9 +1,6 @@
 ## Component Overview
 
 ContactList is a full-featured contact management component designed for chat applications. It enables users to view friend lists, process friend requests, manage group lists, and maintain blacklists. The component also provides a robust set of interactive webhook interfaces for custom event handling.
-| <strong>Contact List</strong> | <strong>Group List</strong> | <strong>Friend Request List</strong> |
-| --- | --- | --- |
-|  |  |  |
 
 ## Component Integration
 
@@ -17,17 +14,11 @@ The `ContactList` component is included in TUIKit Flutter. To use `ContactList`,
 | <code>ContactList</code> | <code>onGroupClick: (ContactInfo contactInfo) {}</code> | Webhook triggered when a group is clicked. Optional. |
 | <code>onContactClick: (ContactInfo contactInfo) {}</code> | Webhook triggered when a contact is clicked. Optional. |  |
 
-The upper section of the `ContactList` displays navigation cells for subviews such as friend requests, group chat requests, group chat list, and blacklist. The lower section contains the contact list itself, as shown below:
-
 ## Basic Usage
 - When you tap the entry cells for friend requests, group chat requests, group chat list, or blacklist in `ContactList`, navigation to the appropriate subview is handled automatically—no additional configuration is required.
 
 - When you tap a group in the group list or a contact in the contact list or blacklist, the corresponding webhook (`onGroupClick` or `onContactClick`) is triggered. Listen to these webhooks to implement custom navigation or behaviors.
 
-   For example, route navigation can be handled as shown below:
-
-   To display the contact list directly, initialize `ContactList` as shown below:
-
    ``` swift
    ContactList(
      onGroupClick: (ContactInfo contactInfo) {

package/resource/knowledge/chat/preset/flutter/features/conversation-list.md

@@ -1,9 +1,6 @@
 ## Component Overview
 
 ConversationList is a UI component that displays and manages user chat conversations. It provides a robust feature set for conversation listing—enabling users to view conversations and perform key actions directly from the list.
-| <strong>Conversation List</strong> | <strong>Conversation Actions</strong> |
-| --- | --- |
-|  |  |
 
 ## Component Integration
 
@@ -118,11 +115,7 @@ Expanded(
 ```
 
 > **Note：**
->
 > Local configuration takes precedence over global configuration.
 >
 
 Below are examples of customization effects:
-| Conversation Actions (Default Options) | Conversation Actions (Delete Option Hidden) | Conversation Actions (Share Option Added) |
-| --- | --- | --- |
-|  |  |  |

package/resource/knowledge/chat/preset/flutter/features/language.md

@@ -1,14 +1,9 @@
 TUIKit Flutter includes built-in language packs for **Simplified Chinese, Traditional Chinese, English, Japanese, Korean, and Arabic**. These packs allow you to set the user interface language easily. With a simple configuration, you can enable dynamic language switching in your app.
 
-|Simplified Chinese|Traditional Chinese|English|Japanese|Korean|Arabic|
-|---------|---------|---------|---------|---------|---------|
-|||||||
-
 ## Using Built-in Languages
 
 ### Language Setup
 
-After integrating the component as described in [TUIKit Flutter](https://www.tencentcloud.com/document/product/1047/77489), you can enable internationalization using `LocaleProvider` and `AtomicLocalizations`. Wrap your app's main entry point with `MultiProvider`, and configure the language settings in `MaterialApp` as shown below. For a complete example, see the [demo](https://github.com/Tencent-RTC/TUIKit_Flutter/blob/main/chat/demo/lib/main.dart):
 ``` javascript
   @override
   Widget build(BuildContext context) {