@tencent-rtc/mcp 1.6.3 → 1.6.5

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

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

@@ -111,7 +111,6 @@ 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();`.
 >
 
@@ -189,11 +188,10 @@ android {
 
 Follow the vendor method to integrate the corresponding plugin and JSON configuration file.
 
-> **Note:**
->
-
-> The following adaptation for HONOR only requires configuration for version 7.7.5283 and above.
->
+   > **Note:**
+   >
+   > The following adaptation for HONOR only requires configuration for version 7.7.5283 and above.
+   >
 
   1. Download the configuration file and place it under the root directory/Android/app of the project.
 
@@ -330,6 +328,7 @@ If you need to customize the parsing of received remote push notifications, you
 >
 > 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.
+>
 
 ``` java
 TIMPushListener timPushListener = TIMPushListener(
@@ -369,7 +368,7 @@ void _onNotificationClicked({required String ext, String? userID, String? groupI
 
 **Please note, do not call in the main method of the Flutter program entry.**
 
-After successfully calling the `TencentCloudChatPush().registerPush` method, you can receive offline push notifications.
+After successfully calling the  `TencentCloudChatPush().registerPush` method, you can receive offline push notifications.
 ``` java
 TencentCloudChatPush().registerPush(
     onNotificationClicked: _onNotificationClicked,
@@ -400,7 +399,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.
 >
 
@@ -447,7 +445,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.
 >
 

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

@@ -44,6 +44,7 @@ After receiving the push message and clicking the notification, the component wi
 >
 > - 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.
+>
 
 ``` java
 let pushListener: TIMPushListener = {

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

@@ -1,6 +1,5 @@
 > **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).
 >
 
@@ -98,10 +97,10 @@ TIMPushManager.registerPush(Int32(sdkAppId), appKey: appKey, succ: { deviceToken
 })
 ```
 
-> **Note:**
->
-> 1. After you log in, when you see the APNs configuration success log printed on the console, it indicates that the integration is successful.
-> 2. If your app has obtained push permissions, you can receive remote push notifications when the app is moved to the background or the process is killed.
+   > **Note:**
+   >
+   > 1. After you log in, when you see the APNs configuration success log printed on the console, it indicates that the integration is successful.
+   > 2. If your app has obtained push permissions, you can receive remote push notifications when the app is moved to the background or the process is killed.
 
 ### Step 4: Push Delivery Rate Statistics
 1. If you need to collect data on push delivery and click rates, you need to implement the `- applicationGroupID` method in the `AppDelegate.m` file and get the App Group ID ([the generation method can be referred to in Vendor Configuration - Generating App Group ID](https://www.tencentcloud.com/document/product/1047/60548#ae5590eb-b974-4226-9f1b-720fb0201c85)).
@@ -148,9 +147,9 @@ override func didReceive(_ request: UNNotificationRequest, withContentHandler co
 
    > **Note:**
    >
->   3. To report push delivery data, enable the mutable-content switch to support iOS 10's extension feature.
-
->   4. Data details can be viewed on the Push Data Page. The Push Data Page can only be used after [purchasing the Push Plugin](https://buy.cloud.tencent.com/avc).
+   > 1. To report push delivery data, enable the mutable-content switch to support iOS 10's extension feature.
+   >
+   > 2. Data details can be viewed on the Push Data Page. The Push Data Page can only be used after [purchasing the Push Plugin](https://buy.cloud.tencent.com/avc).
 
 ### Step 5: **Verify Connection**
 
@@ -170,7 +169,6 @@ If you need to customize the parsing of received remote push notifications, you
 
 > **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

@@ -25,7 +25,6 @@ Copy the following code to `App.tsx` and replace `SDKAppID` and `appKey` with yo
 
 > **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.
 >
 
@@ -81,12 +80,12 @@ if (Push) {
 
 【FCM】
 
-When you need to support FCM push, you must configure the `google-services.json` file in the `MyReactNativeApp/android/app` directory (**Please note! Not in the **`MyReactNativeApp/android/app/src/main/assets directory`). As shown in the picture:
+When you need to support FCM push, you must configure the  `google-services.json` file in the `MyReactNativeApp/android/app` directory (**Please note! Not in the** `MyReactNativeApp/android/app/src/main/assets directory`). As shown in the picture:
 
 【Huawei】
 
 【HONOR】
-3. To support HONOR Push, you need to configure `appID` in the `MyReactNativeApp/android/app/build.gradle` file. As shown in the figure:
+1. To support HONOR Push, you need to configure `appID` in the `MyReactNativeApp/android/app/build.gradle` file. As shown in the figure:
 
 ``` bash
 ......
@@ -105,7 +104,7 @@ android {
 |---------|---------|
 |||
 
-4. 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).
+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】
 
@@ -129,9 +128,9 @@ android {
 |||
 
 【iOS】
-5. 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:
+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:
 
-6. 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:
+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
 {
@@ -139,7 +138,7 @@ android {
 }
 ```
 
-7. 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:
+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**
 
@@ -147,7 +146,6 @@ 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.
 >
 
@@ -264,16 +262,16 @@ dependencies {
 5. After completing the above steps, select **File > Sync Project with Gradle Files**.
 
 【iOS】
-6. Open **MyReactNativeApp/ios/MyReactNativeApp.xcworkspace** with XCode.
+1. Open **MyReactNativeApp/ios/MyReactNativeApp.xcworkspace** with XCode.
 
-7. Go to the `MyReactNativeApp/ios` directory and install TIMPush.
+2. Go to the `MyReactNativeApp/ios` directory and install TIMPush.
 
 ``` bash
 pod install
 # If you cannot install the latest version, run the following command to update your local CocoaPods repository list
 pod repo update
 ```
-8. Enable push notification feature in the app. Open the Xcode project, and select and add **Push Notifications** on the **Project > Target > Capabilities** page.
+3. Enable push notification feature in the app. Open the Xcode project, and select and add **Push Notifications** on the **Project > Target > Capabilities** page.
 
 ### Step 6: **Running on a Real Device (Make sure to enable notification permissions on your phone before testing, allowing the app to send notifications.)**
 
@@ -310,7 +308,6 @@ If you need to collect data on delivery, please complete the setup as follows:
 
 > **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.
 >
 
@@ -355,7 +352,6 @@ If you need to collect data on delivery, please complete the setup as follows:
 
 > **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.
 >