@tencent-rtc/mcp 1.3.8 → 1.4.0

package/resource/doc/{chatuikit → chatkit}/flutter/integration.md

@@ -9,7 +9,6 @@ TUIKit provides a complete set of instant messaging UI components, relying on th
 
 - AtomicXCore (Data Layer): Provides data management and business logic, including various Stores and Managers.
 
-
 ## Prerequisites
 - Flutter >= 3.29.0, Dart >= 3.7.0, Kotlin >= 1.9.
 
@@ -22,10 +21,9 @@ TUIKit provides a complete set of instant messaging UI components, relying on th
   - SDKAppID: The ID of the Chat application obtained from the console, serving as the unique identifier for the application.
 
   - SDKSecretKey: The application's secret key.
-      
 
       > **Note:**
-      > 
+      >
 >     - This project currently only supports manual integration and does not support integration via pub.dev.
 >     - To ensure a stable build environment, please strictly follow the official compatibility requirements for configuration:
 >     - For compatibility between Gradle, Android Gradle Plugin, JDK, and Android Studio, please refer to the Android official documentation: [Version Notes](https://developer.android.com/build/releases/gradle-plugin#updating-gradle).
@@ -33,8 +31,7 @@ TUIKit provides a complete set of instant messaging UI components, relying on th
 >     - Use JDK 17, as other versions may cause compilation failures. Refer to: [Java Version Switching](https://developer.android.com/build/jdks#kts).
 
       > We recommend that you choose a version combination that fully matches the project requirements according to the above guidelines.
-      > 
-
+      >
 
 ## Integration and Import Components
 
@@ -69,21 +66,18 @@ chat/
 ### Integrate Components
 1. Copy the complete component directory to your Flutter project, as shown below. Here flutter_demo is the example project, and TUIKit_Flutter is the component source code downloaded from GitHub:
 
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027325838/b47217aac39011f0a6dd5254005ef0f7.png)
-
 2. Add TUIKit Flutter components to your pubspec.yaml file. Note that TUIKit_Flutter can be placed anywhere, as long as the relative path is correctly set in pubspec.yaml:
 
    ``` bash
      tuikit_atomic_x:
        path: ../TUIKit_Flutter/atomic-x
-   ```   
+   ```
 
    > **Note:**
-   > 
+   >
 >   - When using the local integration solution, if you need to upgrade, you need to obtain the latest component code from GitHub and overwrite the TUIKit_Flutter directory in your local project.
 >   - When there are conflicts between private modifications and remote changes, you need to manually merge and resolve conflicts.
 
-
 ### Configure Project
 
 Add necessary permission configurations on the iOS side. Open ios/Podfile and add the following permission code at the end of the file:
@@ -91,10 +85,10 @@ Add necessary permission configurations on the iOS side. Open ios/Podfile and ad
 post_install do |installer|
   installer.pods_project.targets.each do |target|
     flutter_additional_ios_build_settings(target)
-    target.build_configurations.each do |config|        
-          config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'               
-          config.build_settings['ENABLE_BITCODE'] = 'NO'        
-          config.build_settings["ONLY_ACTIVE_ARCH"] = "NO"    
+    target.build_configurations.each do |config|
+          config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'
+          config.build_settings['ENABLE_BITCODE'] = 'NO'
+          config.build_settings["ONLY_ACTIVE_ARCH"] = "NO"
         end
     target.build_configurations.each do |config|
           config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= [
@@ -113,8 +107,7 @@ end
 
 ### Step 1: Configure User Authentication
 
-Obtain UserSig according to UserID in the [IM Chat Console](console.trtc.io/usersig) for subsequent user authentication during login.
-
+Obtain UserSig according to UserID in the [Chat Console](https://console.trtc.io/usersig) for subsequent user authentication during login.
 
 ### Step 2: User Login
 
@@ -133,11 +126,10 @@ if (result.errorCode == 0) {
 ```
 
 > **Note:**
-> 
+>
 
 > In a formal production environment, it is recommended to generate UserSig on your server. When UserSig is needed, your App should send a request to your business server to obtain dynamic UserSig for authentication. See [Generate UserSig on Server](https://trtc.io/document/34385).
-> 
-
+>
 
 ### Step 3: Build Conversation List Interface
 
@@ -146,12 +138,8 @@ You can build a conversation list page based on the ConversationList component i
 
 - Support user operations on individual conversations: pin, delete, clear conversation messages, etc.
 
-
    You can integrate ConversationList directly into your existing App page, or build a complete new conversation list page. One assembled UI effect is shown below:
 
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027325838/acbda867c3a611f08c0e52540044a08e.png)
-
-
    To encapsulate ConversationList as a conversation list page, refer to the implementation in the `chat/uikit/lib/conversations_page.dart` file. `ConversationsPage` mainly does the following:
 
 1. Adds AppBar above ConversationList.
@@ -166,7 +154,6 @@ You can build a conversation list page based on the ConversationList component i
 
   3. Supports selecting multiple friends to create group chats
 
-
       Core example code is as follows:
 
       ``` java
@@ -211,24 +198,18 @@ Built-in features of MessageList include:
 
 - Support operations on individual messages: view large images for image messages, play video or voice messages, copy text messages, recall messages, delete messages, etc.
 
-
    Built-in features of MessageInput include:
 
 - Support users in composing and sending various types of messages: text, emoji, image, voice, video, file, etc.
 
-
    You can integrate MessageList and MessageInput directly into your existing App page, or build a complete new chat page. One assembled UI effect is shown below:
 
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027325838/a2c04843c3a811f0a6dd5254005ef0f7.png)
-
-
    To assemble MessageList and MessageInput as a chat page, refer to the implementation in the `chat/uikit/lib/chat_page.dart` file. `ChatPage` mainly does the following:
 
 1. Adds AppBar at the top to display the conversation name.
 
 2. Vertically combines MessageList and MessageInput according to mobile user habits.
 
-
    Core example code is as follows:
 
    ``` java
@@ -299,12 +280,8 @@ You can build a contact page based on the ContactList component in TUIKit Flutte
 
 - View friends.
 
-
    You can integrate ContactList directly into your existing App, or build a complete new contact list page. One assembled UI effect is shown below:
 
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027325838/4bf1d883c3a911f0b35752540099c741.png)
-
-
    To encapsulate ContactList as a contact list page, refer to the implementation in the `chat/uikit/lib/contacts_page.dart` file. `ContactsPage` mainly does the following:
 
 1. Adds AppBar above ContactList.
