@tencent-rtc/mcp 1.6.4 → 1.6.6

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

@@ -0,0 +1,123 @@
+## TIMPush - PushManager
+
+PushManager: Push Plugin Interface class
+
+### API Overview
+
+#### Register/Unregister Push Service API
+
+|API|Description|
+|---------|---------|
+|RegisterPush|Register push service (this API must be called to use push service only after the App user consents to the privacy policy).|
+|UnRegisterPush|Disable push service.|
+|SetRegistrationID|RegistrationID is the unique identifier of the push reception device. By default, it is automatically generated when push service registration succeeds, and you can also customize settings. Based on RegistrationID, you can push messages to the specified device. Notably, Uninstall and reinstall the device will change RegistrationID, so you need to call the setRegistrationID API before registering push service.|
+|GetRegistrationID|After successfully registering push service, you can obtain the unique identifier ID of the push reception device, namely RegistrationID, by calling the getRegistrationID API. Based on RegistrationID, you can push messages to the specified device.|
+
+#### Global Listening Interface for Push
+
+|API|Description|
+|---------|---------|
+|AddPushListener|Add a Push Listener.|
+|RemovePushListener|Remove a Push Listener.|
+
+#### Custom Configuration API
+
+|API|Description|
+|---------|---------|
+|ForceUseFCMPushChannel|Specify device offline push to use FCM channel, need to register push service before calling.|
+|DisablePostNotificationInForeground|Disable pop-up notifications when the App is in the foreground.|
+
+### API Detail
+
+#### Static Public Member Function
+
+static PushManager* GetInstance(): Get the PushManager manager instance.
+
+#### Member Function Description
+
+##### virtual void RegisterPush(int sdkAppId, const FString& appKey, PushValueCallback<FString>* callback) = 0;
+
+To register the push service, transmit both parameters sdkAppId and appKey, and just register the push service.
+
+Parameter description:
+| Parameter | Description | Access Path |
+| --- | --- | --- |
+| sdkAppId | The IM console assigned the app ID to you. |  |
+| appKey | The IM console assigned the client key to you. |  |
+
+##### virtual void UnRegisterPush(PushCallback* callback) = 0;
+
+Unregister and disable push service.
+
+##### virtual void SetRegistrationID(const FString& registrationID, PushCallback* callback) = 0;
+
+Set the push ID flag used for push service registration, i.e., RegistrationID, which needs to be called before registering the push service.
+
+Parameter description:
+
+|Parameter|Description|
+|---------|---------|
+|registrationID|The push unique identifier ID of the device may change after uninstall reinstall.|
+
+##### virtual void GetRegistrationID(PushValueCallback<FString>* callback) = 0;
+
+After successful registration of push service, obtain the push ID flag, i.e., RegistrationID.
+
+##### virtual void AddPushListener(PushListener* listener) = 0;
+
+Add a Push Listener
+
+##### virtual void RemovePushListener(PushListener* listener) = 0;
+
+Remove a Push Listener
+
+##### virtual void ForceUseFCMPushChannel(bool enable) = 0;
+
+Specify device offline push to use FCM channel, need to register push service before calling.
+
+Parameter description:
+| Parameter | Description |
+| --- | --- |
+| enable | - true: Use the FCM channel.<br>- false: Use the local machine channel. |
+
+##### virtual void DisablePostNotificationInForeground(bool disable) = 0;
+
+Disable pop-up notifications in the Notification bar when the App is in the foreground. When the Push SDK receives an online push, it automatically adds a Notification prompt to the Notification bar. If you want to handle online push messages yourself, you can call this API to disable the automatic pop-up Notification bar feature.
+
+Parameter description:
+| Parameter | Description |
+| --- | --- |
+| disable | - true: It is disabled.<br>- false: It is enabled. |
+
+## PushListener
+
+PushListener: Push Listener class
+
+### API Overview
+
+|API|Description|
+|---------|---------|
+|OnRecvPushMessage|Push message received.|
+|OnRevokePushMessage|Push message recall notification received.|
+|OnNotificationClicked|Click notification bar message Webhook.|
+
+### API Detail
+
+#### Member Function Description
+
+##### virtual void OnRecvPushMessage(const PushMessage& message) {}
+
+Push message received. Message received.
+
+##### virtual void OnRevokePushMessage(const FString& messageID) {}
+
+Push message recall notification received. messageID: unique message identifier.
+
+##### virtual void OnNotificationClicked(const FString& ext) {}
+
+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

