@tencent-rtc/mcp 1.4.7 → 1.6.0-beta.1

package/resource/{doc/chatkit/ios → knowledge/chat/preset/ios-uikit}/integration.md

@@ -1,65 +1,65 @@
-This article introduces how to integrate `TUIKit` components.
+TUIKit is a UI component library built on the Chat SDK. It enables rapid implementation of chat, conversation, search, relationship chain, and group management features through ready-to-use UI components. Message sending and receiving are handled by the TUIChat component. This guide explains how to quickly integrate TUIKit and implement its core features.
 
-> **Note:**
->
-> - Starting from version 5.7.1435, TUIKit supports modular integration and the classic UI. You can integrate the necessary modules according to your needs.
-> - Starting from version 6.9.3557, TUIKit introduces a brand new minimalist UI.
-> - To respect the copyright of emoji designs, the Chat Demo/TUIKit project does not include cutouts of large emoji elements. Please replace them with your own designs or other emoji packs for which you hold the copyright before officially launching for commercial use. **The default smiley face emoji pack shown below is copyrighted by Tencent RTC** and is available for licensed use for a fee. If you need to obtain a license, please [contact us](https://trtc.io/contact).
+## Key Concepts
+- **Classic UI**: Starting from version 5.7.1435, TUIKit supports modular integration and provides the Classic UI (WeChat-style).
 
->
->
+- **Minimalist UI**: Starting from version 6.9.3557, TUIKit introduces a new Minimalist UI (WhatsApp-style).
 
-You can freely choose between the classic or minimalist UI components according to your needs. If you are not familiar with the effects of the interface libraries, you can refer to the document [TUIKit Overview](https://www.tencentcloud.com/document/product/1047/50062).
+   You can select either the Classic or Minimalist UI components as needed. If you are unfamiliar with the appearance of each UI library, see [TUIKit UI Library Introduction](https://www.tencentcloud.com/zh/document/product/1047/50062).
 
-## Environment Requirements
-- Xcode 10 or later
+## Prerequisites
+- Xcode 15 or later
 
-- iOS 9.0 or later
+- iOS 14.0 or later (physical device or simulator)
 
-## CocoaPods Integration
-1. Install CocoaPods
-Enter the following command in a terminal (you need to install Ruby on your Mac first):
+- CocoaPods 1.7.5 or later. If you have not installed CocoaPods, see [CocoaPods Guides - Getting Started](https://guides.cocoapods.org/using/getting-started.html#getting-started).
 
-   ``` bash
-   sudo gem install cocoapods
-   ```
-2. Create a Podfile
-Go to the path where the project is located and run the following command. Then, a Podfile will appear under the project path.
+- A valid Tencent Cloud account and Chat application. See [Enable Service](https://www.tencentcloud.com/zh/document/product/1047/45913#.E6.93.8D.E4.BD.9C.E6.AD.A5.E9.AA.A4) to obtain the following information from the console:
+
+  - `SDKAppID`: The Chat application ID from the console, serving as your app’s unique identifier.
+
+  - `SDKSecretKey`: The application's secret key.
+
+## CocoaPods Integration
+1. Create a Podfile. Navigate to your project directory and run the following command to generate a Podfile:
 
    ``` bash
    pod init
    ```
-3. Add the corresponding TUIKit components to your Podfile according to your needs. Components are independent of each other, and adding or removing them will not affect project compilation. You can choose different Podfile integration methods as needed:
+2. Add the required TUIKit components to your Podfile based on your business needs. Components are independent; adding or removing them does not affect project compilation. TUIKit supports two integration methods:
 
   - Remote CocoaPods Integration
 
-  - Local Integration of DevelopmentPods
+  - Local Development Pods Integration
 
-      The pros and cons of the above two integration methods are shown in the following table:
+        The following table summarizes the advantages and disadvantages of each integration method:
 
-| Integration methods | Suitable Scenarios | Advantage | Disadvantage |
-| --- | --- | --- | --- |
-| Remote CocoaPods Integration | Suitable for integration without source code modifications. | When there is a version update of TUIKit, you only need to `Pod update` again to complete the update. | When you have modifications to the source code, using `Pod update` to update will overwrite your modifications with the new version of TUIKit. |
-| Local DevelopmentPods Integration | Suitable for customers who have custom modifications to the source code | When you have your own git repository, you can track changes. After modifying the source code, using `Pod update` to update other remote Pod libraries will not overwrite your modifications. | You need to manually overwrite your local TUIKit folder with the TUIKit source code to update. |
+      |Integration Method|Scenarios|Advantages|Disadvantages|
+      |---------|---------|---------|---------|
+      |Remote CocoaPods|Used when no source code modification is required.|To update TUIKit, simply run `pod update`.|If you modify the source code, running `pod update` will overwrite your changes with the latest TUIKit version.|
+      |Local Development Pods|Recommended for customizing the source code.|If you use your own git repository, you can track changes. Updating other remote Pod libraries with `pod update` will not overwrite your customizations.|You must manually update your local TUIKit folder by replacing it with the latest source code.|
 
-### Remote CocoaPods
+      Choose one of the following methods to integrate TUIKit:
 
-> **Note:**
->
+【Remote CocoaPods Integration】
 
-> Swift language component support was introduced in TUIKit version 8.5.6870.
+> **Note：**
 >
+> 3. Starting from version 8.5.6870, TUIKit supports Swift components.
+> 4. If you add only `pod 'TUIChat'` in your Podfile without specifying Classic or Minimalist UI, both UI component versions will be integrated by default.
+> 5. **Classic and Minimalist UI cannot be mixed.** When integrating multiple components, select either all Classic UI or all Minimalist UI components. For example, the Classic `TUIChat` component must be used with Classic `TUIConversation` and `TUIContact` components. Similarly, the Minimalist `TUIChat` component must be used with Minimalist `TUIConversation` and `TUIContact` components.
+> 6. If you use Swift, enable `use_modular_headers!` and use the @import module format for header imports.
 
-You can add components as needed in your Podfile:
+Add the required component libraries to your Podfile as needed:
 
-【Minimalist version】
+【Minimalist UI】
 
 【Swift】
 ``` bash
 # Uncomment the next line to define a global platform for your project
 # ...
 source 'https://github.com/CocoaPods/Specs.git'
-platform :ios, '13.0'
+platform :ios, '14.0'
 # Prevent `*.xcassets` in TUIKit from conflicting with your project
 install! 'cocoapods', :disable_input_output_paths => true
 
@@ -95,7 +95,7 @@ post_install do |installer|
             config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
             config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
             config.build_settings['ENABLE_BITCODE'] = "NO"
-            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = "13.0"
+            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = "14.0"
             #Fix Xcode15 other links  flag  -ld64
             xcode_version = `xcrun xcodebuild -version | grep Xcode | cut -d' ' -f2`.to_f
             if xcode_version >= 15
@@ -123,7 +123,7 @@ end
 # Uncomment the next line to define a global platform for your project
 # ...
 source 'https://github.com/CocoaPods/Specs.git'
-platform :ios, '13.0'
+platform :ios, '14.0'
 # Prevent `*.xcassets` in TUIKit from conflicting with your project
 install! 'cocoapods', :disable_input_output_paths => true
 
@@ -165,7 +165,7 @@ post_install do |installer|
             config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
             config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
             config.build_settings['ENABLE_BITCODE'] = "NO"
-            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = "13.0"
+            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = "14.0"
             #Fix Xcode15 other links  flag  -ld64
             xcode_version = `xcrun xcodebuild -version | grep Xcode | cut -d' ' -f2`.to_f
             if xcode_version >= 15
@@ -188,13 +188,13 @@ post_install do |installer|
 end
 ```
 
-【Classic version】
+【Classic UI】
 
 【Swift】
 ``` bash
 # Uncomment the next line to define a global platform for your project
 source 'https://github.com/CocoaPods/Specs.git'
-platform :ios, '13.0'
+platform :ios, '14.0'
 # Prevent `*.xcassets` in TUIKit from conflicting with your project
 install! 'cocoapods', :disable_input_output_paths => true
 
@@ -240,7 +240,7 @@ post_install do |installer|
             config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
             config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
             config.build_settings['ENABLE_BITCODE'] = "NO"
-            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = "13.0"
+            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = "14.0"
             #Fix Xcode15 other links  flag  -ld64
             xcode_version = `xcrun xcodebuild -version | grep Xcode | cut -d' ' -f2`.to_f
             if xcode_version >= 15
@@ -267,7 +267,7 @@ end
 ``` bash
 # Uncomment the next line to define a global platform for your project
 source 'https://github.com/CocoaPods/Specs.git'
-platform :ios, '13.0'
+platform :ios, '14.0'
 # Prevent `*.xcassets` in TUIKit from conflicting with your project
 install! 'cocoapods', :disable_input_output_paths => true
 
@@ -318,7 +318,7 @@ post_install do |installer|
             config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
             config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
             config.build_settings['ENABLE_BITCODE'] = "NO"
-            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = "13.0"
+            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = "14.0"
             #Fix Xcode15 other links  flag  -ld64
             xcode_version = `xcrun xcodebuild -version | grep Xcode | cut -d' ' -f2`.to_f
             if xcode_version >= 15
@@ -341,59 +341,43 @@ post_install do |installer|
 end
 ```
 
-> **Indication**
->
-> 1. If you directly use `pod 'TUIChat'` without specifying classic or minimalist, it will integrate both UI component versions by default.
-> 2. The Classic and Minimalist UI cannot be mixed. When integrating multiple components, you must choose classic UI or minimalist UI at the same time. For instance, the Classic TUIChat component must be used with the Classic versions of the TUIConversation, TUIContact, and TUIGroup. Similarly, the Minimalist version of the TUIChat component must be paired with the Minimalist versions of the TUIConversation, TUIContact.
-> 3. If you are using Swift, please enable `use_modular_headers!`, and change the header file reference to @import reference.
-
-After modifying the Podfile, run the following command to install TUIKit.
+After updating your Podfile, run the following command to install the TUIKit components:
 ``` bash
 pod install
 ```
 
-If you cannot install the latest version of TUIKit, run the following command to update the local CocoaPods repository.
-``` bash
-pod repo update
-```
-
-Then run the following command to update the Pod version of the component.
-``` bash
-pod update
-```
-
-After all TUIKit components are integrated, the project structure is as follows:
-
-> **Note:**
+> **Note：**
 >
+> 7. If you cannot install the latest version of TUIKit, run `pod repo update` to update your local CocoaPods repository, then run `pod update` to update the component library version.
+> 8. If you encounter third-party library version conflicts, see CocoaPods FAQs - Dependency Version Conflicts.
 
-> If you encounter any errors in the process, you can refer to the FAQs at the end of the document.
->
+After successfully integrating all TUIKit components, your project directory should resemble the following:
 
-### Local DevelopmentPods
-1. Download TUIKit source code from GitHub. Drag it directly into your project directory:
+【Local DevelopmentPods Integration】
+1. Download the TUIKit source code from GitHub and add the TUIKit directory directly to your project directory:
 
-  1. [Swift TUIKit in Github](https://github.com/Tencent-RTC/Chat_UIKit/tree/main/Swift/TUIKit):
+- [Swift TUIKit Source Code GitHub](https://github.com/Tencent-RTC/Chat_UIKit/tree/main/Swift/TUIKit):
 
-  2. [Objective-C TUIKit in Github](https://github.com/TencentCloud/chat-uikit-ios/tree/main/TUIKit):
+- [Objective-C TUIKit Source Code GitHub](https://github.com/TencentCloud/chat-uikit-ios/tree/main/TUIKit):
 
-2. Modify the local path of each component in your Podfile. The path is the location of the TUIKit folder relative to your project's Podfile, commonly including:
+2. Specify the local path for each component in your Podfile. The `:path` parameter value depends on the TUIKit folder’s location relative to the Podfile:
 
-  - The TUIKit folder is located in the **parent directory** of your project's Podfile: `pod 'TUICore', :path => "../TUIKit/TUICore"`
+Common path configurations:
+- TUIKit is in the **parent directory** of the Podfile: `pod 'TUICore', :path => "../TUIKit/TUICore"`
 
-  - The TUIKit folder is located in the **current directory** of your project's Podfile: `pod 'TUICore', :path => "./TUIKit/TUICore"`
+- TUIKit is in the **current directory** of the Podfile: `pod 'TUICore', :path => "./TUIKit/TUICore"`
 
-  - The TUIKit folder is located in the **subdirectory** of your project's Podfile: ` pod 'TUICore', :path => "/TUIKit/TUICore"`
+- TUIKit is in a **subdirectory** of the Podfile: `pod 'TUICore', :path => "TUIKit/TUICore"`
 
-      Taking the TUIKit folder located in the parent directory of your project's Podfile as an example:
+ The following Podfile path configuration assumes the TUIKit folder is in the parent directory of the Podfile:
 
 【DevelopmentPodfile】
 
 【Swift】
 ``` bash
-ment# Uncomment the next line to define a global platform for your project
+# Uncomment the next line to define a global platform for your project
 source 'https://github.com/CocoaPods/Specs.git'
-platform :ios, '13.0'
+platform :ios, '14.0'
 install! 'cocoapods', :disable_input_output_paths => true
 
 # Replace `your_project_name` with your actual project name
@@ -435,7 +419,7 @@ post_install do |installer|
             config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
             config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
             config.build_settings['ENABLE_BITCODE'] = "NO"
-            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = "13.0"
+            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = "14.0"
             #Fix Xcode15 other links  flag  -ld64
             xcode_version = `xcrun xcodebuild -version | grep Xcode | cut -d' ' -f2`.to_f
             if xcode_version >= 15
@@ -460,9 +444,9 @@ end
 
 【Objective-C】
 ``` bash
-ment# Uncomment the next line to define a global platform for your project
+# Uncomment the next line to define a global platform for your project
 source 'https://github.com/CocoaPods/Specs.git'
-platform :ios, '13.0'
+platform :ios, '14.0'
 install! 'cocoapods', :disable_input_output_paths => true
 
 # Replace `your_project_name` with your actual project name
@@ -519,7 +503,7 @@ post_install do |installer|
             config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
             config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
             config.build_settings['ENABLE_BITCODE'] = "NO"
-            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = "13.0"
+            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = "14.0"
             #Fix Xcode15 other links  flag  -ld64
             xcode_version = `xcrun xcodebuild -version | grep Xcode | cut -d' ' -f2`.to_f
             if xcode_version >= 15
@@ -541,85 +525,57 @@ post_install do |installer|
     end
 end
 ```
+3. After updating your Podfile, run the following command to install the TUIKit components:
 
-3. After modifying the Podfile, run the following command to install the local TUIKit components. Example:
-
-   ``` bash
-   pod install
-   ```
-
-   > **Note:**
-   >
->   4. When using the local integration solution, if you need to upgrade, you must obtain the latest souce code from Github and overwrite the TUIKit directory in your local project.
->   5. When private modifications conflict with the remote version, manual merging is required to resolve conflicts.
->   6. The TUIKit plugin relies on the version of TUICore, so please ensure that the plugin version matches the spec.version in "../TUIKit/TUICore/TUICore.spec".
-
-## Third-party Library Dependencies
-
-The minimum version requirements for third-party libraries depended on by TUIKit are as follows. If your version is lower, please upgrade to the latest version.
-
-【Swift】
-``` plaintext
-- MJExtension (3.4.1)
-- MJRefresh (3.7.5)
-- SnapKit (5.7.1)
-- SSZipArchive (2.4.3)
-- SDWebImage (5.18.11)
-```
-
-【Objective-C】
-``` plaintext
-- Masonry (1.1.0)
-- MJExtension (3.4.1)
-- MJRefresh (3.7.5)
-- ReactiveObjC (3.1.1)
-- SDWebImage (5.18.11):
-  - SDWebImage/Core (= 5.18.11)
-- SDWebImage/Core (5.18.11)
-- SnapKit (5.6.0)
-- SSZipArchive (2.4.3)
+``` bash
+pod install
 ```
 
-## Build Basic Interfaces
+> **Notes：**
+>
+> 4. When using local integration, you must obtain the latest component code from GitHub and overwrite your local TUIKit directory when upgrading.
+> 5. If you have private modifications that conflict with the remote repository, manually merge and resolve conflicts.
+> 6. TUIKit plugins depend on the TUICore version. Ensure the plugin version matches the `spec.version` in `../TUIKit/TUICore/TUICore.spec`.
+> 7. If you encounter third-party library version conflicts, see CocoaPods FAQs - Dependency Version Conflicts.
 
-After integrating TUIKit, if you want to continue building basic interfaces for chat, conversation list, etc., please refer to the document: [Build Chat](https://www.tencentcloud.com/document/product/1047/61215), [Build Conversation List.](https://www.tencentcloud.com/document/product/1047/61217)
+      Now you have successfully integrated TUIKit into your project. To continue building basic interfaces such as chat and conversation, see [Build Chat Interface](https://www.tencentcloud.com/zh/document/product/1047/61215) and [Build Conversation List.](https://www.tencentcloud.com/zh/document/product/1047/61217)
 
 ## FAQs
 
-### Xcode Issues
-- **Integration error: [Xcodeproj] Unknown object version (60). (RuntimeError)**
+### Xcode
+- **Integration Error: [Xcodeproj] Unknown object version (60). (RuntimeError)**
 
-   When integrating TUIKit in a new project created with Xcode15 and entering `pod install`, you may encounter this issue due to using an older version of CocoaPods. There are two solutions:
+   When creating a new project with Xcode 15 and integrating TUIKit, this error may occur after running `pod install`. It is caused by an outdated version of CocoaPods. There are two solutions:
 
-   Solution 1: Change the Xcode project's `Project Format` version to Xcode13.0.
+   **Solution 1**: Change your Xcode project’s `Project Format` version to Xcode 13.0.
 
-   Solution 2: Upgrade your local version of CocoaPods. The upgrade method will not be elaborated here.
+   ** Solution 2**: Upgrade your local version of CocoaPods. (Upgrade steps not detailed here.)
 
 - **Assertion failed: (false && "compact unwind compressed function offset doesn't fit in 24 bits"), function operator(), file Layout.cpp.**
 
-   Or, when integrating TUIRoom with XCode15, the latest linker causes symbol conflicts in TUIRoomEngine, which is also part of this issue.
+   Alternatively, when integrating TUIRoom with Xcode 15, you may encounter symbol conflicts in TUIRoomEngine caused by the latest linker. Both issues have the same root cause.
 
-   Solution: Modify the linker configuration. In `Build Settings`, add `-ld64` to `Other Linker Flags`.
+   **Solution**: Update the linker configuration. Add `-ld64` to `Other Linker Flags` in Build Settings.
 
-   Official Documentation: [https://developer.apple.com/forums/thread/735426](https://links.jianshu.com/go?to=https%3A%2F%2Fdeveloper.apple.com%2Fforums%2Fthread%2F735426)
+    Official document: [https://developer.apple.com/forums/thread/735426](https://links.jianshu.com/go)
 
 - **Rosetta Simulator Issue**
 
-   When using Apple Silicon (M1, M2, etc. series chips), you'll encounter this type of popup. The reason is that some third-party libraries, including SDWebImage, do not support xcframework. However, Apple has still provided an adaptation method, which is to enable Rosetta settings on the emulator. Generally, the Rosetta option will automatically pop up during compilation.
+   On Apple Silicon chips (M1/M2 series), you may see a popup due to some third-party libraries (such as SDWebImage) not supporting XCFramework. Apple provides a workaround: enable Rosetta on the simulator. The Rosetta option usually appears automatically during compilation.
 
 - **Xcode 15 Developer Sandbox Option Error: Sandbox: bash(xxx) deny(1) file-write-create**
 
-   When you create a new project using Xcode 15, this option may cause compilation and execution failure. It is recommended that you turn off this option.
+    When creating a new project with Xcode 15, enabling this option may cause build and run failures. We recommend disabling this option.
 
-- **Xcode 16 does not support enabling bitcode for Frameworks**
+- **Xcode 16 Does Not Support Framework Bitcode**
 
-   **Solution 1: Upgrade the SDK**
+   **Solution 1: Upgrade SDK**
 
-   If you are using an old version SDK with Bitcode (e.g., TXIMSDK_iOS), it is recommended to follow this document and upgrade the SDK to TXIMSDK_Plus_iOS_XCFramework.
+   If you are using an older SDK version that includes Bitcode (such as TXIMSDK_iOS), upgrade to TXIMSDK_Plus_iOS_XCFramework as described in this documentation.
 
-   **Solution 2: Modify the Podfile**
+   **Solution 2: Modify Podfile Configuration**
 
-   Add the following configuration to the end of your Podfile and run pod install again.
+   Add the following configuration to the end of your Podfile and run `pod install` again.
 
    ``` java
    post_install do |installer|
@@ -639,31 +595,71 @@ After integrating TUIKit, if you want to continue building basic interfaces for
    end
    ```
 
-### CocoaPods Issues
-- **When using remote integration, issues with mismatched Pod dependency versions**
+### CocoaPods
+- **Pod Dependency Version Mismatch When Using Remote Integration**
+
+    If you encounter a version mismatch between Podfile.lock and the plugin's TUICore dependency when using remote CocoaPods integration:
+
+    Delete the Podfile.lock file, run `pod repo update` to update the local code repository, and then run `pod update`.
+
+- **Pod Dependency Version Mismatch When Using Local Integration**
+
+   When integrating TUI components (such as TUIChat, TUIConversation, TIMCommon, etc.) using local Development Pods, and integrating TUICallKit via remote CocoaPods, you may encounter dependency conflicts caused by inconsistent version numbers. This issue is specifically manifested as follows:
+
+  - Locally integrated TUI components and their dependency TUICore use a default version number of 1.0.0.
+
+  - Remotely integrated TUICallKit and its dependency TUICore use a specific remote version (for example, 7.5.4852).
+
+      This results in a version conflict for TUICore.
+
+      **Solution：**
+
+      To resolve this issue, align the version numbers of your local TUI components and TUICore with the version used by the remote TUICallKit. Follow these steps:
+
+  1. In [Podfile_local](https://github.com/TencentCloud/chat-uikit-ios/blob/main/Demo/Podfile_local), update the version numbers of the relevant local components to match the remote version.
 
-   If you encounter a mismatch between the Podfile.lock and the plugin dependency version of TUICore while using remote CocoaPods integration,
+  2. In the [TUICore.podspec](https://github.com/TencentCloud/chat-uikit-ios/blob/main/TUIKit/TUICore/TUICore.podspec) file, set the version number to the same remote version (for example, 7.5.4852).By ensuring all components use a consistent version, you can avoid dependency conflicts during integration.
 
-   please delete the Podfile.lock file and use `pod repo update`to update your local repository, then use `pod update` to refresh the updates.
+-
 
-- **When using local integration, issues with mismatched Pod dependency versions**
+**Which third-party libraries does TUIKit depend on? What should I do if there are version conflicts?**
 
-   When integrating local DevelopmentPods and the plugin dependency on TUICoreis newer, but the local Pod dependency version is 1.0.0,
+   TUIKit manages dependencies automatically via CocoaPods, so manual intervention is typically unnecessary. If you encounter version conflicts, ensure your third-party library versions meet the following minimum requirements:
 
-   Please refer to [Podfile_local](https://github.com/TencentCloud/chat-uikit-ios/blob/main/Demo/Podfile_local) and [TUICore.spec](https://github.com/TencentCloud/chat-uikit-ios/blob/main/TUIKit/TUICore/TUICore.podspec) for modifications. The plugin needs to follow the version and match the one in TUICore.spec.
+【Swift Components】
+``` json
+- MJExtension (3.4.1)
+- MJRefresh (3.7.5)
+- SnapKit (5.7.1)
+- SSZipArchive (2.4.3)
+- SDWebImage (5.18.11)
+```
+
+【Objective-C Components】
+``` json
+- Masonry (1.1.0)
+- MJExtension (3.4.1)
+- MJRefresh (3.7.5)
+- ReactiveObjC (3.1.1)
+- SDWebImage (5.18.11):
+  - SDWebImage/Core (= 5.18.11)
+- SDWebImage/Core (5.18.11)
+- SnapKit (5.6.0)
+- SSZipArchive (2.4.3)
+```
 
-   When using local integration for the first time, we recommend you download our sample Demo project, replace the content of the Podfile with Podfile_local, and execute `Pod update` for cross-reference.
+### App Store Submission
+- **Packaging Fails When Submitting to App Store, Error: Unsupported Architectures**
 
-### Submission Issues
-- **Packaging failure when launching on the Appstore, with an 'Unsupported Architectures' error message.**
+   The following error may occur during packaging: ImSDK_Plus.framework contains the x86_64 simulator version, which is not supported by the App Store. This is because the SDK includes the simulator version by default for developer debugging.
 
-   The issue is illustrated below, where packaging indicates the ImSDK_Plus.framework includes an x86_64 simulator version not supported by the Appstore. This is because the SDK, to facilitate developer debugging, defaults to including the simulator version upon release.
+   **Solution：**
 
-   You can follow the steps below to remove the simulator version during packaging:
+    To remove the simulator version during packaging:
 
-  1. Select your project's Target and click on the `Build Phases` option, then add a `Run Script` to the current panel;
+  1. Select your project's Target, go to the `Build Phases` tab, and add a `Run Script` in the current panel.
 
-  2. In the newly added Run Script, insert the following script:
+  2. In the new Run Script, add the following script:
 
       ``` bash
       #!/bin/sh
@@ -702,33 +698,39 @@ After integrating TUIKit, if you want to continue building basic interfaces for
       done
       ```
 
-### TUICallKit Issues
-- **What should I do if TUICallKit conflicts with an audio/video library that I have integrated?**
+### TUICallKit
+- **TUICallKit Conflicts with Your Own Integrated Audio/Video Library?**
 
-   Tencent Cloud's audio and video libraries cannot be integrated simultaneously due to possible symbol conflicts. These can be addressed as follows.
+    Tencent Cloud audio/video libraries cannot be integrated together, as symbol conflicts may occur. Handle this according to your scenario:
 
-  1. If you have integrated the `TXLiteAVSDK_TRTC` library, a symbol conflict will not occur. You can directly add the dependency in Podfile:
+  1. If you use the `TXLiteAVSDK_TRTC` library, no symbol conflicts will occur. Add the dependency in your Podfile:
 
       ``` ruby
       pod 'TUICallKit_Swift'
       ```
-  2. If you have integrated the `TXLiteAVSDK_Professional` library, a symbol conflict will occur. You can add the dependency in Podfile:
+  2. If you use the `TXLiteAVSDK_Professional` library, symbol conflicts will occur. Add the dependency in your Podfile:
 
       ``` ruby
         pod 'TUICallKit_Swift/Professional'
       ```
-  3. If you have integrated the `TXLiteAVSDK_Enterprise` library, a symbol conflict will occur. It is recommended to upgrade to `TXLiteAVSDK_Professional` and then use TUICallKit_Swift/Professional.
+  3. If you use the `TXLiteAVSDK_Enterprise` library, symbol conflicts will occur. We recommend upgrading to `TXLiteAVSDK_Professional` and then using `TUICallKit_Swift/Professional`.
+
+- **What is the default timeout for call invitations?**
+
+    The default timeout for call invitations is 30 seconds.
+
+- **If the invitee goes offline and comes back online within the invitation timeout, can they receive the invitation immediately?**
 
-- **How long is the default duration for call invitation timeouts?**
+   1.1 For one-on-one call invitations, if the invitee goes offline and comes back online, they will receive the call invitation. TUIKit will automatically display the call invitation interface.
 
-   The default timeout duration for a call invitation is 30 seconds.
+   1.2 For group call invitations, if the invitee goes offline and comes back online, TUIKit will automatically retrieve invitations from the last 30 seconds and display the group call interface.
 
-- **During the invitation timeout period, can the invitee immediately receive the invitation if they go offline and then online?**
+### Others
 
-   1.If the call invitation is started in a one-to-one chat, the invitee can receive the call invitation, and the TUIKit will automatically open the call invitation UI internally.
+#### Using Emoji Packs
 
-   2.If the call invitation is for a group chat, the invitee will automatically fetch invitations from the last 30 seconds upon going online again, and the TUIKit will automatically trigger the group call interface.3.
+To respect the copyright of emoji designs, the Chat Demo/TUIKit project does not include cutouts of large emoji elements. Please replace them with your own designs or other emoji packs for which you hold the copyright before officially launching for commercial use. **The default smiley face emoji pack shown below is copyrighted by Tencent RTC**, you can upgrade to [Chat Pro Plus Edition and Enterprise Edition](https://console.trtc.io/subscription/buy/chat) to use it for free.
 
 ## Contact Us
 
-If you have any questions about this article, feel free to join the [Telegram Technical Group](https://t.me/+EPk6TMZEZMM5OGY1), where you will receive reliable technical support.
+If you have any questions or suggestions, feel free to join our [Telegram](https://t.me/tencent_imsdk) or [WhatsApp](https://chat.whatsapp.com/IVa11ZkVmKTEwSWsAzSyik) community, or [contact us](https://trtc.io/contact) for support.

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

@@ -0,0 +1,101 @@
+## Component Overview
+
+`ChatSetting` is an intelligent chat settings component that can automatically render the appropriate settings interface based on the currently activated session type. This component internally integrates two modes: C2C (one-on-one) chat settings and group chat settings, providing users with a uniform chat settings portal.
+
+Core features of components:
+- **Automatic adaptation** - The settings interface is automatically switched based on session type
+
+- **Status-driven** - Auto-update content based on the current active session status
+
+## Props Parameters
+
+|Parameter|Type|Default Value|Description|
+|---------|---------|---------|---------|
+|className|string \| undefined|undefined|Custom CSS class name|
+|style|React.CSSProperties \| undefined|undefined|Custom inline style|
+
+## Quick Usage
+
+`ChatSetting` is an independent component that can be used freely. By default, the switch control is on the ChatHeader Component. Alternatively use the useUIOpenControlState Hook to customize the ChatSetting switch.
+``` typescript
+import { useState } from 'react';
+import {
+  ChatSetting,
+  Search,
+  useChatContext,
+  VariantType,
+} from '@tencentcloud/chat-uikit-react';
+import './styles.css';
+
+function ChatSidePanelsBasicDemo() {
+  const [isChatSettingShow, setIsChatSettingShow] = useState(false);
+  const [isSearchShow, setIsSearchShow] = useState(false);
+  const [targetID, setTargetID] = useState('');
+  const [conversationType, setConversationType] = useState<'C2C' | 'GROUP'>('C2C');
+  const { activeConversationID, setActiveConversation } = useChatContext();
+
+  const handleActivateConversation = () => {
+    const normalizedID = targetID.trim();
+    if (!normalizedID) {
+      return;
+    }
+    setActiveConversation(`${conversationType}${normalizedID}`);
+  };
+
+  return (
+    <div className="chat-side-panels-basic-demo">
+      <div className="chat-side-panels-basic-demo__header">
+        <h2>Chat Side Panels</h2>
+        <p>Activate a conversation, then open or close ChatSetting and Search.</p>
+      </div>
+
+      <div className="chat-side-panels-basic-demo__frame">
+        <div className="chat-side-panels-basic-demo__actions">
+          <input
+            onChange={event => setTargetID(event.target.value)}
+            placeholder="User ID or group ID"
+            value={targetID}
+          />
+          <select
+            onChange={event => setConversationType(event.target.value as 'C2C' | 'GROUP')}
+            value={conversationType}
+          >
+            <option value="C2C">C2C</option>
+            <option value="GROUP">GROUP</option>
+          </select>
+          <button onClick={handleActivateConversation} type="button">
+            Activate Conversation
+          </button>
+          <span className="chat-side-panels-basic-demo__active">
+            Active: {activeConversationID || 'None'}
+          </span>
+          <button
+            onClick={() => setIsChatSettingShow(show => !show)}
+            type="button"
+          >
+            {isChatSettingShow ? 'Hide Setting' : 'Show Setting'}
+          </button>
+          <button
+            onClick={() => setIsSearchShow(show => !show)}
+            type="button"
+          >
+            {isSearchShow ? 'Hide Search' : 'Show Search'}
+          </button>
+        </div>
+
+        {isChatSettingShow && (
+          <div className="chat-side-panels-basic-demo__panel">
+            <ChatSetting />
+          </div>
+        )}
+
+        {isSearchShow && (
+          <div className="chat-side-panels-basic-demo__panel">
+            <Search variant={VariantType.EMBEDDED} />
+          </div>
+        )}
+      </div>
+    </div>
+  );
+}
+```