@@ -319,7 +296,6 @@ You can build a contact page based on the ContactList component in TUIKit Flutte
 
   3. Supports searching for target groups by GroupID
 
-
       Core example code is as follows:
 
       ``` java
@@ -350,58 +326,14 @@ You can build a contact page based on the ContactList component in TUIKit Flutte
 ### Step 6: Complete Navigation Logic Between Interfaces
 
 ConversationsPage, ChatPage, and ContactsPage implement default user click events. You can customize events to implement interactions between pages:
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >Page</td>
-
-<td rowspan="1" colSpan="1" >Callback</td>
-
-<td rowspan="1" colSpan="1" >Suggested Navigation Logic</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >**ConversationsPage**</td>
-
-<td rowspan="1" colSpan="1" >`onConversationClick: (conversation) {}`</td>
-
-<td rowspan="1" colSpan="1" >Triggered when clicking a conversation in the conversation list, recommended to navigate to the chat page (ChatPage).</td>
-</tr>
-
-<tr>
-<td rowspan="2" colSpan="1" >**ContactsPage**</td>
-
-<td rowspan="1" colSpan="1" >`onContactClick: (ContactInfo contactInfo) {}`</td>
-
-<td rowspan="1" colSpan="1" >Triggered when clicking a contact cell, recommended to navigate to the user info page (C2CChatSetting).</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`onGroupClick: (ContactInfo contactInfo) {}`</td>
-
-<td rowspan="1" colSpan="1" >Triggered when clicking a group cell, recommended to navigate to the group chat page (ChatPage).</td>
-</tr>
-
-<tr>
-<td rowspan="3" colSpan="1" >**ChatPage**</td>
-
-<td rowspan="1" colSpan="1" >`onUserClick: (String userID) {}`</td>
-
-<td rowspan="1" colSpan="1" >Triggered when clicking a user avatar or nickname in a message, recommended to navigate to the user info page (C2CChatSetting).</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`onChatHeaderClick: () {}`</td>
-
-<td rowspan="1" colSpan="1" >Triggered when clicking the avatar in the navigation bar, recommended to navigate to the user info page (C2CChatSetting) or group chat info page (GroupChatSetting)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >`onBackClick: () {}`</td>
-
-<td rowspan="1" colSpan="1" >Triggered when clicking the back button, recommended to return to the previous page.</td>
-</tr>
-</table>
-
+| Page | Callback | Suggested Navigation Logic |
+| --- | --- | --- |
+| **ConversationsPage** | `onConversationClick: (conversation) {}` | Triggered when clicking a conversation in the conversation list, recommended to navigate to the chat page (ChatPage). |
+| **ContactsPage** | `onContactClick: (ContactInfo contactInfo) {}` | Triggered when clicking a contact cell, recommended to navigate to the user info page (C2CChatSetting). |
+| `onGroupClick: (ContactInfo contactInfo) {}` | Triggered when clicking a group cell, recommended to navigate to the group chat page (ChatPage). |  |
+| **ChatPage** | `onUserClick: (String userID) {}` | Triggered when clicking a user avatar or nickname in a message, recommended to navigate to the user info page (C2CChatSetting). |
+| `onChatHeaderClick: () {}` | Triggered when clicking the avatar in the navigation bar, recommended to navigate to the user info page (C2CChatSetting) or group chat info page (GroupChatSetting) |  |
+| `onBackClick: () {}` | Triggered when clicking the back button, recommended to return to the previous page. |  |
 
 You can refer to the above callback descriptions and reference code to implement interaction logic between Pages.
 
@@ -410,4 +342,3 @@ You can refer to the above callback descriptions and reference code to implement
 ### **After integrating the tuikit_atomic_x component, what should I do about errors related to **`theme_state`** and **`atomic_localizations`**?**
 
 The component supports theme color and internationalized string switching. You need to use `ComponentTheme` to wrap the root `widget` in the `main.dart` file in the project root directory, and add the `AtomicLocalizations.delegate` configuration to the `localizationsDelegates` of `MaterialApp`. You can refer to the `main.dart` file in the source code Demo for usage.
-

package/resource/doc/{chatuikit/iOS → chatkit/ios}/faq.md

@@ -7,7 +7,6 @@ Yes.
 
 - If you are using Chat Free edition and upgrade to Chat Pro Edition, after the upgrade, you can configure your SDKAppID in the console to ensure proper login. For pricing details, see [Pricing](https://intl.cloud.tencent.com/document/product/1047/34350).
 
-
 ### Why do I encounter a 6013 "SDK Not Initialized" error?
 
 If the 6013 "SDK Not Initialized" error occurs, try the following troubleshooting methods:
@@ -17,7 +16,6 @@ If the 6013 "SDK Not Initialized" error occurs, try the following troubleshootin
 
 3. For Android, verify that all library files have been loaded or repossessed by the system during use.
 
-
 ### Why do I encounter "code: 6205 desc: QALSERVICE not ready" error?
 
 This error is caused by calling `stopQALService` after initialization. To fix it, refer to the [configuration method](https://blog.csdn.net/qq_16131393/article/details/54895733) shared by one of our customers.
@@ -31,10 +29,8 @@ There are two ways to use emojis:
 
 - Use data in TIMFaceElem. For example, the names of emoji images are string-type. Use the word "smile" to represent the smile emoji, and store "smile" in data. Then, both iOS and Android devices use data as the key to retrieve and display the corresponding emoji.
 
-
    You can also use the two fields at the same time. For example, use data to specify the emoji set and index to indicate the specific index in this emoji set. This way, you can implement many different emoji effects as in QQ. It is possible to store more complex data structures in data as long as the devices follow the same parsing rules.
 
-
 ### Why do I encounter error 10002 during operations?
 
 This status code is returned when a network exception, timeout, or ticket switching failure occurs during server-side authentication. If you see this status code, wait a moment and try again.
@@ -60,7 +56,6 @@ These errors occur because UserID and UserSig do not match. To fix it, check the
 
 - -5: When the login attempt is not completed and the SDK has not received the a2key and tinyID returned by the server, directly calling other APIs returns the "tinyid or a2 is empty" error message and -5 error code.
 
-
 ### What should I do when the SDK on the armeabi platform reports "java.lang.UnsatisfiedLinkError: No implementation found for"?
 
 Copy jni/armeabi-v7a/libImSDK.so in the Chat SDK’s aar file to the src/main/jniLibs/armeabi directory in your source code project and load it in build.gradle.
@@ -77,44 +72,40 @@ This error occurs because App Store does not support the x86_64 and i386 archite
  c. Add the following code:
 
    ``` bash
