npm - @tencent-rtc/mcp - Versions diffs - 1.6.6 → 1.6.8 - Mend

@tencent-rtc/mcp 1.6.6 → 1.6.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (248) hide show

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

@@ -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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -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.
 >

package/resource/knowledge/push/integration/flutter.md CHANGED Viewed

@@ -13,8 +13,6 @@ flutter pub add tencent_cloud_chat_push
 Please upload the iOS APNs push certificate you obtained in the manufacturer configuration step to the Chat console.
-The Chat console will allocate a Certificate ID for you, see the image below:
 To register for push notifications, you need to pass in this Certificate ID (apnsCertificateID):
 ``` java
 TencentCloudChatPush().registerPush(apnsCertificateID: Your configured Certificate ID);
@@ -24,10 +22,6 @@ TencentCloudChatPush().registerPush(apnsCertificateID: Your configured Certifica
 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 `android/app/src/main/assets` directory of the project. If the directory does not exist, please create it manually.
-|1.Choose to download the configuration file timpush-configs.json|2.Add to the project|
-|---------|---------|
-|||
 ### Step 3: Client Code Configuration
 In this step, you will need to write some native code, such as Swift, Java, XML, etc.
@@ -38,8 +32,6 @@ Please do not worry. Just follow the instructions and copy the provided code int
 You can edit using Xcode, or directly in Visual Studio Code or Android Studio.
-Open the `ios/Runner/AppDelegate.swift` file, paste the highlighted code as shown in the image below. The code is attached after the image.
 ``` swift
 import UIKit
 import Flutter
@@ -83,7 +75,6 @@ import tencent_cloud_chat_push
 ```
 > **Note:**
->
 > 1. For the iOS console, please set the certificate ID to use businessID. The offlinePushCertificateID is deprecated.
 > 2. The old field offlinePushCertificateID is still supported, but you need to add the @objc keyword.
@@ -110,12 +101,9 @@ public class MyApplication extends TencentCloudChatPushApplication {
 ```
 > **Note:**
->
 > If you have already created your own Application for other purposes, directly `extend TencentCloudChatPushApplication` and ensure that the `onCreate()` function calls `super.onCreate();`.
 >
-Open the `android/app/src/main/AndroidManifest.xml` file and add an `<application>` tag to specify an `android:name` parameter, pointing to the custom `Application` class you just created. As shown in the figure:
 ### Step 4: Client Manufacturer Configuration
 【iOS】
@@ -325,7 +313,6 @@ If you need to customize the parsing of received remote push notifications, you
 【Custom click redirect implementation】
 > **Note:**
->
 > 1. It is recommended to register the callback in the main() function at the program entry.
 > 2. For console configuration, click on 'Subsequent Actions' and configure as follows, choose **Open the specified interface within the app**, and the plugin users will by default fill in the jump parameters.
 >
@@ -398,7 +385,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.
 >
@@ -425,10 +411,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
@@ -444,7 +426,6 @@ 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.
 >

package/resource/knowledge/push/integration/harmonyos.md CHANGED Viewed

@@ -41,7 +41,6 @@ For detailed API instructions, see RESTful APIs - Initiate Push to All Users/Tag
 After receiving the push message and clicking the notification, the component will Webhook the click event and offline message pass-through.
 > **Note:**
