@tencent-rtc/mcp 1.6.3 → 1.6.5

package/resource/knowledge/roomkit/core-sdk/ios/unsupported-features.md

@@ -0,0 +1,79 @@
+# AtomicX Core iOS unsupported features
+
+This document summarizes features currently **unsupported** in `knowledge/roomkit/core-sdk/ios/`.
+
+## Usage policy
+
+- If this document is retrieved, the answer should focus on **capability boundary**, not implementation steps.
+- For alternatives, only reference capabilities that are already documented for iOS.
+
+## In-room chat / Room Chat / In-room IM Chat
+
+**Unsupported.** iOS Core currently has no `room-chat.md`.
+
+- Do not reuse `MessageList`, `MessageInput`, `MessageStore`, or conversation bootstrap flow from other platforms.
+- Do not treat preset `RoomMainView` capability as iOS Core atomic capability.
+
+**Alternative path**:
+1. Build chat UI and message flow with Chat / IM iOS SDK.
+2. See `knowledge/chat/urls/sdk/ios.md` for iOS message API entries.
+
+## Screen share / Screen Sharing
+
+**Unsupported.** iOS Core currently has no `screen-share.md`.
+
+- Do not provide iOS Core `startScreenShare`-style steps.
+- Do not reuse screen-share flow from other platforms.
+
+**Alternative path**:
+1. Prefer preset room main page solution.
+2. No documented iOS Core atomic alternative currently.
+
+## Virtual background
+
+**Unsupported.** iOS Core currently has no `virtual-background.md`.
+
+- Do not output iOS Core virtual-background initialization / resource-path / state-management steps.
+- Do not reuse panel hooks from other platforms.
+
+**Alternative path**:
+1. Prefer preset UI path.
+2. No iOS Core atomic integration path currently.
+
+## Room main view / video layout
+
+**Unsupported.** iOS Core currently has no `room-view.md`.
+
+- Do not output iOS Core `RoomView` component, layout template, or widget-slot steps.
+- Do not treat `RoomMainView` preset page as `RoomView` atomic capability.
+
+**Alternative path**:
+1. If the goal is a full meeting page, prefer `RoomMainView` preset UI.
+2. For atomic video-layout capability, no official iOS Core doc currently.
+
+## Device detection
+
+**Unsupported.** iOS Core currently has no `device-detection.md`.
+
+- Do not output iOS Core pre-join camera/mic/speaker test steps.
+- Do not map test APIs from other platforms to iOS Core.
+
+**Alternative path**: no documented iOS Core solution currently.
+
+## Device state management
+
+**Unsupported.** iOS Core currently has no `device-state.md`.
+
+- Do not output iOS Core device-list switching, volume detection, mirror switching, or network panel steps.
+- Do not treat device-state logic from other platforms as iOS Core capability.
+
+**Alternative path**: no documented iOS Core solution currently.
+
+## Basic beauty panel
+
+**Unsupported.** iOS Core currently has no `free-beauty-panel.md`.
+
+- Do not output iOS Core beauty-panel UI / parameter steps.
+- Do not directly reuse beauty interaction from other platforms.
+
+**Alternative path**: no documented iOS Core solution currently.

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

@@ -52,11 +52,10 @@ dependencies {
 }
 ```
 
-> **Note****:**
->
-
-> TUIRoomKit includes dependencies on TRTC SDK, IM SDK, and other common libraries by default. You do not need to configure these separately.
->
+   > **Note****:**
+   >
+   > TUIRoomKit includes dependencies on TRTC SDK, IM SDK, and other common libraries by default. You do not need to configure these separately.
+   >
 
 #### 3. Configure Proguard Rules
 
@@ -76,7 +75,7 @@ Because the SDK uses Java reflection internally, add the following to your `prog
 
 #### 4. Modify AndroidManifest.xml
 
-To prevent attribute conflicts during AndroidManifest merging at build time, add `tools:replace="android:allowBackup"` and `android:allowBackup="false"` to the `` node in your `app/src/main/AndroidManifest.xml`, overriding settings from the component.
+To prevent attribute conflicts during AndroidManifest merging at build time, add `tools:replace="android:allowBackup"` and `android:allowBackup="false"` to the ` `node in your` app/src/main/AndroidManifest.xml`, overriding settings from the component.
 ``` xml
 <manifest xmlns:android="http://schemas.android.com/apk/res/android"
     xmlns:tools="http://schemas.android.com/tools">
@@ -97,7 +96,6 @@ After integrating the code, complete the login process. This step is **required
 
 > **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

@@ -112,7 +112,6 @@ After integration, complete the login process—a **critical step for using TUIR
 
 > **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.
 >
 
@@ -177,7 +176,6 @@ Within the `TUIRoomKit` component, `RoomMainWidget` is the primary interface for
 
    > **Note:**
    >
-
    > Mobile currently supports only standard rooms. To create a large webinar room, see Web Quick Integration for web-based creation.
    >
 
@@ -312,11 +310,10 @@ class YourMainPage extends StatelessWidget {
 }
 ```
 