-   APP_PATH="${TARGET_BUILD_DIR}/${WRAPPER_NAME}"  
-   
-   # This script loops through the frameworks embedded in the application and  
-   
-   # removes unused architectures.  
-   
-    find "$APP_PATH" -name '*.framework' -type d | while read -r FRAMEWORK  
-    do  
-    FRAMEWORK_EXECUTABLE_NAME=$(defaults read "$FRAMEWORK/Info.plist" CFBundleExecutable)  
-    FRAMEWORK_EXECUTABLE_PATH="$FRAMEWORK/$FRAMEWORK_EXECUTABLE_NAME"  
-    echo "Executable is $FRAMEWORK_EXECUTABLE_PATH"  
-   
-    EXTRACTED_ARCHS=()  
-   
-    for ARCH in $ARCHS  
-    do  
-    echo "Extracting $ARCH from $FRAMEWORK_EXECUTABLE_NAME"  
-    lipo -extract "$ARCH" "$FRAMEWORK_EXECUTABLE_PATH" -o "$FRAMEWORK_EXECUTABLE_PATH-$ARCH"  
-    EXTRACTED_ARCHS+=("$FRAMEWORK_EXECUTABLE_PATH-$ARCH")  
-    done  
-   
-    echo "Merging extracted architectures: ${ARCHS}"  
-    lipo -o "$FRAMEWORK_EXECUTABLE_PATH-merged" -create "${EXTRACTED_ARCHS[@]}"  
-    rm "${EXTRACTED_ARCHS[@]}"  
-   
-    echo "Replacing original executable with thinned version"  
-    rm "$FRAMEWORK_EXECUTABLE_PATH"  
-    mv "$FRAMEWORK_EXECUTABLE_PATH-merged" "$FRAMEWORK_EXECUTABLE_PATH"  
-   
+   APP_PATH="${TARGET_BUILD_DIR}/${WRAPPER_NAME}"
+
+   # This script loops through the frameworks embedded in the application and
+
+   # removes unused architectures.
+
+    find "$APP_PATH" -name '*.framework' -type d | while read -r FRAMEWORK
+    do
+    FRAMEWORK_EXECUTABLE_NAME=$(defaults read "$FRAMEWORK/Info.plist" CFBundleExecutable)
+    FRAMEWORK_EXECUTABLE_PATH="$FRAMEWORK/$FRAMEWORK_EXECUTABLE_NAME"
+    echo "Executable is $FRAMEWORK_EXECUTABLE_PATH"
+
+    EXTRACTED_ARCHS=()
+
+    for ARCH in $ARCHS
+    do
+    echo "Extracting $ARCH from $FRAMEWORK_EXECUTABLE_NAME"
+    lipo -extract "$ARCH" "$FRAMEWORK_EXECUTABLE_PATH" -o "$FRAMEWORK_EXECUTABLE_PATH-$ARCH"
+    EXTRACTED_ARCHS+=("$FRAMEWORK_EXECUTABLE_PATH-$ARCH")
+    done
+
+    echo "Merging extracted architectures: ${ARCHS}"
+    lipo -o "$FRAMEWORK_EXECUTABLE_PATH-merged" -create "${EXTRACTED_ARCHS[@]}"
+    rm "${EXTRACTED_ARCHS[@]}"
+
+    echo "Replacing original executable with thinned version"
+    rm "$FRAMEWORK_EXECUTABLE_PATH"
+    mv "$FRAMEWORK_EXECUTABLE_PATH-merged" "$FRAMEWORK_EXECUTABLE_PATH"
+
     done
    ```
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100031390357/ac95ba51e28011eeb1eb525400b5f95f.png)
 
 3. Package the app and upload it again.
 
-
 ### Can developers directly utilize the emoticon packs demonstrated in the Chat various client demos/TUIKit projects?
 
 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).
-
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027202808/a44543c197f611ef820f525400d5f8ef.png)