@tencent-rtc/mcp 1.6.7 → 1.7.0

package/resource/knowledge/livekit/core-sdk/voice/ios/integration.md

@@ -39,7 +39,6 @@ See Activate Service to obtain either the trial or paid version of the SDK.Then,
 Call `LoginStore.shared.login` in your project to complete authentication. **This is required before using any functionality of AtomicXCore**.
 
 > **Note：**
->
 > We recommend calling LoginStore.shared.login only after your app's own user authentication is successful, to ensure clear and consistent login logic.
 >
 
@@ -198,7 +197,6 @@ class YourAnchorViewController: UIViewController {
 #### **4. Build the Mic Seat UI**
 
 > **Note：**
->
 > For seat UI logic and effects, refer to the open-source [SeatGridView.swift](https://github.com/Tencent-RTC/TUIKit_iOS/blob/main/live/Sources/Component/SeatGridview/SeatGridView.swift) in TUILiveKit.
 >
 
@@ -337,7 +335,7 @@ class YourAudienceViewController: UIViewController {
 
 #### **3. Build the Mic Seat UI**
 
-Building the seat UI for audience members is identical to the host process. Refer to the host Build the Mic Seat UI.
+Building the seat UI for audience members is identical to the host process. .
 
 #### **4. Leave the Voice Chat Room**
 
@@ -377,7 +375,6 @@ In voice chat rooms, it's common to show a wave animation over the avatar of use
 #### Implementation
 
 > **Note：**
->
 > For a complete implementation of the speaking wave animation, refer to [SeatGridView.swift](https://github.com/Tencent-RTC/TUIKit_iOS/blob/main/live/Sources/Component/SeatGridview/SeatGridView.swift) in TUILiveKit.
 >
 

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

@@ -11,7 +11,6 @@
 |-1002|Not logged in, please call `Login` API.|
 |-1003|Failed to obtain permission, unauthorized audio/video permission, please check if `Device Permission` is enabled.|
 |-1004|This feature requires an additional package. Please activate the corresponding package as needed in the [TRTC Console](https://console.tencentcloud.com/trtc/allapp).|
-|-3301|Network access is restricted. Please [contact us](https://trtc.io/contact) for support.|
 
 ### Local User Rendering, Video Management, Audio Management API Callback Error Definition
 

package/resource/knowledge/livekit/preset/live/vue/features/barrage.md

@@ -1,4 +1,4 @@
-This document provides a detailed introduction to the **barrage component**, including the **barrage message component (BarrageList)** and the **message sending component (BarrageInput)**. You can refer to the sample code in this document for seamless integration of our pre-developed components into your existing project, or customize the style and layout according to your needs by following the component customization section in the document.
+This document provides a detailed introduction to the **barrage component**, including the **barrage message component (BarrageList)** and the **message sending component (BarrageInput)**. You can .
 
 ## Component Composition
 | <strong>Component Name</strong> | <strong>Detailed Description</strong> |
@@ -10,7 +10,7 @@ This document provides a detailed introduction to the **barrage component**, inc
 
 ### Step 1: Configuring the Environment and Activating the Service
 
-Before performing quick integration, you need to refer to preparations, meet the related environment configuration and activate the corresponding service.
+Before performing quick integration, you need to .
 
 ### Step 2: Installing Dependencies
 
@@ -84,7 +84,6 @@ onMounted(async () => {
 **Barrage Message Component** provides users with various and dimensional `Props` APIs for custom requirements, allowing users to customize features or UI. Parameter content is as shown in the table below.
 
 > **Note:**
->
 > Note: To directly learn about the custom details of the Barrage Message Component (BarrageList), quickly jump to the following link: Barrage Message Component Customization;
 >
 > Note: To directly learn about the custom details of the Message Sending Component (BarrageInput), quickly jump to the following link: Message Sending Component Customization.

package/resource/knowledge/livekit/preset/live/vue/features/live-audience-list.md

@@ -1,4 +1,4 @@
-This document provides a detailed introduction to the **Audience List Component (LiveAudienceList)**. You can refer to the sample code in this document for seamless integration into your existing project, or customize the style and layout according to your needs by following the component customization section in the document.
+This document provides a detailed introduction to the **Audience List Component (LiveAudienceList)**. You can .
 
 ## Core Features
 | <strong>Feature Category</strong> | <strong>Specific capabilities</strong> |
@@ -11,7 +11,7 @@ This document provides a detailed introduction to the **Audience List Component
 
 ### Step 1: Configuring the Environment and Activating the Service
 
-Before performing quick integration, you need to refer to preparations, meet the required environment configuration and activate the corresponding service.
+Before performing quick integration, you need to .
 
 ### Step 2: Dependency Installation
 
@@ -119,7 +119,7 @@ interface AudienceInfo {
 
 #### Custom Slot Example
 
-To help you better experience and understand the **audience list component**'s **customAudienceInfo** slot customization capability, we provide a **custom personal info** example scenario for your reference. You can refer to the above **step 3** and incrementally copy the following code into your project to achieve a similar effect.
+To help you better experience and understand the **audience list component**'s **customAudienceInfo** slot customization capability, we provide a **custom personal info** example scenario for your reference. You can .
 ``` typescript
 <template>
   <LiveAudienceList>

package/resource/knowledge/livekit/preset/live/vue/features/live-view.md

@@ -1,4 +1,4 @@
-This document provides a detailed introduction to the **live stream video component (LiveView)**. You can refer to the sample code in this document to integrate our pre-developed components into your existing project, or customize the style and layout according to your needs by following the component customization section in the document.
+This document provides a detailed introduction to the **live stream video component (LiveView)**. You can .
 
 ## Core Features
 | <strong>Feature Category</strong> | <strong>Specific Capacity</strong> |
@@ -10,7 +10,7 @@ This document provides a detailed introduction to the **live stream video compon
 
 ### Step 1: Configuring the Environment and Activating the Service
 
-Before quick integration, you need to refer to preparations, meet the related environment configuration and activate the corresponding service.
+Before quick integration, you need to .
 
 ### Step 2: Dependency Installation
 
@@ -164,7 +164,7 @@ LiveView provides flexible component customization slots. These slots support ad
 
 #### Custom Mic Seat Example
 
-To help you better experience and understand the customized capability of the LiveView component's streamViewUI, we provide a **live streaming and mic connection scenario** example for your reference. You can refer to the above **Step 3** to incrementally copy the following code into your project to achieve a similar scenario effect.
+To help you better experience and understand the customized capability of the LiveView component's streamViewUI, we provide a **live streaming and mic connection scenario** example for your reference. You can .
 ``` typescript
 <template>
   <LiveView>

package/resource/knowledge/push/api-reference/android.md

@@ -118,6 +118,5 @@ Received a notification of Push message recall, messageID uniquely identifies th
 Notification bar message click callback.
 
 > **Note:**
->
 > The push certificate in the console needs to be configured as "open a specific interface within the application" and use the default fill value to take effect.
 >

package/resource/knowledge/push/api-reference/harmonyos.md

@@ -41,7 +41,6 @@ unRegisterPush(): Promise<TIMPushResult>;
 ### Setting Push ID Identifier RegistrationID
 
 > **Note:**
->
 > 1. If you call this API, ensure to call it before `registerPush`.
 
 #### API
@@ -58,7 +57,6 @@ setRegistrationID(registrationID: string): Promise<TIMPushResult>;
 ### Getting Push ID Identifier RegistrationID
 
 > **Note:**
->
 > Note: If you have called the `setRegistrationID` API to set an identifier ID, this API will return the identifier ID you have set. Otherwise, it will return a random value generated by the Push SDK.
 >
 

package/resource/knowledge/push/api-reference/react-native.md

@@ -32,7 +32,7 @@ registerPush(SDKAppID, appKey, onSuccess, onError)
 
 #### API
 ``` javascript
-unRegisterPush(onSuccess, onError)
+unRegisterPush(onSuccess, onError)
 ```
 
 #### Parameter description:
@@ -45,12 +45,11 @@ registerPush(SDKAppID, appKey, onSuccess, onError)
 ### Set push ID identifier RegistrationID
 
 > **Note:**
->
 > 1. If you call this API, make sure to call it before `registerPush`.
 
 #### API
 ``` javascript
-setRegistrationID(registrationID, onSuccess)
+setRegistrationID(registrationID, onSuccess)
 ```
 
 #### Parameter description:
@@ -63,12 +62,11 @@ registerPush(SDKAppID, appKey, onSuccess, onError)
 ### Get push ID identifier RegistrationID
 
 > **Note:**
->
 > 1. If you have called the `setRegistrationID` interface to set the identifier ID, this interface will return the identifier ID you set, otherwise, it will return a random value generated by the Push SDK.
 
 #### API
 ``` javascript
-getRegistrationID(onSuccess)
+getRegistrationID(onSuccess)
 ```
 
 #### Parameter description:

package/resource/knowledge/push/api-reference/uni-app.md

@@ -32,7 +32,7 @@ registerPush(SDKAppID, appKey, onSuccess, onError)
 
 #### API
 ``` javascript
-unRegisterPush(onSuccess, onError)
+unRegisterPush(onSuccess, onError)
 ```
 
 #### Parameter description:
@@ -45,12 +45,11 @@ registerPush(SDKAppID, appKey, onSuccess, onError)
 ### Set push ID identifier RegistrationID
 
 > **Note:**
->
 > 1. If you call this API, make sure to call it before `registerPush`.
 
 #### API
 ``` javascript
-setRegistrationID(registrationID, onSuccess)
+setRegistrationID(registrationID, onSuccess)
 ```
 
 #### Parameter description:
@@ -63,12 +62,11 @@ registerPush(SDKAppID, appKey, onSuccess, onError)
 ### Get push ID identifier RegistrationID
 
 > **Note:**
->
 > 1. If you have called the `setRegistrationID` interface to set the identifier ID, this interface will return the identifier ID you set, otherwise, it will return a random value generated by the Push SDK.
 
 #### API
 ``` javascript
-getRegistrationID(onSuccess)
+getRegistrationID(onSuccess)
 ```
 
 #### Parameter description:

package/resource/knowledge/push/api-reference/unity.md

@@ -114,6 +114,5 @@ Received a Push message recall notification, messageID unique message identifier
 Click the notification bar message Webhook.
 
 > **Note:**
->
 > Configure the console Push Certificate to "open specified in-app page" and use the default populated value to take effect.
 >

package/resource/knowledge/push/api-reference/unreal-engine.md

@@ -118,6 +118,5 @@ Push message recall notification received. messageID: unique message identifier.
 Click notification bar message Webhook.
 
 > **Note:**
->
 > Note: Push Certificate in the console need to configure "open specified in-app page" and use populate by default to take effect.
 >

package/resource/knowledge/push/config/android.md

@@ -22,10 +22,6 @@ Explanation of the **Subsequent Actions** option:
 
 【Mi】
 
-|Vendor Push Platform|Configuring in the Chat console|
-|---------|---------|
-|||
-
 【Huawei】
 | Vendor Push Platform | Configuring in the Chat console |
 | --- | --- |
@@ -33,38 +29,18 @@ Explanation of the **Subsequent Actions** option:
 
 【OPPO】
 
-|Vendor Push Platform|Configuring in the Chat console|
-|---------|---------|
-|||
-
 【vivo】
 
-|Vendor Push Platform|Configuring in the Chat console|
-|---------|---------|
-|||
-
 For receipt configuration, please refer to: [Message Delivery Statistics Configuration - vivo](https://www.tencentcloud.com/document/product/1047/60552#daa658b0-1ac0-44a8-8a47-7ec8822ebe82).
 
 【Meizu】
 
-|Vendor Push Platform|Configuring in the Chat console|
-|---------|---------|
-|||
-
 For receipt configuration, please refer to: [Message Delivery Statistics Configuration - Meizu](https://www.tencentcloud.com/document/product/1047/60552#daa658b0-1ac0-44a8-8a47-7ec8822ebe82).
 
 【HONOR】
 
-|Vendor Push Platform|Configuring in the Chat console|
-|---------|---------|
-|||
-
 【Google FCM】
 
-|Vendor Push Platform|Configuring in the Chat console|
-|---------|---------|
-|||
-
    > **Note:**
    >
    > Regarding **Click for Subsequent Actions** supports the Report Statistics feature:

package/resource/knowledge/push/config/harmonyos.md

@@ -1,5 +1,4 @@
 > **Note:**
->
 > Each vendor only supports the configuration of one certificate.
 >
 

package/resource/knowledge/push/config/ios.md

@@ -6,7 +6,6 @@ If you have any questions about the "Developer Account" or "Develop/Distribute C
 1. APNs Push Certificate Configuration
 
 > **Note：**
->
 > Each vendor only supports the configuration of one certificate.
 >
 
@@ -43,8 +42,6 @@ Apple currently offers two mainstream types of certificates for vendor configura
 #### Generating Certificate
 1. Select your AppID, choose **Configure**.
 
-2. You can see in the  **Apple Push Notification service SSL Certificates**  window, there are two  `SSL  Certificate`, one for the development environment (Development) and the other for the production environment (Production) remote push certificate, as shown below:
-
 3. First, we choose the Development **Create Certificate**; the system will prompt us that a Certificate Signing Request (CSR) is required.
 
 4. Open **Keychain Access** on your Mac, in the menu, select **Keychain Access** > **Certificate Assistant** > **Request a Certificate From a Certificate Authority** (`Keychain Access - Certificate Assistant - Request a Certificate From a Certificate Authority`).

package/resource/knowledge/push/config/react-native.md

@@ -1,7 +1,6 @@
 React Native push currently supports vendor channels such as Xiaomi, Huawei, Honor, OPPO, vivo, Meizu, APNs, OnePlus, realme, iQOO, FCM, and Apple.
 
 > **Note:**
->
 > Each vendor only supports the configuration of one certificate.
 >
 
@@ -43,8 +42,6 @@ There are currently two mainstream types of certificates for Apple Manufacturer
 #### Certificate Generation
 1. Select your AppID and choose **Configure**.
 
-2. In the **Apple Push Notification service SSL Certificates** window, there are two `SSL Certificates` for the development environment (Development) and the production environment (Production), as shown below:
-
 3. We first select the **Create Certificate** for the Development environment, the system will prompt us that we need a Certificate Signing Request (CSR).
 
 4. On a Mac, open **Keychain Access tool**, in the menu select **Keychain Access** > **Certificate Assistant** > **Request a Certificate From a Certificate Authority** (`Keychain Access - Certificate Assistant - Request a Certificate From a Certificate Authority`).
@@ -83,7 +80,6 @@ There are currently two mainstream types of certificates for Apple Manufacturer
 4. Select the certificate type, upload the iOS Certificate (.p12), set the certificate password, and click **Confirm**.
 
 > **Note:**
->
 > - We recommend naming the uploaded certificate in English (special characters such as brackets are not allowed).
 > - You need to set a password for the uploaded certificate. Without a password, push notifications cannot be received.
 > - For an app published on App Store, the environment of the certificate must be the production environment. Otherwise, push notifications cannot be received.
@@ -120,7 +116,6 @@ Confirm and generate the key: On the confirmation page, verify your key informat
 4. Select the .p8 certificate, upload the iOS Certificate (.p8), set **KeyID、TeamID and BundleID**, and click **Confirm**.
 
 > **Note:**
->
 > - **KeyID**: This is the unique identifier for your APNs Auth Key. When you create a new APNs Auth Key in the Apple Developer Center, a Key ID will be generated for you. You can find it in the "Certificates, Identifiers & Profiles" section under "Keys".
 > - **TeamID**: This is the unique identifier for your developer account. You can find it on the account details page of the Apple Developer Center. Click "Membership" in the upper right corner, and you can find your Team ID in the "Membership Details" section.
 > - **BundleID**: This is the unique identifier for your application, also known as the app ID. You can find it in the "Certificates, Identifiers & Profiles" section of the Apple Developer Center. Select "Identifiers", then find the corresponding Bundle ID in your list of applications.
@@ -138,7 +133,6 @@ Offline push requires you to register your app with each vendor's push platform
 Log in to Tencent Cloud [Chat Console](https://console.trtc.io/chat/push-plugin-push-identifier), under **Push Management** > **Access Settings** feature tab, add the push certificates for each vendor, and configure the AppId, AppKey, AppSecret, and other parameters obtained in step one to the added push certificates.
 
 > **Note:**
->
 > Regarding the **Action after Click** option, to use the click-to-navigate feature provided by this plugin, please keep the default value unchanged, which is usually `Open a specified page within the app` with default settings. (Note)
 >
 > To use the reporting statistics feature, also keep this item at its default value. (Note)
@@ -146,10 +140,6 @@ Log in to Tencent Cloud [Chat Console](https://console.trtc.io/chat/push-plugin-
 
 【Mi】
 
-|Vendor Push Platform|Configuring in the Chat console|
-|---------|---------|
-|||
-
 【Huawei】
 | Vendor Push Platform | Configuring in the Chat console |
 | --- | --- |
@@ -172,16 +162,8 @@ Log in to Tencent Cloud [Chat Console](https://console.trtc.io/chat/push-plugin-
 
 【OPPO】
 
-|Vendor Push Platform|Configuring in the Chat console|
-|---------|---------|
-|||
-
 【vivo】
 
-|Vendor Push Platform|Configuring in the Chat console|
-|---------|---------|
-|||
-
 #### Receipt configuration
 
 **Receipt Address:**
@@ -199,10 +181,6 @@ Log in to Tencent Cloud [Chat Console](https://console.trtc.io/chat/push-plugin-
 
 【Meizu】
 
-|Vendor Push Platform|Configuring in the Chat console|
-|---------|---------|
-|||
-
 #### Receipt configuration
 
 **Receipt Address:**
@@ -220,10 +198,6 @@ Log in to Tencent Cloud [Chat Console](https://console.trtc.io/chat/push-plugin-
 
 【HONOR】
 
-|Vendor Push Platform|Configuring in the Chat console|
-|---------|---------|
-|||
-
 #### Receipt configuration
 
 **Receipt Address:**
@@ -241,6 +215,3 @@ Log in to Tencent Cloud [Chat Console](https://console.trtc.io/chat/push-plugin-
 
 【Google FCM】
 
-|Vendor Push Platform|Configuring in the Chat console|
-|---------|---------|
-|||

package/resource/knowledge/push/config/unity.md

@@ -1,7 +1,6 @@
 Currently, the message push plugin in Unity only supports push to Android (including manufacturer channels) and iOS devices.
 
 > **Note:**
->
 > Each vendor only supports the configuration of one certificate.
 >
 
@@ -18,7 +17,7 @@ Before integrating the message push plug-in, you must apply for an APNs Push Cer
 
 2. Click **+** on the right of Identifiers.
 
-3. You can refer to the following procedure to create a new AppID, or add the `Push Notification` `Service` to your original AppID.
+3. You can .
 
    > **Note**
    >
@@ -36,8 +35,6 @@ Before integrating the message push plug-in, you must apply for an APNs Push Cer
 #### Generating a Certificate
 1. Select your AppID, choose **Configure**.
 
-2. In the **Apple Push Notification service SSL Certificates** window, you can see two `SSL Certificates`, respectively for remote push certificates in development environment (Development) and production environment (Production), as shown below:
-
 3. First select the development environment (Development) **Create Certificate**, the system will prompt you to provide a Certificate Signing Request (CSR).
 
 4. On your Mac, open **Keychain Access**, select **Keychain Access** > **Certificate Assistant** > **Request a Certificate From a Certificate Authority** (`Keychain Access - Certificate Assistant - Request a Certificate From a Certificate Authority`).
@@ -97,16 +94,12 @@ Offline push requires registering your own application to various manufacturers'
 Log in to Tencent Cloud [Chat console](https://console.trtc.io/chat/push-plugin-push-identifier), go to **Push Management** > **Access Setting** feature section, add push certificates from various manufacturers, and configure the AppId, AppKey, AppSecret and other parameters obtained from step 1 for the added certificates.
 
 > **Note:**
->
 > Note: For the **click subsequent actions** option, if you need to use the click redirect capacity provided by this Plugin, keep default values unchanged, usually `open a specified page within the app` with default configuration.
 >
 > If you need to use the report statistics feature, keep this item unchanged.
 >
 
 【Xiaomi】
-| Vendor Push Platform | Chat Console Configuration |
-| --- | --- |
-|  |  |
 
 【Huawei】
 | Vendor Push Platform | Chat Console Configuration |
@@ -129,14 +122,8 @@ Log in to Tencent Cloud [Chat console](https://console.trtc.io/chat/push-plugin-
 - China: https://api.im.qcloud.com/v3/offline_push_report/huawei
 
 【OPPO】
-| Vendor Push Platform | Chat Console Configuration |
-| --- | --- |
-|  |  |
 
 【vivo】
-| Vendor Push Platform | Chat Console Configuration |
-| --- | --- |
-|  |  |
 
 **Receipt configuration**
 
@@ -154,9 +141,6 @@ Log in to Tencent Cloud [Chat console](https://console.trtc.io/chat/push-plugin-
 - China: https://api.im.qcloud.com/v3/offline_push_report/vivo
 
 【Meizu】
-| Vendor Push Platform | Chat Console Configuration |
-| --- | --- |
-|  |  |
 
 **Receipt configuration**
 
@@ -175,10 +159,6 @@ Log in to Tencent Cloud [Chat console](https://console.trtc.io/chat/push-plugin-
 
 【Honor】
 
-| Vendor Push Platform | Chat Console Configuration |
-| --- | --- |
-|  |  |
-
 #### Receipt configuration
 
 **Receipt Address:**
@@ -196,6 +176,3 @@ Log in to Tencent Cloud [Chat console](https://console.trtc.io/chat/push-plugin-
 
 【Google FCM】
 
-| Vendor Push Platform | Chat Console Configuration |
-| --- | --- |
-|  |  |

package/resource/knowledge/push/config/unreal-engine.md

@@ -1,7 +1,6 @@
 The push service currently supports Vendor Channels such as Xiaomi, Huawei, Honor, OPPO, vivo, Meizu, OnePlus, realme, iQOO, FCM, and Apple.
 
 > **Note:**
->
 > Each vendor only supports the configuration of one certificate.
 >
 
@@ -18,7 +17,7 @@ Before integrating the message push plug-in, you must apply for an APNs Push Cer
 
 2. Click **+** on the right of Identifiers.
 
-3. You can refer to the following steps to create a new AppID or add the `Push Notification` `Service` to your original AppID.
+3. You can .
 
    > **Note**
    >
@@ -36,8 +35,6 @@ Before integrating the message push plug-in, you must apply for an APNs Push Cer
 #### Generating a Certificate
 1. Select your AppID, then click **Configure**.
 
-2. You can see two `SSL Certificates` in the **Apple Push Notification service SSL Certificates** window, used for development environment (Development) and production environment (Production) remote push certificates, as shown below:
-
 3. First select the development environment (Development) **Create Certificate**, the system will prompt us to provide a Certificate Signing Request (CSR).
 
 4. On your Mac, open **Keychain Access**, then select **Keychain Access** > **Certificate Assistant** > **Request a Certificate From a Certificate Authority** (`Keychain Access - Certificate Assistant - Request a Certificate From a Certificate Authority`).
@@ -97,16 +94,12 @@ Offline push requires registering your own application to various manufacturers'
 Sign in to the [Chat console](https://console.trtc.io/chat/push-plugin-push-identifier), go to the **push management** > **access setting** feature section, add push certificates for various manufacturers, and configure the AppId, AppKey, AppSecret and other parameters obtained from step 1 for the added push certificates.
 
 > **Note:**
->
 > Note: For the **click subsequent actions** option, if you need to use the click redirect power provided by this Plugin, keep default values unchanged, usually `open a specified page within the app` with default configuration.
 >
 > If you need to use the report statistics feature, keep this item unchanged.
 >
 
 【Xiaomi】
-| Vendor Push Platform | Chat Console Configuration |
-| --- | --- |
-|  |  |
 
 【Huawei】
 | Vendor Push Platform | Chat Console Configuration |
@@ -114,14 +107,8 @@ Sign in to the [Chat console](https://console.trtc.io/chat/push-plugin-push-iden
 |  | <strong>Note:</strong><br>Client ID corresponds to AppID, and Client Secret corresponds to AppSecret. |
 
 【OPPO】
-| Vendor Push Platform | Chat Console Configuration |
-| --- | --- |
-|  |  |
 
 【vivo】
-| Vendor Push Platform | Chat Console Configuration |
-| --- | --- |
-|  |  |
 
 **Receipt configuration**
 
@@ -139,9 +126,6 @@ Sign in to the [Chat console](https://console.trtc.io/chat/push-plugin-push-iden
 - China: https://api.im.qcloud.com/v3/offline_push_report/vivo
 
 【Meizu】
-| Vendor Push Platform | Chat Console Configuration |
-| --- | --- |
-|  |  |
 
 **Receipt configuration**
 
@@ -160,10 +144,6 @@ Sign in to the [Chat console](https://console.trtc.io/chat/push-plugin-push-iden
 
 【Honor】
 
-| Vendor Push Platform | Chat Console Configuration |
-| --- | --- |
-|  |  |
-
 #### Receipt configuration
 
 **Receipt Address:**
@@ -181,6 +161,3 @@ Sign in to the [Chat console](https://console.trtc.io/chat/push-plugin-push-iden
 
 【Google FCM】
 
-| Vendor Push Platform | Chat Console Configuration |
-| --- | --- |
-|  |  |

package/resource/knowledge/push/integration/android.md

@@ -1,5 +1,4 @@
 > **Note:**
->
 > If you need to use products such as Chat, CallKit, RoomKit, LiveKit, etc. simultaneously, please refer to [Chat Quick Integration Solution](https://www.tencentcloud.com/document/product/1047/50034).
 >
 
@@ -7,10 +6,6 @@
 
 After completing the console manufacturer push information, download and add the configuration file to the project. Add the downloaded timpush-configs.json file to the assets directory of the application module:
 
-|1.Choose to download the configuration file timpush-configs.json|2.Add to the project|
-|---------|---------|
-|||
-
 ### Step 2: Integrate TIMPush
 ``` java
 // The version number "VERSION" can be obtained from the .
@@ -244,7 +239,6 @@ Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/huawei
 China: https://api.im.qcloud.com/v3/offline_push_report/huawei
 
 > **Note:**
->
 > Huawei Push Certificate ID <= 11344, using Huawei Push v2 interface, does not support Reach and Click Receipt, please regenerate and update Certificate ID.
 >
 
@@ -271,10 +265,6 @@ China: https://api.im.qcloud.com/v3/offline_push_report/honor
 
 【Meizu】
 
-|Enable Receipt Switch|Configure Receipt Address|
-|---------|---------|
-|||
-
 Receipt Address:
 
 Singapore : https://apisgp.im.qcloud.com/v3/offline_push_report/meizu
@@ -290,12 +280,10 @@ Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/meizu
 China: https://api.im.qcloud.com/v3/offline_push_report/meizu
 
 > **Note:**
->
 > After turning on the receipt toggle, please make sure the receipt address is correctly configured. Not configuring it or configuring the wrong address will affect the push notification feature.
 >
 
 > **Note:**
->
 > - No configuration for message delivery statistics is required for other supported manufacturers.
 > - FCM currently does not support the push notification statistics feature.
 
@@ -316,7 +304,6 @@ After receiving the push message, clicking the notification bar will trigger the
 【Custom click redirect implementation】
 
 > **Note:**
->
 > 1. It is recommended to place the registration callback timing in the onCreate() function of the application.
 > 2. Console configuration follow-up actions are configured as follows, select **Open the specified interface within the app** and do not modify, use the default values.
 >
@@ -337,7 +324,6 @@ TIMPushManager.getInstance().addPushListener(new TIMPushListener() {
 The component will notify the application in the form of a callback or broadcast, and the application can configure the app's page jump in the callback.
 
 > **Note:**
->
 > 1. It is recommended to place the registration callback timing in the onCreate() function of the application.
 > 2. Console configuration follow-up actions are configured as follows, select **Open the specified interface within the app** and do not modify, use the default values.
 >