-**For detailed parameter descriptions, see: **RoomMainWidget Constructor Parameter Descriptions and ConnectConfig Parameter Descriptions.
+**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_`.
 >
 
@@ -331,21 +328,19 @@ Once `RoomMainWidget` is integrated, you get a full-featured multi-party audio a
 
 > **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.
 > 2. Downloads the corresponding version source code from the remote repository.
 > 3. Overwrites files in the .pub-cache/ directory with the downloaded original code.
-
 > **Any manual changes to the cache directory are temporary and will be reverted the next time you install dependencies.**
 >
-
 > **Recommended Approach:**
 >
 > 1. Fork the official [TUIKit_Flutter](https://github.com/Tencent-RTC/TUIKit_Flutter/tree/main) repository.
 > 2. Make and commit your changes in your fork.
 > 3. Update pubspec.yaml to reference your **custom repository and branch.**
+
 > `dependencies:`
 > `  tencent_conference_uikit:`
 > `    git:`

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

@@ -27,7 +27,6 @@ Before running the demo, make sure your development environment meets the follow
 
       > **Tip:**
       >
-
       > When running `sudo gem install cocoapods`, you may be prompted for your computer's password. Enter your administrator password as requested.
       >
 
@@ -90,7 +89,6 @@ After integrating the code, complete the login process. **This step is required
 
 > **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.
 >
 
@@ -164,7 +162,6 @@ func setSelfInfo() {
 
    > **Note:**
    >
-
    > TUIRoomKit's internal navigation is based on standard `UINavigationController` methods (push/pop). Ensure your view controller is either the root controller of a `UINavigationController` or part of its stack. If not, SDK navigation will fail due to the absence of a valid navigation context, resulting in page switching issues.
    >
 
@@ -283,26 +280,24 @@ Once you've integrated `RoomMainView`, your application will offer a full-featur
 
 > **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.
 > - Download the corresponding source code from the remote repository.
 > - Overwrite files in the Pods/ directory with the original source.
-
-> **Any manual modifications to the Pods/ directory will be lost the next time you run **`pod install`**.**
+> **Any manual modifications to the Pods/ directory will be lost the next time you run** `pod install`**.**
 >
-
 > **Recommended workflow:**
 >
 > - Fork the official [TUIRoomKit](https://github.com/Tencent-RTC/TUIKit_iOS) repository.
 > - Make and commit changes to your fork.
 > - Update your Podfile to reference your fork and branch:
+
 > `pod 'TUIRoomKit', :git => 'https://github.com/your-username/TUIRoomKit.git', :branch => 'your-branch'`
 
 The `RoomMainView` main page is highly customizable. You can modify the UI to fit your product requirements and interaction scenarios. The following overview details the view components within `RoomMainView` to help you make quick adjustments.
 
-**Component Overview for **`RoomMainView`
+**Component Overview for** `RoomMainView`
 
 |Component|Feature Description|Customization Suggestions|
 |---------|---------|---------|
@@ -335,7 +330,6 @@ TUIRoomKit uses the [Apple Strings Catalog](https://developer.apple.com/document
 
 > **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

@@ -61,7 +61,6 @@ Authentication is required to access all TUIRoomKit features. Call **conference.
 
 > **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).
 >
 
@@ -128,9 +127,9 @@ The **Room ID (roomId)**is the unique identifier for each meeting and must be ge
 
 #### Scenario 1: Quick Meeting Initiated by Client
 
-**Use Case: **The user clicks "Quick Meeting" and needs to immediately create and join a room (e.g., ad-hoc meetings, IM chat).
+**Use Case:** The user clicks "Quick Meeting" and needs to immediately create and join a room (e.g., ad-hoc meetings, IM chat).
 
-**Implementation: **The client generates or requests a unique Room ID from the backend, then calls `conference.createAndJoinRoom` to create and enter the room.
+**Implementation:** The client generates or requests a unique Room ID from the backend, then calls `conference.createAndJoinRoom` to create and enter the room.
 ``` typescript
 import { conference } from '@tencentcloud/roomkit-web-react';
 
