@tencent-rtc/mcp 1.6.7 → 1.6.8

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/core-sdk/android/call-user-to-room.md

@@ -235,7 +235,3 @@ fun rejectCall(roomID: String, reason: CallRejectionReason = CallRejectionReason
 |Store/Component|Description|API Documentation|
 |---------|---------|---------|
 |**RoomStore**|Manages the full room lifecycle: create and join, join, leave, end room, update/retrieve room information, schedule rooms, invite external members, listen for passive room events (such as room dissolution, room info updates, etc).|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-store/index.html)|
-
-## Contact Us
-
-If you have any questions or suggestions during integration or usage, contact info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/android/room-participant-state.md

@@ -582,7 +582,3 @@ private fun subscribeParticipantState() {
 |Store/Component|Description|API Documentation|
 |---------|---------|---------|
 |**RoomParticipantStore**|Manages room participants: assign admin, transfer ownership, retrieve participant list, remove participant, control participant devices (close, invite to enable camera/microphone, etc.), request device enablement.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-participant-store/index.html)|
-
-## Contact Us
-
-If you have any questions or suggestions during integration or use, please contact info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/android/room-state.md

@@ -358,7 +358,3 @@ private fun subscribeCurrentRoomState() {
         **What does this mean for developers?**
 
         `participantCount` is a highly accurate, near real-time estimate. In rare cases with extremely high concurrency, brief delays or data loss may occur. We recommend using it for UI display only—not for billing, statistics, or scenarios requiring absolute precision.
-
-## Contact Us
-
-If you have questions or feedback during integration or usage, please email info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/android/schedule-room.md

@@ -94,7 +94,7 @@ Follow the Integration Overview to integrate the AtomicXCore SDK. Make sure you
 | <code>scheduleStartTime</code> | <code>Long</code> | Yes | - Scheduled start time (Unix timestamp in seconds).<br>- Must be greater than the current time.<br>- We recommend aligning to a future minute. Example: 1736164800 (2025-01-06 20:00:00). |
 | <code>scheduleEndTime</code> | <code>Long</code> | Yes | Scheduled end time (Unix timestamp in seconds).<br>- Must be greater than <code>scheduleStartTime</code>.<br>- Set based on expected duration, e.g., <code>scheduleStartTime</code> + 3600 for one hour. |
 | <code>reminderSecondsBeforeStart</code> | <code>Int</code> | No | - Reminder time before the scheduled start (seconds). Used for system-triggered notifications.<br>- Recommended: 300 (5 min) or 900 (15 min) for local app notifications. |
-| <code>scheduleAttendees</code> | <code>List</code> | No | - List of participant user IDs. The system will send invitations to these users.<br>- For details, see retrieving the participant list for scheduled rooms. |
+| <code>scheduleAttendees</code> | <code>List</code> | No | - List of participant user IDs. The system will send invitations to these users.<br>- . |
 | <code>isAllMicrophoneDisabled</code> | <code>Boolean</code> | No | Whether to mute all participants by default.<br>- true: Disabled.<br>- false: Not disabled (default). |
 | <code>isAllCameraDisabled</code> | <code>Boolean</code> | No | Whether to disable all participant cameras by default.<br>- true: Disabled.<br>- false: Not disabled (default). |
 | <code>isAllScreenShareDisabled</code> | <code>Boolean</code> | No | Whether to disable screen sharing for all participants.<br>- true: Disabled.<br>- false: Not disabled (default). |
@@ -334,7 +334,3 @@ If you are not receiving the upcoming event notification after scheduling a room
   - **Edge Case:** If the room is scheduled to start very soon (e.g., in 5 minutes) but the reminder is set for 10 minutes before start, the system cannot send the notification, and the event will be missed.
 
   - **Solution:** Ensure the scheduled start time is sufficiently further in the future than the reminder interval you've set.
-
-## Contact Us
-
-For questions or feedback during integration or usage, contact info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/ios/call-user-to-room.md

@@ -227,7 +227,3 @@ func rejectCall(roomID: String, reason: CallRejectionReason = .rejected) {
 |**Store/Component**|**Description**|**API Documentation**|
 |---------|---------|---------|
 |**RoomStore**|Room lifecycle management: create and join, join, leave, end room, update and retrieve room info, reserve room, call users outside the room, listen to passive room events (such as room dissolution, updates, etc.).|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/roomstore)|
-
-## Contact Us
-
-If you have any questions or suggestions during integration or usage, contact info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/ios/room-participant-state.md

@@ -563,7 +563,3 @@ private func subscribeParticipantState() {
 |**Store/Component**|**Description**|**API Documentation**|
 |---------|---------|---------|
 |**RoomParticipantStore**|Manage participants in the room: assign admin roles, transfer ownership, retrieve participant list, remove participants, control participant devices (e.g., close, invite to enable camera/microphone), request device enable (e.g., request to enable camera/microphone).|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/roomparticipantstore)|
-
-## Contact Us
-
-If you have any questions or suggestions during integration or use, please contact info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/ios/room-state.md

@@ -319,7 +319,3 @@ private func subscribeRoomState() {
       **What does this mean for developers?**
 
       `participantCount` provides a highly accurate, near real-time estimate. However, during periods of extremely high concurrency, updates may be briefly delayed or lost. We recommend using it for **UI display** purposes only, not for billing, analytics, or other scenarios requiring absolute precision.
-
-## Contact Us
-
-If you have questions or feedback during integration or usage, please email info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/ios/schedule-room.md

@@ -89,7 +89,7 @@ func scheduleRoom() {
 | <code>scheduleStartTime</code> | <code>Int</code> | Yes | - Scheduled start time (Unix timestamp in seconds).<br>- Must be greater than the current time.<br>- We recommend aligning to a future minute. Example: 1736164800 (2025-01-06 20:00:00). |
 | <code>scheduleEndTime</code> | <code>Int</code> | Yes | - Scheduled end time (Unix timestamp in seconds).<br>- Must be greater than <code>scheduleStartTime</code>.<br>- Set based on expected duration, e.g., <code>scheduleStartTime</code> + 3600 for one hour. |
 | <code>reminderSecondsBeforeStart</code> | <code>Int</code> | No | - Reminder time before the scheduled start (seconds). Used for system-triggered notifications.<br>- Recommended: 300 (5 min) or 900 (15 min) for local app notifications. |
-| <code>scheduleAttendees</code> | <code>[String]</code> | No | - List of participant user IDs. The system will send invitations to these users.<br>- For details, see retrieving the participant list for scheduled rooms. |
+| <code>scheduleAttendees</code> | <code>[String]</code> | No | - List of participant user IDs. The system will send invitations to these users.<br>- . |
 | <code>isAllMicrophoneDisabled</code> | <code>Bool</code> | No | Whether to mute all participants by default.<br>- true: Disabled.<br>- false: Not disabled (default). |
 | <code>isAllCameraDisabled</code> | <code>Bool</code> | No | Whether to disable all participant cameras by default.<br>- true: Disabled.<br>- false: Not disabled (default). |
 | <code>isAllScreenShareDisabled</code> | <code>Bool</code> | No | Whether to disable screen sharing for all participants.<br>- true: Disabled.<br>- false: Not disabled (default). |
@@ -316,7 +316,3 @@ If you are not receiving a "room starting soon" notification after scheduling, c
   - If the room's start time is too close (e.g., 5 minutes away) and the reminder is set too far in advance (e.g., 10 minutes before), the event will not trigger.
 
   - Make sure the scheduled start time is at least as far in the future as the reminder value you set.
-
-## Contact Us
-
-For questions or feedback during integration or usage, contact info_rtc@tencent.com.

package/resource/knowledge/roomkit/core-sdk/vue/call-user-to-room.md

@@ -138,7 +138,7 @@ onUnmounted(() => {
 
 ## Practical Tutorial: Improving the Call Answer Rate
 
-To achieve a higher call answer rate in your business, beyond implementing the basic functionality, it is recommended to refer to the following strategies to optimize the user experience:
+To achieve a higher call answer rate in your business, beyond implementing the basic functionality, it is recommended to
 
 ### 1. Enhance Call Awareness (Avoid Users Missing Calls)
 

package/resource/knowledge/roomkit/core-sdk/vue/device-state.md

@@ -74,9 +74,6 @@ watch(currentCamera, (camera) => {
 });
 ```
 
-> **Note:**
->
-
 > When you call [setCurrentCamera](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#setCurrentCamera) to switch the device, if the camera is already on, Atomicx will automatically stop capturing from the current device and restart capturing with the new device, so the video stream switches seamlessly. If switching fails, the original device will continue to be used.
 >
 
@@ -331,9 +328,6 @@ watch(outputVolume, (volume) => {
 
 Using the [networkInfo](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#networkInfo) data from [useDeviceState](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#module-DeviceState), you can monitor the local user's network quality in real time.
 
-> **Note:**
->
-
 > Valid data can only be obtained from [networkInfo](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#networkInfo) when the local user has joined a room via [joinRoom](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#joinRoom) and turned on the microphone or camera.
 >
 

package/resource/knowledge/roomkit/core-sdk/vue/free-beauty-panel.md

@@ -37,9 +37,6 @@ It is generally recommended to place `FreeBeautyPanel` inside a Dialog or Modal,
 
 **The following example shows how to implement a complete interaction where clicking a button opens the beauty settings:**
 
-> **Note:**
->
-
 > All TUIKit components must be wrapped inside UIKitProvider; otherwise, they will not be able to obtain their context dependencies, resulting in abnormal styling.
 >
 
@@ -117,9 +114,6 @@ This section mainly describes how to implement basic beauty via the atomicx-core
 
 When the user adjusts the beauty parameters (for example, by dragging a slider), use [setFreeBeauty](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#setFreeBeauty) for real-time preview. At this point, the effect is only visible locally and will not be transmitted to remote users.
 
-> **Note:**
->
-
 > The value range of the parameters is 0-100.
 >
 
@@ -143,9 +137,6 @@ const updatePreview = async (beauty: number, white: number, ruddy: number) => {
 
 After the user confirms that they are satisfied with the preview, call [saveBeautySetting](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#saveBeautySetting) to apply the current configuration to the video stream. At this point, remote users can see the beauty effect.
 
-> **Note:**
->
-
 > The beauty feature depends on a camera device. You can use [useDeviceState](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#module-DeviceState) to check the device status.
 >
 > - [cameraList](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#cameraList): The list of currently available camera devices. If the list is empty, it means no camera was detected or camera permission is denied.

package/resource/knowledge/roomkit/core-sdk/vue/room-chat.md

@@ -35,7 +35,6 @@ This feature offers two integration approaches, and you can choose the one that
 After the user successfully joins the room, you need to call the [setActiveConversation](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#setActiveConversation) API to initialize the chat data. We recommend listening for changes to [currentRoom](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#currentRoom) to handle this automatically.
 
 > **Note:**
->
 > - `GROUP` is a fixed prefix. The `setActiveConversation` argument must be ``GROUP${roomId}``; otherwise, messages cannot be sent or received properly.
 > - `GROUP` is the fixed prefix for IM SDK group conversations (see [IM conversation types](https://web.sdk.qcloud.com/im/doc/zh-cn/Conversation.html)). Room chat is built on IM groups, so the conversation ID must be in the ``GROUP${roomId}`` format.
 
@@ -60,9 +59,6 @@ watch(() => currentRoom.value?.roomId, (roomId) => {
 
 In your page, you can directly combine these two components. At the same time, use [useRoomParticipantState](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#module-RoomParticipantState) to obtain the current user's mute status and control the availability of the input box.
 
-> **Caution:**
->
-
 > All TUIKit components must be wrapped inside UIKitProvider; otherwise, they cannot obtain their context dependencies, resulting in abnormal styles.
 >
 
@@ -144,9 +140,6 @@ const openChatWindow = () => {
 
 This section mainly explains how to implement a custom chat interface using the atomicx-core SDK APIs [useMessageListState](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#module-MessageListState) and [useMessageInputState](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#module-MessageInputState).
 
-> **Caution:**
->
-
 > `MessageInputState` supports integration with the `@tiptap/vue-3` editor by default. If you only need a simple text input (such as `<input>` or `<textarea>`), please **ignore** the editor-instance-bound APIs such as `setEditorInstance` and `setContent`, and simply use `updateRawValue` and `sendMessage`.
 >
 
@@ -155,7 +148,6 @@ This section mainly explains how to implement a custom chat interface using the
 After the user successfully joins the room, you need to call the [setActiveConversation](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#setActiveConversation) API to initialize the chat data. We recommend listening for changes to [currentRoom](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#currentRoom) to handle this automatically.
 
 > **Note:**
->
 > - `GROUP` is a fixed prefix. The `setActiveConversation` argument must be ``GROUP${roomId}``; otherwise, messages cannot be sent or received properly.
 > - When switching rooms or leaving a room, we recommend resetting or clearing the active conversation to avoid sending messages to the wrong conversation.
 
@@ -241,9 +233,6 @@ const handleSend = async () => {
 
 Use the [loadMoreOlderMessage](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#module-MessageListState) method to fetch historical messages page by page. This is usually triggered when scrolling to the top of the list.
 
-> **Caution:**
->
-
 > After loading historical messages, you usually need to manually adjust the scrollbar position to keep the current viewport from jumping.
 >
 

package/resource/knowledge/roomkit/core-sdk/vue/room-participant-state.md

@@ -81,7 +81,6 @@ const { participantList } = useRoomParticipantState();
 ```
 
 > **Note:**
->
 > - `RoomParticipantList` automatically fills the height and width of its parent container, so make sure its parent container has explicit dimensions.
 > - When using the `RoomParticipantList` component, make sure to configure the global `UIKitProvider` in `App.vue`. For details, refer to [Configuring App.vue](https://cloud.tencent.com/document/product/647/81962#ce98ee15-b0cb-43af-81da-70f51231430e).
 
@@ -111,9 +110,6 @@ const handleLoadMore = async () => {
 };
 ```
 
-> **Note:**
->
-
 > The data successfully fetched by the `getParticipantList` interface is automatically maintained in `participantList`. The UI only needs to render the data in `participantList`.
 >
 
@@ -355,7 +351,7 @@ await kickParticipant({ userId });
 
 ### Step 9: Invite others to join the room
 
-In actual business scenarios, you may need to send a call invitation to users who have not yet entered the room. Atomicx provides full support for a calling system. For details, refer to In-Meeting Calling.
+In actual business scenarios, you may need to send a call invitation to users who have not yet entered the room. Atomicx provides full support for a calling system. .
 
 ## API Documentation
 

package/resource/knowledge/roomkit/core-sdk/vue/room-state.md

@@ -32,9 +32,6 @@ const {
 
 Create a room (room owner): Use [createAndJoinRoom](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#createAndJoinRoom). After a successful call, the user automatically gains room owner permissions.
 
-> **Note:**
->
-
 > It is recommended that the roomId specified when creating a room be generated and delivered by the business backend, to ensure the uniqueness and stability of the room ID across the entire application globally.
 >
 
@@ -148,9 +145,6 @@ await updateRoomInfo({
 })
 ```
 
-> **Note:**
->
-
 > The room owner must be inside the room to call [updateRoomInfo](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#updateRoomInfo). If the room owner has already left the room, they need to rejoin before they can update the room information.
 >
 
@@ -175,7 +169,6 @@ await endRoom();
 ```
 
 > **Note:**
->
 > - If the room owner leaves the room but does not call [endRoom](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#endRoom), the room will continue to exist until the automatic reclamation condition is met (no users for 6 consecutive hours).
 > - The room owner can transfer the room owner identity to another user via the [transferOwner](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#transferOwner) interface.
 
@@ -261,7 +254,7 @@ Atomicx provides complete scheduled room capabilities, including:
 
 - **Join reminders:** Support automatic reminder logic before the start.
 
-   If you need to implement the more complex business logic for managing multi-person audio/video rooms described above, please refer to: Schedule Room.
+ If you need to implement the more complex business logic for managing multi-person audio/video rooms described above, please .
 
 ## FAQ
 

package/resource/knowledge/roomkit/core-sdk/vue/room-view.md

@@ -52,9 +52,6 @@ import { RoomView } from 'tuikit-atomicx-vue3/room';
 </style>
 ```
 
-> **Note:**
->
-
 > `RoomView` automatically fills the height and width of its parent container, so make sure its parent container has explicit dimensions.
 >
 

package/resource/knowledge/roomkit/core-sdk/vue/screen-share.md

@@ -60,9 +60,6 @@ const handleStartScreenShareWithAudio = async () => {
 |Firefox|Not supported|System audio sharing is not yet supported|
 |Safari|Not supported|System audio sharing is not yet supported|
 
-> **Note:**
->
-
 > System audio sharing requires browser support, and the user must check the **Share audio** option in the screen picker. If the browser does not support system audio sharing, the `screenAudio` parameter is ignored, but the screen sharing feature is not affected and works normally.
 >
 

package/resource/knowledge/roomkit/core-sdk/vue/virtual-background.md

@@ -50,7 +50,6 @@ It is generally recommended to place the [VirtualBackgroundPanel](https://github
 **The following example shows how to implement a complete interaction where clicking a button opens the virtual background settings:**
 
 > **Note:**
->
 > - Publish the `node_modules/trtc-sdk-v5/assets` directory to a CDN or static resource server. For details, see the [SDK documentation](https://web.sdk.qcloud.com/trtc/webrtc/doc/zh-cn/tutorial-36-advanced-virtual-background.html).
 > - When using the [VirtualBackgroundPanel](https://github.com/Tencent-RTC/TUIKit_Vue3/tree/main/packages/tuikit-atomicx-vue3/src/components/VirtualBackgroundPanel) component, pass the `assetsPath` static resource address via props.
 > - All TUIKit components must be wrapped inside UIKitProvider; otherwise, they will not be able to obtain their context dependencies, resulting in abnormal styling.
@@ -122,7 +121,6 @@ This section mainly describes how to implement the virtual background via the at
 Before invoking the virtual background feature, you must first check whether the browser supports it and initialize the resource path.
 
 > **Note:**
->
 > - Publish the node_modules/trtc-sdk-v5/assets directory to a CDN or static resource server. For details, see the [SDK documentation](https://web.sdk.qcloud.com/trtc/webrtc/doc/zh-cn/tutorial-36-advanced-virtual-background.html).
 > - When using the [initVirtualBackground](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#initVirtualBackground) interface, pass the assetsPath static resource address.
 > - The virtual background feature depends on a camera device. You can use [useDeviceState](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#module-DeviceState) to check the device status.
@@ -155,9 +153,6 @@ onMounted(async () => {
 
 Before the user confirms applying the background, you usually need to preview the effect first. Use the [setVirtualBackground](https://web.sdk.qcloud.com/trtc/live/web/doc/en/index.html#setVirtualBackground) method to set the preview effect. At this point, it is not applied to the video stream visible to remote users.
 
-> **Note:**
->
-
 > Calling `setVirtualBackground` only takes effect in the local preview. Remote users will not see the virtual background effect; it is synchronized to the remote video stream only after `saveVirtualBackground` is called.
 >
 

package/resource/knowledge/roomkit/preset/android/integration.md

@@ -1,9 +1,6 @@
 TUIRoomKit is a comprehensive multi-party audio and video conferencing solution built on TRTC. It provides a complete set of UI components along with all the core functionality you need to get up and running quickly.
 
 This documentation walks you through integrating TUIRoomKit into your project to enable reliable multi-party audio/video conferencing. You'll also find step-by-step guides for customizing image assets, localizing UI text, and configuring other options—everything you need to build audio/video experiences that align with your brand.
-| Room Preparation Page | Room Main Page | Member Management |
-| --- | --- | --- |
-|  |  |  |
 
 ## Prerequisites
 
@@ -95,7 +92,6 @@ After completing the above steps, Android Studio will usually prompt you to **Sy
 After integrating the code, complete the login process. This step is **required to use TUIRoomKit features**—you must log in successfully before accessing any functionality. Verify that all parameters are set correctly:
 
 > **Note:**
->
 > The sample code calls the login API directly. In production scenarios, always call AtomicXCore's login service **after** completing your own user authentication and login workflow. This ensures correct business logic flow, prevents data inconsistencies, and integrates seamlessly with your user management and permission systems.
 >
 

package/resource/knowledge/roomkit/preset/flutter/integration.md

@@ -1,7 +1,4 @@
 TUIRoomKit is a comprehensive multi-party audio and video conferencing solution powered by TRTC. It provides a full suite of UI components and essential features out of the box. This guide walks developers through integrating TUIRoomKit into their projects to enable robust multi-party audio and video conferencing. It also covers how to quickly customize image assets, localize UI text, and configure other settings, empowering you to build branded audio and video applications.
-| Room Preparation Page | Standard Room Home | Large Webinar Room Home | Member Management |
-| --- | --- | --- | --- |
-|  |  |  |  |
 
 ## Prerequisites
 
@@ -111,7 +108,6 @@ To enable proper page navigation and multilingual UI, update your Flutter app as
 After integration, complete the login process—a **critical step for using TUIRoomKit**. You must log in successfully before accessing TUIRoomKit features. Ensure all parameters are configured correctly:
 
 > **Note:**
->
 > The sample code calls the login interface directly. In production, always call TUIRoomKit's login service **after your own user authentication and login logic**. This prevents business logic confusion and data inconsistencies, and ensures seamless integration with your user management and permission system.
 >
 
@@ -233,7 +229,7 @@ class YourMainPage extends StatelessWidget {
 | Parameter | Type | Description |
 | --- | --- | --- |
 | <code>roomID</code> | <code>String</code> | - Unique Room Identifier.<br>- Length: 0-48 bytes.<br>- Use only numbers, English letters (case-sensitive), underscores (_), and hyphens (-). Avoid spaces and Chinese characters. |
-| <code>behavior</code> | <code>RoomBehavior</code> | - Main Room Page initialization source.<br>- Parameter options:<br>- create: Host creates the room (requires Room Creation Options). For detailed usage of CreateRoomOptions, please refer to: CreateRoomOptions Structure Specifications.<br>- enter: Participant joins the room. |
+| <code>behavior</code> | <code>RoomBehavior</code> | - Main Room Page initialization source.<br>- Parameter options:<br>- create: Host creates the room (requires Room Creation Options). For detailed usage of CreateRoomOptions, please .<br>- enter: Participant joins the room. |
 | <code>config</code> | <code>ConnectConfig</code> | Controls audio/video device behavior after entering the room. |
 
 **ConnectConfig Parameter Descriptions:**
@@ -313,21 +309,16 @@ class YourMainPage extends StatelessWidget {
 **For detailed parameter descriptions, see:** RoomMainWidget Constructor Parameter Descriptions and ConnectConfig Parameter Descriptions.
 
 > **Note:**
->
 > When joining a large webinar room using TUIRoomKit, ensure the room ID created on the web starts with `webinar_`.
 >
 
 ## Core Features
 
 Once `RoomMainWidget` is integrated, you get a full-featured multi-party audio and video conferencing interface, including member management, device control, room information display, and more. This is the core of the TUIRoomKit component.
-| Standard Room | Large Webinar Room |
-| --- | --- |
-|  |  |
 
 ## UI Customization
 
 > **Note:**
->
 > UI customization, icon customization, and text customization require modifying TUIRoomKit source code. When integrated via the pub Dependency Manager, TUIRoomKit is treated as an immutable dependency. Each time you run flutter pub get, Flutter:
 >
 > 1. Checks the version in pubspec.lock.
@@ -349,9 +340,6 @@ Once `RoomMainWidget` is integrated, you get a full-featured multi-party audio a
 > `      path: room`
 
 The `RoomMainWidget` main room page is highly customizable and feature-rich. Developers can adapt the UI to fit their business requirements. Below are the main view components in `RoomMainWidget` for quick modification.
-| Standard Room | Large Webinar Room |
-| --- | --- |
-|  |  |
 
 **RoomMainWidget Component Details**
 

package/resource/knowledge/roomkit/preset/ios/integration.md

@@ -1,9 +1,6 @@
 TUIRoomKit is a comprehensive multi-party audio and video conferencing solution built on TRTC. It provides a complete set of UI components along with all the core functionality you need to get up and running quickly.
 
 This documentation walks you through integrating TUIRoomKit into your project to enable reliable multi-party audio/video conferencing. You'll also find step-by-step guides for customizing image assets, localizing UI text, and configuring other options—everything you need to build audio/video experiences that align with your brand.
-| Room Preparation Page | Room Main Page | Member Management |
-| --- | --- | --- |
-|  |  |  |
 
 ## Prerequisites
 
@@ -88,7 +85,6 @@ To enable audio/video features, your app must request microphone and camera perm
 After integrating the code, complete the login process. **This step is required to use TUIRoomKit.** You must log in successfully before accessing any features. Verify that all parameters are correctly configured:
 
 > **Note:**
->
 > In the sample code, login is handled in the `didFinishLaunchingWithOptions` method. In real-world projects, **call the AtomicXCore login service only after your own user authentication and login procedures have completed**. This prevents business logic conflicts and ensures seamless integration with your user management and permission systems.
 >
 
@@ -279,7 +275,6 @@ Once you've integrated `RoomMainView`, your application will offer a full-featur
 ## Customize UI
 
 > **Note:**
->
 > Customizing UI elements, icons, or text requires modifying the TUIRoomKit source code. When you integrate TUIRoomKit via CocoaPods, it acts as an immutable dependency. Each time you run `pod install`, CocoaPods will:
 >
 > - Check the version listed in Podfile.lock.
@@ -329,7 +324,6 @@ TUIRoomKit manages UI image resources in `TUIRoomKit.xcassets`. Use Xcode's grap
 TUIRoomKit uses the [Apple Strings Catalog](https://developer.apple.com/documentation/xcode/localizing-and-varying-text-with-a-string-catalog) tool to manage UI text. You can easily adjust text using Xcode's visual tools.
 
 > **Note:**
->
 > The Apple Strings Catalog (.xcstrings) format, introduced in Xcode 15, streamlines localization management. It supports structured formats for plurals, device-specific variants, and more, and is now the recommended localization approach for iOS and macOS apps.
 >
 

package/resource/knowledge/roomkit/preset/react/integration.md

@@ -60,7 +60,6 @@ export default function App() {
 Authentication is required to access all TUIRoomKit features. Call **conference.login** immediately after your business system completes authentication (when the user logs in to your web page). After calling `conference.login`, call `conference.setSelfInfo` to set the user's display name and avatar, which appear in the participant video area and member list.
 
 > **Note:**
->
 > Make sure to use the generated UserSig in your configuration. In production, generate UserSig on your server and have the client request a dynamic UserSig from your business server as needed. See [How to Calculate UserSig in Production](https://trtc.io/document/35166).
 >
 
@@ -305,7 +304,6 @@ const enterDualMeeting = async (bizOrderId: string) => {
 ```
 
 > **Tip:**
->
 > The `conference.createAndJoinRoom` API automatically handles "create if not exists (become Host), join if exists (become Participant)", resolving state conflicts under high concurrency.
 >
 
@@ -325,7 +323,6 @@ await conference.leaveRoom();
 ```
 
 > **Note:**
->
 > When the Host leaves or closes the webpage, the room is not automatically ended. Other Participants can continue using TUIRoomKit. The system will reclaim room resources 6 hours after the scheduled end time if there are zero Participants.
 >
 
@@ -339,7 +336,6 @@ await conference.endRoom();
 ```
 
 > **Note:**
->
 > Only the Host can call `endRoom()` after successfully entering the room. Calling as a non-host or before entering will result in an error.
 >
 
@@ -404,8 +400,6 @@ pnpm run dev
 yarn run dev
 ```
 
-After the project starts, open your browser to the debug address (usually http://localhost:5173) to access the app. You should see the meeting interface as shown below:
-
 ## Next Steps
 
 After completing the basic integration, you can further customize the UI to fit your business requirements.
@@ -498,17 +492,13 @@ No. TUIRoomKit does not allow the same userId to join the same room on multiple
 
 ### Is iframe integration supported?
 
-Yes. When integrating TUIRoomKit via iframe, set the allow attribute to grant necessary browser permissions (microphone, camera, screen sharing, fullscreen, etc.) as shown below:
 ``` typescript
 // Enable microphone, camera, screen sharing, fullscreen permissions
 <iframe src="https://your-domain.com/index.html" allow="microphone; camera; display-capture; display; fullscreen;">
 ```
 
-For more information, see Embedded Pages (iframe).
-
 ### Is intranet proxy supported?
 
-Yes. Set intranet proxy parameters as shown below. For more details, see [Dealing with Firewall Restrictions](https://trtc.io/document/59667).
 ``` typescript
 // Set intranet proxy parameters before entering the room
 import TUIRoomEngine from '@tencentcloud/tuiroom-engine-js';
@@ -540,8 +530,6 @@ TUIRoomKit offers rich customization out of the box—custom themes and language
 We strongly discourage exporting the source code. Doing so removes your project from TUIRoomKit's standard npm upgrade path, increases maintenance costs, and prevents you from benefiting from new features and performance improvements in the underlying audio/video engine.
 - Recommended: Explore standard customization options in the UI customization documentation.
 
-- Feedback: If the available APIs do not meet your needs, contact us via [Contact Us](https://trtc.io/contact) to submit your requirements. We will evaluate and strive to provide stable, standardized API support.
-
    If you have fully considered the maintenance risks and require deep customization, you may export the source code as follows:
 
 【React】
@@ -566,7 +554,3 @@ import { ConferenceMainView, conference } from './components/RoomKit/index.ts';
 // Replace with the actual TUIRoomKit source path
 src/components/RoomKit
 ```
-
-## Contact Us
-
-If you have any questions or suggestions during integration or usage, you are welcome to join our [Telegram technical group](https://t.me/+EPk6TMZEZMM5OGY1) or [contact us](https://trtc.io/contact) for support.