@@ -17,7 +17,6 @@ Explanation of the **Subsequent Actions** option:
 
    > **Note：**
    >
-
    > Each vendor only supports the configuration of one certificate.
    >
 
@@ -68,13 +67,12 @@ For receipt configuration, please refer to: [Message Delivery Statistics Configu
 
    > **Note:**
    >
-
    > Regarding **Click for Subsequent Actions** supports the Report Statistics feature:
    >
->   1. If you choose to open an app or a web page, purchasing the plugin will by default support reporting statistics.
->   2. If you choose to open a specified interface within the application:
->   - For new certificate status, please directly use the auto-fill default value to support click statistics reporting.
->   - If there was a certificate configured previously, continue using the old certificate and modify it to the default value to support reporting statistics, or regenerate a new certificate.
+   > 1. If you choose to open an app or a web page, purchasing the plugin will by default support reporting statistics.
+   > 2. If you choose to open a specified interface within the application:
+   > - For new certificate status, please directly use the auto-fill default value to support click statistics reporting.
+   > - If there was a certificate configured previously, continue using the old certificate and modify it to the default value to support reporting statistics, or regenerate a new certificate.
 
 ### About FCM Data Messaging
 
@@ -87,6 +85,5 @@ FCM provides two push methods: Notification Message and Data Messaging.
 
    > **Note:**
    >
-
    > FCM data messaging capability only supports TIMPush version 7.8 and above on pixel phones. Other manufacturers' devices need to be tested for support.
    >

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

@@ -1,6 +1,5 @@
 > **Note:**
 >
-
 > Each vendor only supports the configuration of one certificate.
 >
 
@@ -22,7 +21,6 @@
 
       > **Note:**
       >
-
       > Certificate request file (CSR) need to be applied for in DevEco Studio. For details, see [generate certificate request file](https://developer.huawei.com/consumer/cn/doc/harmonyos-guides/ide-signing#section462703710326).
       >
 
@@ -38,7 +36,6 @@
 
       > **Note:**
       >
-
       > Note: For how to obtain UDID for different device types, please refer to [UDID Retrieval Method](https://developer.huawei.com/consumer/cn/doc/app/agc-help-add-device-0000001946142249#section67331926102911).
       >
 

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

@@ -7,7 +7,6 @@ If you have any questions about the "Developer Account" or "Develop/Distribute C
 
 > **Note：**
 >
-
 > Each vendor only supports the configuration of one certificate.
 >
 
@@ -30,7 +29,6 @@ Apple currently offers two mainstream types of certificates for vendor configura
 
    > **Note:**
    >
-
    >  Your App's `Bundle ID` cannot use a wildcard `*`, otherwise, remote push service will not be available.
    >
 
@@ -47,9 +45,7 @@ Apple currently offers two mainstream types of certificates for vendor configura
 
 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.
+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`).
 
@@ -65,17 +61,15 @@ First, we choose the Development **Create Certificate**; the system will prompt
 
    > **Note:**
    >
-
    > Actually, this certificate is a Sandbox and Production merged certificate that applies to both the development and production environments.
    >
 
 10. Double-click the downloaded `SSL Certificate` for the development and production environments. The system will import it into the keychain.
 
-11. Open the Keychain Access app, go to ** log in to  **> **My Certificates**, right-click to export the recently created development environment (`Apple Development IOS Push Service`) and production environment (`Apple Push Services`)  `p12`  files.
+11. Open the Keychain Access app, go to  **log in to**  > **My Certificates**, right-click to export the recently created development environment (`Apple Development IOS Push Service`) and production environment (`Apple Push Services`)  `p12`  files.
 
    > **Note:**
    >
-
    > When saving the `.p12` file, be sure to set a password. Step 2: Upload the certificate to the console.
    >
 
@@ -90,13 +84,13 @@ First, we choose the Development **Create Certificate**; the system will prompt
 
    > **Note:**
    >
->   - When uploading the push certificate, make sure that the Bundle ID matches the Bundle ID of your main app.
->   - 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.
->   - The uploaded .p12 certificate must be your own authentic and valid certificate.
+   > - When uploading the push certificate, make sure that the Bundle ID matches the Bundle ID of your main app.
+   > - 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.
+   > - The uploaded .p12 certificate must be your own authentic and valid certificate.
 
-5. After the push certificate information is generated, record the certificate** ID**.
+5. After the push certificate information is generated, record the certificate **ID**.
 
 ### Method 2: Use a p8 certificate (supports Dynamic Island Push)
 
@@ -116,10 +110,8 @@ To create a p8 certificate file, you first need to log in to the [Apple Develope
 
    > **Note:**
    >
-
    > The p8 certificate can only be downloaded once, so please keep it safe.
    >
-
    > Please keep the downloaded p8 file safe, as you will not be able to download it again. You can use this P8 certificate to configure your iOS application to receive push notifications.
    >
 
@@ -136,9 +128,9 @@ To create a p8 certificate file, you first need to log in to the [Apple Develope
 
    > **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, the system generates a Key ID 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 in the Apple Developer Center. Click "Membership" in the top right corner, and you will find your Team ID in the "Membership Details" section.
->   - **BundleID**: This is the unique identifier for your application, also known as the Application 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 application list.
+   > - **KeyID**: This is the unique identifier for your APNs Auth Key. When you create a new APNs Auth Key in the Apple Developer Center, the system generates a Key ID 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 in the Apple Developer Center. Click "Membership" in the top right corner, and you will find your Team ID in the "Membership Details" section.
+   > - **BundleID**: This is the unique identifier for your application, also known as the Application 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 application list.
 
 ##
 1. Create a Description File
@@ -198,7 +190,7 @@ To create a p8 certificate file, you first need to log in to the [Apple Develope
 
 ### To add push permissions to the app, enable the push notification feature in the Xcode project.
 
-Open  **Xcode**  project, navigate to the  Project > Target > Capabilities  page, click the plus button in the red box, and then select and add  **Push Notifications **.
+Open  **Xcode**  project, navigate to the  Project > Target > Capabilities  page, click the plus button in the red box, and then select and add  **Push Notifications** .
 
 The result after adding is shown in the red box in the figure.
 

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

@@ -2,7 +2,6 @@ React Native push currently supports vendor channels such as Xiaomi, Huawei, Hon
 
 > **Note:**
 >
-
 > Each vendor only supports the configuration of one certificate.
 >
 
@@ -26,13 +25,12 @@ There are currently two mainstream types of certificates for Apple Manufacturer
 
 2. click the **+** next to Identifiers.
 
-3. You can follow the steps below to create a new AppID or add a `Push Notification``Service` to your existing AppID.
+3. You can follow the steps below to create a new AppID or add a `Push Notification` `Service` to your existing AppID.
 
-> **Note:**
->
-
->  Your App's `Bundle ID` cannot use the wildcard `*`, otherwise, the remote push service cannot be used.
->
+   > **Note:**
+   >
+   >  Your App's `Bundle ID` cannot use the wildcard `*`, otherwise, the remote push service cannot be used.
+   >
 
 4. Check the **App IDs** box, click **Continue** to proceed to the next step.
 
@@ -47,9 +45,7 @@ There are currently two mainstream types of certificates for Apple Manufacturer
 
 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).
+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`).
 
@@ -63,21 +59,19 @@ We first select the **Create Certificate** for the Development environment, the
 
 9. Repeat steps 1 - 8 above to download the `Production SSL Certificate` for the production environment to your local machine.
 
-> **Note:**
->
-
-> The certificate for the production environment is actually a combined certificate of Development (Sandbox) + Production, and it can be used as a certificate for both the development and production environments.
->
+   > **Note:**
+   >
+   > The certificate for the production environment is actually a combined certificate of Development (Sandbox) + Production, and it can be used as a certificate for both the development and production environments.
+   >
 
 10. Double-click the downloaded `SSL Certificate` for the development and production environments. The system will import it into the keychain.
 
 11. Open the Keychain App, go to **log in to** > **My Certificates**, right-click to export the newly created `Apple Development IOS Push Services` and `Apple Push Services` for the development and production environments as `p12` files respectively.
 
-> **Note**
->
-
->  Note: Set the password when saving the `.p12` file.
->
+   > **Note**
+   >
+   >  Note: Set the password when saving the `.p12` file.
+   >
 
 ### Step 2: Upload the certificate to the console
 1. Log in to the [Chat Console](https://console.trtc.io/chat/push-plugin-push-identifier).
@@ -111,10 +105,10 @@ To create a p8 certificate file, first log in to [Apple Developer Center](https:
 
 Confirm and generate the key: On the confirmation page, verify your key information, then click **Register**. Next, you'll see a page prompting you to download the key. Click **Download** and save the generated .p8 file to your computer.
 
-> **Note:**
->
-> - The p8 certificate can only be downloaded once; please save it properly.
-> - Please safeguard the downloaded p8 file, as you will not be able to download it again. You can use this p8 certificate to configure your iOS applications to receive push notifications.
+   > **Note:**
+   >
+   > - The p8 certificate can only be downloaded once; please save it properly.
+   > - Please safeguard the downloaded p8 file, as you will not be able to download it again. You can use this p8 certificate to configure your iOS applications to receive push notifications.
 
 ### Step 2: Upload the p8 certificate to the Chat console
 1. Log in to the [Chat Console](https://console.trtc.io/chat/push-plugin-push-identifier).
@@ -145,10 +139,8 @@ Log in to Tencent Cloud [Chat Console](https://console.trtc.io/chat/push-plugin-
 
 > **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)
 >
 

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

@@ -2,7 +2,6 @@ Currently, the message push plugin in Unity only supports push to Android (inclu
 
 > **Note:**
 >
-
 > Each vendor only supports the configuration of one certificate.
 >
 
@@ -19,13 +18,12 @@ 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.
-
-> **Note**
->
+3. You can refer to the following procedure to create a new AppID, or add the `Push Notification` `Service` to your original AppID.
 
->  Note: The `Bundle ID` of your App cannot use wildcard `*`, otherwise the Remote Push Service will be unavailable.
->
+   > **Note**
+   >
+   >  Note: The `Bundle ID` of your App cannot use wildcard `*`, otherwise the Remote Push Service will be unavailable.
+   >
 
 4. Check **App IDs**, click **Continue** to proceed to the next step.
 
@@ -40,9 +38,7 @@ Before integrating the message push plug-in, you must apply for an APNs Push Cer
 
 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).
+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`).
 
@@ -56,21 +52,19 @@ First select the development environment (Development) **Create Certificate**, t
 
 9. Repeat steps 1 - 8 to download the `Production SSL Certificate` for the production environment to local.
 
-> **Note**
->
-
-> The certificate in the production environment is a merged certificate of development (Sandbox) and production (Production), which can be used as both a development and production environment certificate.
->
+   > **Note**
+   >
+   > The certificate in the production environment is a merged certificate of development (Sandbox) and production (Production), which can be used as both a development and production environment certificate.
+   >
 
 10. Double-click to open the downloaded `SSL Certificate` for the development and production environment, and the system will import it into the keychain.
 
 11. Open the keychain access app, go to **Login** > **My Certificates**, right-click to export the newly created `P12` files for the development environment (`Apple Development IOS Push Service`) and production environment (`Apple Push Services`).
 
-> **Note**
->
-
-> When saving the `P12` file, ensure to set a password for it.
->
+   > **Note**
+   >
+   > When saving the `P12` file, ensure to set a password for it.
+   >
 
 ### Step 2: Upload Certificate to Console
 1. Log in to the [Chat console](https://console.trtc.io/chat/push-plugin-push-identifier).
@@ -81,12 +75,12 @@ First select the development environment (Development) **Create Certificate**, t
 
 4. Select certificate type, upload iOS certificate (.p12), set certificate password, click **confirm**.
 
-> **Note**
->
-> - Upload certificate name should be in English (do not use parentheses or other special characters).
-> - Upload certificate needs to be set with password. Passwordless will not receive push notifications.
-> - Set the certificate for App Store release to production environment, otherwise unable to receive push notifications.
-> - Uploaded p12 certificate must be your own real and valid applied certificate.
+   > **Note**
+   >
+   > - Upload certificate name should be in English (do not use parentheses or other special characters).
+   > - Upload certificate needs to be set with password. Passwordless will not receive push notifications.
+   > - Set the certificate for App Store release to production environment, otherwise unable to receive push notifications.
+   > - Uploaded p12 certificate must be your own real and valid applied certificate.
 
 5. After generation of pending certificate information, record the cert ID.
 
@@ -104,10 +98,8 @@ Log in to Tencent Cloud [Chat console](https://console.trtc.io/chat/push-plugin-
 
 > **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.
 >
 

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

@@ -2,7 +2,6 @@ The push service currently supports Vendor Channels such as Xiaomi, Huawei, Hono
 
 > **Note:**
 >
-
 > Each vendor only supports the configuration of one certificate.
 >
 
@@ -19,13 +18,12 @@ 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.
-
-> **Note**
->
+3. You can refer to the following steps to create a new AppID or add the `Push Notification` `Service` to your original AppID.
 
->  Note: Your App's `Bundle ID` cannot use wildcard `*`, otherwise Remote Push Service will be unavailable.
->
+   > **Note**
+   >
+   >  Note: Your App's `Bundle ID` cannot use wildcard `*`, otherwise Remote Push Service will be unavailable.
+   >
 
 4. Check **App IDs**, then click **Continue** to proceed to the next step.
 
@@ -40,9 +38,7 @@ Before integrating the message push plug-in, you must apply for an APNs Push Cer
 
 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).
+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`).
 
@@ -56,21 +52,19 @@ First select the development environment (Development) **Create Certificate**, t
 
 9. Repeat steps 1-8 to download the `Production SSL Certificate` for the production environment locally.
 
-> **Note**
->
-
-> Note: The cert in the production environment is actually a merged certificate of Sandbox and Production, which can be used as the cert for both development and production environments.
->
+   > **Note**
+   >
+   > Note: The cert in the production environment is actually a merged certificate of Sandbox and Production, which can be used as the cert for both development and production environments.
+   >
 
 10. Double-click to open the downloaded `SSL Certificate` for development and production environments, and the system will import it into the Keychain.
 
-11. Open the keychain access app, go to **Login** > **My Certificates**, right-click and export the newly created `Apple Development IOS Push Service` and `Apple Push Services``P12` files for development and production environments respectively.
-
-> **Note**
->
+11. Open the keychain access app, go to **Login** > **My Certificates**, right-click and export the newly created `Apple Development IOS Push Service` and `Apple Push Services` `P12` files for development and production environments respectively.
 
-> When saving a `P12` file, ensure to set password for it.
->
+   > **Note**
+   >
+   > When saving a `P12` file, ensure to set password for it.
+   >
 
 ### Step 2: Upload Certificate to Console
 1. Sign in to the [Chat Console](https://console.trtc.io/chat/push-plugin-push-identifier).
@@ -81,12 +75,12 @@ First select the development environment (Development) **Create Certificate**, t
 
 4. Select certificate type, upload iOS certificate (.p12), set certificate password, click **confirm**.
 
-> **Note**
->
-> - Use English for the certificate name (do not use parentheses or other special characters).
-> - Upload certificate needs to be set with password. Passwordless will not receive push notifications.
-> - To publish an App Store certificate, set it to production environment, otherwise unable to receive push.
-> - Uploaded p12 certificate must be a real and valid certificate applied by yourself.
+   > **Note**
+   >
+   > - Use English for the certificate name (do not use parentheses or other special characters).
+   > - Upload certificate needs to be set with password. Passwordless will not receive push notifications.
+   > - To publish an App Store certificate, set it to production environment, otherwise unable to receive push.
+   > - Uploaded p12 certificate must be a real and valid certificate applied by yourself.
 
 5. After generation of pending certificate information, record the cert ID.
 
@@ -104,10 +98,8 @@ Sign in to the [Chat console](https://console.trtc.io/chat/push-plugin-push-iden
 
 > **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.
 >
 

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

@@ -1,6 +1,5 @@
 > **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).
 >
 
@@ -71,7 +70,6 @@ android {
 
    > **Note:**
    >
-
    > The following adaptation for HONOR only requires configuration for version 7.7.5283 and above.
    >
 
@@ -247,7 +245,6 @@ 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.
 >
 
@@ -294,7 +291,6 @@ 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.
 >
 
@@ -323,6 +319,7 @@ After receiving the push message, clicking the notification bar will trigger the
 >
 > 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.
+>
 
 ``` java
 TIMPushManager.getInstance().addPushListener(new TIMPushListener() {
@@ -341,8 +338,9 @@ The component will notify the application in the form of a callback or broadcast
 
 > **Note:**
 >
-> 3. It is recommended to place the registration callback timing in the onCreate() function of the application.
-> 4. 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.
+> 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.
+>
 
 1. The callback method is as follows:
 
@@ -400,5 +398,5 @@ Vendor offline push channels use a [message categorization mechanism](https://tr
 
    > **Note:**
    >
->   1. If you are unable to receive push notifications after integration, please first use the [Troubleshooting Tool](https://trtc.io/document/60541) to check the specific reasons. To view push indicator data, please use [Statistics](https://trtc.io/document/60540) query.
->   2. For the All/Tag Push feature, please refer to: [RESTful APIs - Initiate All/Tag Push](https://trtc.io/document/60561).
+   > 1. If you are unable to receive push notifications after integration, please first use the [Troubleshooting Tool](https://trtc.io/document/60541) to check the specific reasons. To view push indicator data, please use [Statistics](https://trtc.io/document/60540) query.
+   > 2. For the All/Tag Push feature, please refer to: [RESTful APIs - Initiate All/Tag Push](https://trtc.io/document/60561).