@@ -150,9 +149,9 @@ const startQuickMeeting = async () => {
 
 #### Scenario 2: Schedule a Meeting
 
-**Use Case: **Meetings scheduled for a future time (e.g., weekly team meetings, online training). Users can set the Meeting Title, Meeting Time, and invite Participants.
+**Use Case:** Meetings scheduled for a future time (e.g., weekly team meetings, online training). Users can set the Meeting Title, Meeting Time, and invite Participants.
 
-**Implementation: **The client generates or requests a unique Room ID from the backend, then submits the reservation using the `scheduleRoom` API with Meeting Time and other parameters. Upon success, meeting information is synced to each Participant's Meeting List.
+**Implementation:** The client generates or requests a unique Room ID from the backend, then submits the reservation using the `scheduleRoom` API with Meeting Time and other parameters. Upon success, meeting information is synced to each Participant's Meeting List.
 ``` typescript
 import { useRoomState } from 'tuikit-atomicx-react/room';
 
@@ -188,9 +187,9 @@ function ScheduleDemo() {
 
 #### Scenario 3: Create a Room on the Server Side
 
-**Use Case: **Highly controlled environments such as government, healthcare, or enterprise OA.
+**Use Case:** Highly controlled environments such as government, healthcare, or enterprise OA.
 
-**Implementation: **The business backend initiates room creation by calling TRTC's [Server REST API to Create Room](https://trtc.io/document/60707).
+**Implementation:** The business backend initiates room creation by calling TRTC's [Server REST API to Create Room](https://trtc.io/document/60707).
 ``` bash
 POST /v4/room_engine_http_srv/create_room
 {
@@ -208,9 +207,9 @@ Choose the appropriate method for joining a room based on your business requirem
 
 #### Scenario 1: Join Existing Room with Known Room ID
 
-**Use Case: **The room has already been created, and Participants have received the Room ID or invitation link.
+**Use Case:** The room has already been created, and Participants have received the Room ID or invitation link.
 
-**Implementation: **After entering the Room ID or extracting it from the invitation link, call `conference.joinRoom` to join.
+**Implementation:** After entering the Room ID or extracting it from the invitation link, call `conference.joinRoom` to join.
 ``` typescript
 import { conference } from '@tencentcloud/roomkit-web-react';
 
@@ -223,9 +222,9 @@ const joinExistingMeeting = async (sharedRoomId: string) => {
 
 #### Scenario 2: Join from Meeting List
 
-**Use Case: **Meetings scheduled via "Client Scheduling" or "Server-Side Creation". Users can view their scheduled or invited meetings in the Meeting List and join directly.
+**Use Case:** Meetings scheduled via "Client Scheduling" or "Server-Side Creation". Users can view their scheduled or invited meetings in the Meeting List and join directly.
 
-**Implementation: **Use the `getScheduledRoomList` API from `useRoomState` to fetch the user's scheduled meetings and render them in the UI. When the user clicks a meeting, retrieve its Room ID and call `conference.joinRoom`.
+**Implementation:** Use the `getScheduledRoomList` API from `useRoomState` to fetch the user's scheduled meetings and render them in the UI. When the user clicks a meeting, retrieve its Room ID and call `conference.joinRoom`.
 ``` typescript
 import { useState, useEffect } from 'react';
 import { conference } from '@tencentcloud/roomkit-web-react';
@@ -288,9 +287,9 @@ export default function ScheduledRoomList() {
 
 #### Scenario 3: Enter Room When Existence Is Uncertain
 
-**Use Case: **Peer-to-peer scenarios (e.g., online consultation, 1v1 video customer service) where room existence is unknown.
+**Use Case:** Peer-to-peer scenarios (e.g., online consultation, 1v1 video customer service) where room existence is unknown.
 
-**Implementation: **Both parties use a shared Business Document Number (e.g., order number) as Room ID and call `conference.createAndJoinRoom` to enter.
+**Implementation:** Both parties use a shared Business Document Number (e.g., order number) as Room ID and call `conference.createAndJoinRoom` to enter.
 ``` typescript
 import { conference } from '@tencentcloud/roomkit-web-react';
 
@@ -307,7 +306,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.
 >
 
@@ -328,7 +326,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.
 >
 
@@ -343,7 +340,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.
 >