->
 > - Register the callback timing in the oncreate() function of the application [UIAbility](https://developer.huawei.com/consumer/cn/doc/harmonyos-guides/uiability-lifecycle).
 > - Console configuration click subsequent actions with the following configuration, select **open specified in-app page**, do not modify use default values.
 >
@@ -59,6 +58,5 @@ TIMPushManager.getInstance().addPushListener(pushListener);
 Congratulations on completing the Push Plugin access. Remind you: **After trial or purchase expiry, the Push Plugin will automatically stop providing push service (including offline push for regular messages, Tag Push, etc.)**. To avoid affecting normal business operation, please [proceed to purchase](https://buy.tencentcloud.com/avc) or [renew](https://buy.tencentcloud.com/avc) in advance.
 > **Note:**
->
 > - Integration completed but not receiving push notifications? Please first use the [troubleshooting tool](https://cloud.tencent.com/document/product/269/100629) to check the reason. To view push metrics data, use [data statistics](https://cloud.tencent.com/document/product/269/100628) for querying.
 > - For push notification feature to all users/Tag Push, please refer to: [RESTful APIs - Initiate Push to All Users/Tag Push](https://cloud.tencent.com/document/product/269/100634).

package/resource/knowledge/push/integration/ios.md CHANGED Viewed

@@ -1,5 +1,4 @@
 > **Note:**
->
 > If you need to use products like Chat, CallKit, RoomKit, LiveKit simultaneously, please refer to [Chat Quick Integration Solution](https://www.tencentcloud.com/document/product/1047/50033).
 >
@@ -27,7 +26,6 @@
    ```
 ### Step 2: Set push parameters
-1. After you upload a certificate to the Chat console, the Chat console will assign a certificate ID to you, as shown below.
 2. You need to implement the `- businessID` protocol method in AppDelegate to return the certificate ID.
@@ -168,7 +166,6 @@ If you need to customize the parsing of received remote push notifications, you
 【Custom click redirect implementation】
 > **Note:**
->
 > It is recommended to place the registration callback timing in the didFinishLaunchingWithOptions function of the AppDelegate.
 >

package/resource/knowledge/push/integration/react-native.md CHANGED Viewed

@@ -24,7 +24,6 @@ yarn add @tencentcloud/react-native-push
 Copy the following code to `App.tsx` and replace `SDKAppID` and `appKey` with your application's information.
 > **Note:**
->
 > After successfully registering the push service with `registerPush`, you can obtain the push ID, namely RegistrationID, through `getRegistrationID`. You can push messages to the specified RegistrationID.
 >
@@ -74,7 +73,6 @@ if (Push) {
 ### Step 4: Configuring Vendor Push
 【Android】
-1. After completing the vendor push information in the console, download the `timpush-configs.json` file from the console and add it to the `MyReactNativeApp/android/app/src/main/assets` directory of the project. If this directory does not exist, please create it manually. As shown in the figure:
 2. Huawei, HONOR, vivo, FCM.
@@ -85,7 +83,6 @@ When you need to support FCM push, you must configure the  `google-services.json
 【Huawei】
 【HONOR】
-1. To support HONOR Push, you need to configure `appID` in the `MyReactNativeApp/android/app/build.gradle` file. As shown in the figure:
 ``` bash
 ......
@@ -100,15 +97,10 @@ android {
 }
 ```
-|Obtain HONOR appID|Configure HONOR appID|
-|---------|---------|
-|||
 2. Download the `mcs-services.json` file from the [Honor Developer Management Center](https://developer.honor.com/en/), and configure it in the `MyReactNativeApp/android/app` directory (**Please note! Not in the** `MyReactNativeApp/android/app/src/main/assets directory` directory).
 【vivo】
-To support vivo Push, you need to configure `appID` and `appKey` in the `MyReactNativeApp/android/app/build.gradle` file. As shown in the figure:
 ``` bash
 ......
 android {
@@ -123,14 +115,7 @@ android {
 }
 ```
-|Obtain vivo appID && appKey|Configure vivo appID && appKey|
-|---------|---------|
-|||
 【iOS】
-1. Please upload the iOS APNs Push Certificate obtained in the manufacturer configuration step to the Chat Console. The Chat Console will assign a Certificate ID to you, as shown in the figure:
-2. In the `MyReactNativeApp/ios/MyReactNativeApp` directory, create a new `Resources` folder and a new `timpush-configs.json` file. Edit `timpush-configs.json` and enter the certificate ID obtained from the console, as shown below:
 ``` javascript
 {
@@ -138,14 +123,11 @@ android {
 }
 ```
-3. Open the MyReactNativeApp project in XCode, right-click the project > **Add Files to "MyReactNativeApp"**, and add the `timpush-configs.json` directory to the project. As shown in the figure:
 ### Step 5: **Configuring Native Modules and Dependencies**
 【Android】
 > **Note:**
->
 > Please ensure the package name in `timpush-configs.json` matches the `applicationId` value in `MyReactNativeApp/android/app/build.gradle`. Inconsistency will result in offline push notifications being unavailable.
 >
@@ -307,7 +289,6 @@ If you need to collect data on delivery, please complete the setup as follows:
 - China: https://api.im.qcloud.com/v3/offline_push_report/huawei
 > **Note:**
->
 > Huawei Push Certificate ID <= 11344, using Huawei Push v2 version interface does not support reach and click receipt, please regenerate and update the certificate ID.
 >
@@ -333,10 +314,6 @@ If you need to collect data on delivery, please complete the setup as follows:
 【Meizu】
-|Enable Receipt Switch|Configure Receipt Address|
-|---------|---------|
-|||
 **Receipt Address:**
 - Singapore : https://apisgp.im.qcloud.com/v3/offline_push_report/meizu
@@ -351,7 +328,6 @@ If you need to collect data on delivery, please complete the setup as follows:
 - China: https://api.im.qcloud.com/v3/offline_push_report/meizu
 > **Note:**
->
 > After enabling the Receipt Switch, please make sure the Receipt Address is configured correctly. Failing to configure or configuring the wrong address will affect the push feature.
 >

package/resource/knowledge/push/integration/uni-app.md CHANGED Viewed

@@ -16,7 +16,6 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
 ### Step 2. Offline push configuration
 > **Note:**
->
 > 1. HBuilderX 4.36 has released non-backward compatible updates. If you are using HBuilderX 4.36 or higher and need vendor push for vivo/Honor, please upgrade the push version to 1.1.0 or higher and refer to the documentation to correctly configure `manifestPlaceholders.json` and `mcs-services.json`.
 > 2. You need to configure push notifications in the `nativeResources` directory. If this folder is not yet created in the project root directory, please create a new folder named `nativeResources`.
 > 3. Ensure that the `nativeResources` directory exists in the project opened with HBuilderX and is at the same level as the `uni_modules` directory.
@@ -24,12 +23,9 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
 【Android】
 1. Create the directory `nativeResources/android/assets`.
-2. Configure `timpush-configs.json` (download from [Push Service > Access Settings > One-click Quick Configuration](https://console.trtc.io/chat/push-plugin-push-identifier)) to the `nativeResources/android/assets/` directory. As shown in the figure:
 3. Huawei, HONOR, vivo, FCM.
 【FCM】
-1. Configure `com.google.gms.google-services` to `uni_modules/TencentCloud-Push/utssdk/app-android/config.json`  in `project.plugins`, as shown below:
 ``` json
 "project": {
@@ -45,8 +41,6 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
 }
 ```
-2. Configure the `google-services.json` file to the `nativeResources/android/` directory (Note! Do not configure it to the `nativeResources/android/assets`  directory). As shown in the figure:
 【Huawei】
 【HONOR】
@@ -97,8 +91,6 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
 2. Create a `timpush-configs.json` file in `nativeResources/ios/Resources`.
-3. Add the certificate ID obtained from [Chat Console > Push Service > Access Settings](https://console.trtc.io/chat/push-plugin-push-identifier) to the `timpush-configs.json` file. As shown below:
 ``` json
 {
     "businessID":"xxx"
@@ -107,8 +99,6 @@ HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-a
 ### Step 3. Introduce and register Tencent Cloud Push Service (Push)
-Replace `SDKAppID` and `appKey` with the application information obtained from [Chat Console - Push Service - Access Settings page](https://console.trtc.io/chat/push-plugin-push-identifier). As shown in the figure:
 ``` javascript
 // Integration of TencentCloud-Push
 import * as Push from '@/uni_modules/TencentCloud-Push';
@@ -159,7 +149,7 @@ Before testing the push, please make sure to turn on notifications and the statu
 ## Push Result Callback
-After enabling the push service, the push results can be forwarded to the App backend by configuring basic callbacks. For details, see:
+After enabling the push service, the push results can be forwarded to the App backend by configuring basic callbacks.
 - [Normal push result callback](https://www.tencentcloud.com/document/product/1047/67553)
 - [All-member push result callback](https://www.tencentcloud.com/document/product/1047/60561)

package/resource/knowledge/push/integration/unity.md CHANGED Viewed

@@ -18,8 +18,6 @@ Adjust the `Packages/manifest.json` file and add relevant dependencies:
 Upload the iOS APNs Push Certificate obtained from the manufacturer configuration process to the Chat console.
-The Chat console will allocate a certificate ID for you, as shown below:
 You need to create file `UnityIMPush.mm` under the directory `Assets/Plugins/iOS` (if the directory does not exist, create it manually), and implement the `- businessID` protocol method in the file to return the certificate ID. See the implementation as follows:
 ``` objectivec
 #import "TPush/TPush.h"
@@ -244,7 +242,6 @@ apply plugin: 'com.hihonor.mcs.asplugin'
 If you need to customize the parsing of received remote push, you can implement it by the following method.
 > **Note:**
->
 > 1. Register the callback timing in the program entry function.
 > 2. Configure the console to click subsequent actions with the following configuration, select **open specified in-app page,** do not modify and use default values.
 >
@@ -266,7 +263,6 @@ PushManager.AddPushListener(listener);
 Upon success of calling the `PushManager.RegisterPush` method, you can receive offline push notifications.
 > **Note:**
->
 > Note: If you have already integrated the Chat product and call this API after successful log-in, set the appKey parameter to null. Otherwise, the Chat account will be taken offline.
 >
@@ -299,7 +295,6 @@ Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/huawei
 China: https://api.im.qcloud.com/v3/offline_push_report/huawei
 > **Note:**
->
 > Note: Huawei Push certificate ID <= 11344 uses Huawei Push v2 version interface with no support for reachability and Receipt Click. Please regenerate the certificate ID.
 >
@@ -325,9 +320,6 @@ China: https://api.im.qcloud.com/v3/offline_push_report/honor
 | Receipt Address:<br>Singapore :https://apisgp.im.qcloud.com/v3/offline_push_report/vivo<br>Korea:<br>https://apikr.im.qcloud.com/v3/offline_push_report/vivo<br>USA: https://apiusa.im.qcloud.com/v3/offline_push_report/vivo<br>Germany: https://apiger.im.qcloud.com/v3/offline_push_report/vivo<br>Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/vivo<br>China:<br>https://api.im.qcloud.com/v3/offline_push_report/vivo |  |
 【Meizu】
-| Enable Receipt Switch | Configure Receipt Address |
-| --- | --- |
-|  |  |
 Receipt Address:
@@ -344,7 +336,6 @@ Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/meizu
 China: https://api.im.qcloud.com/v3/offline_push_report/meizu
 > **Note:**
->
 > Note: After enabling the receipt switch, please ensure the receipt address is configured correctly. Without configuring or with an incorrect address, it will impact the push notification feature.
 >