@tencent-rtc/mcp 1.6.7 → 1.6.8

package/resource/knowledge/livekit/core-sdk/live/flutter/integration.md

@@ -65,7 +65,6 @@ end
 Call `LoginStore.shared.login` in your project to log in. **This is the key premise for using all functions of AtomicXCore.**
 
 > **Important:**
->
 > It is recommended to call `LoginStore.shared.login` after successful log-in to your App's user account to ensure clear and consistent business logic.
 >
 
@@ -106,7 +105,6 @@ void main() async {
 Follow these steps to quickly set up host video streaming:
 
 > **Note:**
->
 > For a complete host streaming implementation, see [live_room_anchor_widget.dart](https://github.com/Tencent-RTC/TUIKit_Flutter/blob/main/live/livekit/lib/live_stream/features/live_room_anchor_widget.dart) in the TUILiveKit open-source project.
 >
 
@@ -343,7 +341,6 @@ Follow these steps to quickly set up host video streaming:
 Enable audience live viewing with these steps:
 
 > **Note:**
->
 > For a complete audience implementation, see [audience_widget.dart](https://github.com/Tencent-RTC/TUIKit_Flutter/blob/main/live/livekit/lib/live_stream/features/audience/audience_widget.dart) in the TUILiveKit open-source project.
 >
 
@@ -586,7 +583,7 @@ After integrating LiveCoreWidget, you’ll have a clean video rendering view wit
 
 ## Enrich Live Streaming Scenarios
 
-Once the basic live streaming functionality is in place, refer to the following guides to add interactive features to your live stream:
+Once the basic live streaming functionality is in place,
 
 |**Feature**|**Description**|**Store**|**Implementation Guide**|
 |---------|---------|---------|---------|

package/resource/knowledge/livekit/core-sdk/live/ios/co-guest-interaction.md

@@ -18,8 +18,6 @@
 
 ### Step 1: Component Integration
 
-Refer to Quick Start to integrate AtomicXCore and complete the setup of `LiveCoreView`.
-
 ### Step 2: Implement Audience Request to Join
 
 #### Audience-Side Implementation
@@ -258,7 +256,6 @@ Use the "slot" capability provided by the `LiveCoreView.VideoViewDelegate` proto
 #### Implementation Steps
 
 > **Note：**
->
 > For complete implementation details, refer to the open-source TUILiveKit project files [AnchorCoGuestView.swift](https://github.com/Tencent-RTC/TUIKit_iOS/blob/main/live/Sources/Features/AnchorView/View/VideoWidgets/AnchorCoGuestView.swift) and [AnchorEmptySeatView.swift](https://github.com/Tencent-RTC/TUIKit_iOS/blob/main/live/Sources/Features/AnchorView/View/VideoWidgets/AnchorEmptySeatView.swift).
 >
 

package/resource/knowledge/livekit/core-sdk/live/ios/host-interaction.md

@@ -2,7 +2,6 @@ Displaying PK User Score on Video View**AtomicXCore** provides two primary modul
 
 ## Core Scenario
 
-A typical "Host Co-hosting PK" session consists of three main stages, as shown below:
 1. **Cross-room Co-hosting**: Two hosts connect, and both video streams are displayed in a shared view.
 
 2. **Initiate PK**: After the connection is established, either host can start a PK challenge.
@@ -13,8 +12,6 @@ A typical "Host Co-hosting PK" session consists of three main stages, as shown b
 
 ### Step 1: Component Integration
 
-Refer to Quick Start to integrate AtomicXCore and complete the setup of LiveCoreView.
-
 ### Step 2: Implement Cross-Room Co-hosting
 
 The goal of this step is to display the video streams of two hosts in the same view. Use [CoHostStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/cohoststore) to achieve this.

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

@@ -44,7 +44,6 @@ See Activate Service to obtain either the trial or paid version of the SDK.Then,
 Call `LoginStore.shared.login` in your project to complete authentication. **This is required before using any functionality of AtomicXCore**.
 
 > **Note：**
->
 > We recommend calling LoginStore.shared.login only after your app's own user authentication is successful, to ensure clear and consistent login logic.
 >
 
@@ -81,7 +80,6 @@ func application(_ application: UIApplication, didFinishLaunchingWithOptions lau
 Follow these steps to quickly set up broadcaster video streaming:
 
 > **Note：**
->
 > For a complete broadcaster streaming implementation, refer to [TUILiveRoomAnchorViewController.swift](https://github.com/Tencent-RTC/TUIKit_iOS/blob/main/live/Sources/LiveStream/TUILiveRoomAnchorViewController.swift) in the TUILiveKit open source project.
 >
 
@@ -223,7 +221,6 @@ Follow these steps to quickly set up broadcaster video streaming:
 Enable audience viewing with the following steps:
 
 > **Note：**
->
 > For a complete audience playback implementation, refer to [TUILiveRoomAudienceViewController.swift](https://github.com/Tencent-RTC/TUIKit_iOS/blob/main/live/Sources/LiveStream/TUILiveRoomAudienceViewController.swift) in the TUILiveKit open source project.
 >
 
@@ -439,7 +436,7 @@ private func subscribeToDataUpdates() {
 
 ## Enriching the Live Streaming Scene
 
-Once the basic live streaming functionality is in place, refer to the following guides to add interactive features to your live stream:
+Once the basic live streaming functionality is in place,
 | <strong>Feature</strong> | <strong>Description</strong> | <strong>Store</strong> | <strong>Implementation Guide</strong> |
 | --- | --- | --- | --- |
 | Enable Audience Audio/Video Co-hosting | Audience can apply to join the host and interact via real-time video. | <a href="https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/cogueststore">CoGuestStore</a> | Implementation Guide |

package/resource/knowledge/livekit/core-sdk/voice/android/co-guest-interaction.md

@@ -13,8 +13,6 @@ AtomicXCore provides the [CoGuestStore](https://tencent-rtc.github.io/TUIKit_And
 
 ### Step 1: Component Integration
 
-Refer to the Quick Start guide to integrate **AtomicXCore** into your project.
-
 ### Step 2: Implement Audience Mic-Link Request
 
 #### Audience Side Implementation

package/resource/knowledge/livekit/core-sdk/voice/android/host-interaction.md

@@ -24,7 +24,6 @@ To initiate a connection or PK, the host must retrieve the current list of live
 **Implementation:** Call `LiveListStore.shared().fetchLiveList`.
 
 > **Note：**
->
 > - If the target room is missing from the returned list, verify that isPublicVisible in TUILiveInfo is set to true when starting the stream.
 > - This API supports pagination. Use the cursor from the onSuccess callback for subsequent fetches. An empty cursor indicates all rooms have been fetched.
 > - For optimal performance, set pageCount to 20.
@@ -55,7 +54,6 @@ fun fetchLiveListForCoHost() {
 When a host selects another host, use `CoHostStore.requestHostConnection` to send a connection invitation.
 
 > **Note：**
->
 > 1. AtomicXCore supports up to **9** interconnected rooms, each with up to **50** users.
 > 2. This interface supports batch invitations, which you can use continuously; to check if an invitation to a single live room was successful, you need to listen for the `onSuccess` callback.
 > 3. The API supports extension fields. These are delivered to the target host via `onCoHostRequestReceived` in `CoHostListener`. Use this to pass business logic such as "start PK immediately".
@@ -214,7 +212,6 @@ AtomicXCore enables hosts to start a timed PK battle once connected. Typical UI
 To start a PK battle among connected hosts, use `BattleStore.requestBattle`. Configure PK duration, whether a response is required, and any extension info.
 
 > **Note：**
->
 > 1. Default PK duration is 5 minutes if not set in `BattleConfig`.
 > 2. To start PK immediately, set `needResponse` to `false`.
 > 3. If `needResponse` is `false`, set `timeout` to 0.
@@ -305,7 +302,6 @@ PK ends either when the duration expires or when all hosts leave.
 5. After PK ends, the winner is determined by points.
 
 > **Note：**
->
 > This workflow requires both CoHostStore and BattleStore, with `needResponse` in BattleConfig set to `false`.
 >
 
@@ -401,7 +397,6 @@ This step is the same as Enter PK State.
 In typical **live host PK scenarios,** the value of gifts received by the host is linked to the PK score (for example, when a viewer sends a "Rocket" gift, the host's PK score increases by 500 points). You can implement real-time PK score updates using our REST API.
 
 > **Note：**
->
 > The PK score system in the LiveKit backend uses pure numeric calculation and accumulation. You must calculate the PK score according to your own business logic before calling the update API. See the following PK score calculation examples:
 >
 

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

@@ -38,7 +38,6 @@ dependencies {
 Call `LoginStore.shared.login` in your project to complete authentication. **This is required before using any functionality of AtomicXCore**.
 
 > **Note：**
->
 > We recommend calling `LoginStore.shared.login` after your app's own user authentication is successful to ensure clear and consistent login logic.
 >
 
@@ -221,7 +220,6 @@ class YourHostActivity : AppCompatActivity() {
 #### **4. Build the Mic Seat UI**
 
 > **Note：**
->
 > For the complete business logic of mic seat UI effects, refer to the open-source [SeatGridView.kt](https://github.com/Tencent-RTC/TUILiveKit/blob/main/Android/tuilivekit/src/main/java/com/trtc/uikit/livekit/voiceroomcore/SeatGridView.kt) in the TUILiveKit project.
 >
 
@@ -379,7 +377,7 @@ class YourAudienceActivity : AppCompatActivity() {
 
 #### **3. Build the Mic Seat UI**
 
-The process for building the mic seat UI as an audience member is the same as for the host. Refer to the host Build the Mic Seat UI.
+The process for building the mic seat UI as an audience member is the same as for the host. .
 
 #### **4. Leave the Voice Chat Room**
 
@@ -431,7 +429,6 @@ In voice chat rooms, it is common to show a wave animation on the avatar of user
 #### Implementation
 
 > **Note：**
->
 > For a complete implementation of the speaking wave animation, refer to [SeatGridView.kt](https://github.com/Tencent-RTC/TUILiveKit/blob/main/Android/tuilivekit/src/main/java/com/trtc/uikit/livekit/voiceroomcore/SeatGridView.kt) in the open-source TUILiveKit project.
 >
 

package/resource/knowledge/livekit/core-sdk/voice/flutter/co-guest-interaction.md

@@ -13,10 +13,7 @@
 
 ### Step 1: Integrate the Components
 
-Refer to quick integration to integrate **AtomicXCore**.
-
 > **Note:**
->
 > Before enabling co-hosting features, you must obtain the `liveId` (the unique identifier for the live room) to distinguish between different live rooms. You can get it as follows:
 >
 > - **Host**: Specify when creating a live stream via `LiveListStore.shared.createLive(liveInfo)`.
@@ -468,7 +465,7 @@ if (result2.isSuccess) {
 Host and co-host can call `moveUserToSeat` to change seat positions.
 
 #### Implementation:
-1. **Host Moves User to Mic Seat**: The host can call this API to move any user to a specified seat. At this point, `userID` is the ID of the target user, `targetIndex` is the index of the target seat, and the `policy` parameter specifies the move strategy if the target seat is occupied. For details, see the API parameter description.
+1. **Host Moves User to Mic Seat**: The host can call this API to move any user to a specified seat. At this point, `userID` is the ID of the target user, `targetIndex` is the index of the target seat, and the `policy` parameter specifies the move strategy if the target seat is occupied. .
 
 2. **On-Mic User Moves Themselves**: On-mic users can also call this API to move themselves. In this case, `userID` must be the user's own ID, `targetIndex` is the desired new seat index, and the `policy` parameter is ignored. If the target seat is occupied, the move fails with an error.
 

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

@@ -65,7 +65,6 @@ end
 Call `LoginStore.shared.login` in the project to complete login. **This is the key premise for using** `AtomicXCore` **all functions**.
 
 > **Important:**
->
 > We recommend calling LoginStore.shared.login after successful log-in to your App's user account to ensure clear and consistent login service logic.
 >
 
@@ -244,7 +243,6 @@ class _YourAnchorPageState extends State<YourAnchorPage> {
 #### 4. Build a Seat UI
 
 > **Note:**
->
 > For the business code of the Mic Seat `UI` effect, see the [seat_grid_widget.dart](https://github.com/Tencent-RTC/TUIKit_Flutter/blob/main/live/livekit/lib/seat_grid_widget/seat_grid_widget.dart) file in the `TUILiveKit` open-source project to learn about the complete implementation logic.
 >
 
@@ -423,7 +421,7 @@ class _YourAudiencePageState extends State<YourAudiencePage> {
 
 #### 3. Build a Seat UI
 
-Audience seat UI implementation is identical to the host. Refer to Build a Mic Seat UI.
+Audience seat UI implementation is identical to the host. .
 
 #### 4. **Leave the Voice Chat Room**
 
@@ -446,7 +444,7 @@ class _YourAudiencePageState extends State<YourAudiencePage> {
 
 ### Run and Test
 
-After completing the above steps, you can complete a most basic voice chat live streaming scenario. You can refer to various voice chat room scenarios to refine the voice chat scenario.
+After completing the above steps, you can complete a most basic voice chat live streaming scenario. You can .
 
 ## Advanced Features
 
@@ -457,7 +455,6 @@ In a voice chat room scenario, a common need is to display a wave animation on t
 #### Implementation
 
 > **Note:**
->
 > When an Anchor speaks, a wave animation effect is shown. See the [seat_grid_widget.dart](https://github.com/Tencent-RTC/TUIKit_Flutter/blob/main/live/livekit/lib/seat_grid_widget/seat_grid_widget.dart) file in the `TUILiveKit` open-source project to learn about the complete implementation logic.
 >
 
@@ -524,7 +521,7 @@ class YourSpeakingIndicatorWidget extends StatelessWidget {
 
 ## Enrich Voice Chat Room Scenarios
 
-After completing the basic voice chat room features, you can refer to the following feature guide to add various interactive gameplay features to the voice chat room.
+After completing the basic voice chat room features, you can .
 
 |**Feature**|**Feature Description**|**Feature Stores**|**Implementation Guide**|
 |---------|---------|---------|---------|

package/resource/knowledge/livekit/core-sdk/voice/ios/co-guest-interaction.md

@@ -13,8 +13,6 @@
 
 ### Step 1: Component Integration
 
-Refer to the Quick Start to integrate **AtomicXCore**.
-
 ### Step 2: Implement Audience Mic-Link Request
 
 #### Audience Side Implementation

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

@@ -24,7 +24,6 @@ To initiate co-hosting or PK, fetch the current list of live rooms and select a
 **Implementation:** Call `LiveListStore.shared.fetchLiveList`.
 
 > **Note：**
->
 > - If the desired live room is missing from the list, verify that the isPublicVisible field in TUILiveInfo was set to true when starting the stream.
 > - This API supports pagination. Use the cursor from the `Result` is `.success` callback for subsequent requests. If the returned cursor is empty, all rooms have been fetched.
 > - For optimal performance, set count to 20.
@@ -56,7 +55,6 @@ func fetchLiveListForCoHost() {
 After selecting a target streamer, use `CoHostStore.requestHostConnection` to send a co-hosting invitation.
 
 > **Note：**
->
 > - AtomicXCore supports up to 9 rooms for cross-room co-hosting, with 50 users per room.
 > - The API supports batch invitations. To check if an invitation to a single room was successful, you need to check if the `Result` is `.success` in the completion callback.
 > - The API accepts extension fields. After the invitation is sent, this field is delivered to the target streamer via the `onCoHostRequestReceived` callback. Use it to pass custom business data, such as "start PK immediately".
@@ -251,7 +249,6 @@ PK Streamer Initiates a PK BattleStreamers can start PK battles using two main f
 While co-hosting, call `BattleStore.requestBattle` to send a PK invitation. Configure PK duration, whether acceptance is required, and any extension info.
 
 > **Note：**
->
 > - If duration is not set, PK defaults to 5 minutes.
 > - To skip target acceptance, set needResponse to false in BattleConfig. PK starts immediately.
 > - If needResponse is false, set timeout to 0.
@@ -465,7 +462,6 @@ This step is same as Enter PK State.
 In typical **live host PK scenarios,** the value of gifts received by the host is linked to the PK score (for example, when a viewer sends a "Rocket" gift, the host's PK score increases by 500 points). You can implement real-time PK score updates using our `REST API`.
 
 > **Note：**
->
 > The PK score system in the LiveKit backend uses pure numeric calculation and accumulation. You must calculate the PK score according to your own business logic before calling the update API. See the following PK score calculation examples:
 >
 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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