@tencent-rtc/mcp 1.6.4 → 1.6.6

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

@@ -62,11 +62,10 @@ end
 
 ### Step 3: Implement Login Logic
 
-Call `LoginStore.shared.login` in the project to complete login. **This is the key premise for using **`AtomicXCore`** all functions**.
+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.
 >
 
@@ -108,7 +107,7 @@ void main() async {
 
 Follow these steps to quickly set up a voice chat room as the host.
 
-#### 1. **Initialize **LiveSeatStore
+#### 1. **Initialize** LiveSeatStore
 
 On your anchor page, create a `LiveSeatStore` instance. You need to listen to changes in `liveSeatStore.liveSeatState` for real-time seat updates and UI rendering.
 ``` java
@@ -169,7 +168,7 @@ class _YourAnchorPageState extends State<YourAnchorPage> {
 
 #### 2. Turn on Microphone
 
-Turn on the microphone by calling the `DeviceStore``openLocalMicrophone` API:
+Turn on the microphone by calling the `DeviceStore` `openLocalMicrophone` API:
 ``` java
 class _YourAnchorPageState extends State<YourAnchorPage> {
   // ... Other code ...
@@ -183,7 +182,7 @@ class _YourAnchorPageState extends State<YourAnchorPage> {
 
 #### 3. Start Voice Chat
 
-By calling the `LiveListStore``createLive` API to start a voice chat room live stream:
+By calling the `LiveListStore` `createLive` API to start a voice chat room live stream:
 ``` java
 class _YourAnchorPageState extends State<YourAnchorPage> {
   // ... Other code ...
@@ -246,7 +245,6 @@ class _YourAnchorPageState extends State<YourAnchorPage> {
 
 > **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.
 >
 
@@ -336,7 +334,7 @@ class _YourAnchorPageState extends State<YourAnchorPage> {
 
 Enable audience members to join the voice chat room with the following steps.
 
-#### 1. **Initialize the **LiveSeatStore
+#### 1. **Initialize the** LiveSeatStore
 
 On your audience page, create a `LiveSeatStore` instance and listen to changes in `liveSeatState.seatList` to render the mic seat UI.
 ``` java
@@ -396,7 +394,7 @@ class _YourAudiencePageState extends State<YourAudiencePage> {
 
 #### 2. **Join the Voice Chat Room**
 
-By calling the `LiveListStore``joinLive` API to join a voice chat room, sample code:
+By calling the `LiveListStore` `joinLive` API to join a voice chat room, sample code:
 ``` java
 class _YourAudiencePageState extends State<YourAudiencePage> {
   // ... Other code ...
@@ -460,7 +458,6 @@ In a voice chat room scenario, a common need is to display a wave animation on t
 
 > **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.
 >
 

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

@@ -470,7 +470,7 @@ For detailed information about all public interfaces, properties, and methods of
 ### What’s the difference between voice room mic-link and video live mic-link implementation?
 
 The main differences are in business logic and UI presentation:
-- `Video Live: `The core is the video feed. Use `LiveCoreView` as the main component to render video streams for the host and mic-linked viewers. The UI focuses on video layout and sizing, and you can add overlays (nickname, placeholder image) via `VideoViewDelegate`. Both camera and microphone can be enabled.
+- `Video Live:` The core is the video feed. Use `LiveCoreView` as the main component to render video streams for the host and mic-linked viewers. The UI focuses on video layout and sizing, and you can add overlays (nickname, placeholder image) via `VideoViewDelegate`. Both camera and microphone can be enabled.
 
 - `Voice Room:` The core is the mic seat grid. Do not use `LiveCoreView`; instead, build a grid UI (e.g., `UICollectionView`) based on the `LiveSeatStore`'s `state` (especially `seatList`). The UI focuses on real-time display of each seat’s `SeatInfo` status: occupied, muted, locked, and speaking status. Only the microphone needs to be enabled.
 
@@ -498,7 +498,7 @@ This is an important distinction. `DeviceStore` manages the physical device, whi
 
 - `unmuteMicrophone`: Unmute. Resumes sending audio stream to remote.
 
-   **Recommended workflow: **"Open the device once, control mute/unmute while on mic"
+   **Recommended workflow:** "Open the device once, control mute/unmute while on mic"
 
 1. **When joining mic:** When an audience member successfully joins the mic, call `openLocalMicrophone` once to start the device.
 

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

@@ -58,7 +58,7 @@ After selecting a target streamer, use `CoHostStore.requestHostConnection` to se
 > **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 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".
 
 ``` swift
@@ -335,8 +335,8 @@ PK can end in two ways:
 
    > **Note：**
    >
->   - After PK ends, the session returns to cross-room co-hosting.
->   - To end co-hosting after PK, call `exitHostConnection`.
+   > - After PK ends, the session returns to cross-room co-hosting.
+   > - To end co-hosting after PK, call `exitHostConnection`.
 
 ### Scenario 2: Co-hosting with PK Mode
 
@@ -353,7 +353,6 @@ PK can end in two ways:
 
    > **Note：**
    >
-
    > This flow requires both CoHostStore and BattleStore, with `BattleConfig.needResponse` set to `false`.
    >
 
@@ -463,11 +462,10 @@ This step is same as Enter PK State.
 
 ### Updating PK Score via REST API
 
-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`.
+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/{voice-integration.md → integration.md}

@@ -40,7 +40,6 @@ Call `LoginStore.shared.login` in your project to complete authentication. **Thi
 
 > **Note：**
 >
-
 > We recommend calling LoginStore.shared.login only after your app's own user authentication is successful, to ensure clear and consistent login logic.
 >
 
@@ -121,7 +120,7 @@ class YourAnchorViewController: UIViewController {
 }
 ```
 
-#### **2. **Turn On Microphone
+#### **2.** Turn On Microphone
 
 Turn On Microphone by calling `openLocalMicrophone` from `DeviceStore`:
 ``` swift
@@ -200,7 +199,6 @@ class YourAnchorViewController: UIViewController {
 
 > **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.
 >
 
@@ -380,7 +378,6 @@ In voice chat rooms, it's common to show a wave animation over the avatar of use
 
 > **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/preset/live/vue/features/barrage.md

@@ -85,10 +85,8 @@ onMounted(async () => {
 
 > **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/push/api-reference/android.md

@@ -0,0 +1,123 @@
+## TIMPush - TIMPushManager
+
+public abstract class TIMPushManager: Push Plugin Interface Class.
+
+### API overview
+
+#### Register/Unregister Push Service Interface
+
+|API|Description|
+|---------|---------|
+|registerPush|Register Push Service, push information reads the configuration file timpush-configs.json in the project (this interface must be called after the App user has agreed to the privacy policy to use the push service).|
+|unRegisterPush|Unregister and disable the push service.|
+|setRegistrationID|RegistrationID is the unique identifier ID of the push receiving device. By default, this ID is automatically generated when the push service is successfully registered, but you can also customize the setting. You can push messages to the specified device based on the RegistrationID. Note that uninstalling and reinstalling the device will change the RegistrationID, so you need to call the setRegistrationID interface before registering the push service.|
+|getRegistrationID|After successfully registering the push service, you can get the unique identifier ID of the push receiving device, that is, the RegistrationID, by calling the getRegistrationID interface. You can push messages to the specified device based on the RegistrationID.|
+
+#### Push global listening interface
+
+|API|Description|
+|---------|---------|
+|addPushListener|Add Push listener.|
+|removePushListener|Remove Push listener.|
+
+#### Custom Configuration Interface
+
+|API|Description|
+|---------|---------|
+|forceUseFCMPushChannel|Specify offline push to use the FCM channel for the device. This needs to be called before registering the push service.|
+|disablePostNotificationInForeground|Disable the notification bar when the app is in the foreground.|
+
+### Interface Details
+
+#### Static Public Member Functions
+
+static TIMPushManager getInstance(): Retrieves the TIMPushManager manager instance.
+
+#### Member Function Description
+
+##### abstract void registerPush(Context context, int sdkAppId, String appKey, TIMPushCallback callback)
+
+Register Push Service. Please correctly pass the parameters sdkAppId and appKey to register the push service.
+
+Parameter description:
+| Parameter | Description | Get Path |
+| --- | --- | --- |
+| sdkAppId | The application ID assigned to you by the Chat console. |  |
+| appKey | The client key assigned to you by the Chat console. |  |
+
+##### abstract void unRegisterPush(TIMPushCallback callback)
+
+Unregister and disable the push service.
+
+##### abstract void setRegistrationID(String registrationID, TIMPushCallback callback)
+
+Set the push ID identifier used for registering the push service, i.e., RegistrationID, which needs to be called before registering the push service.
+
+Parameter description:
+
+|Parameter|Description|
+|---------|---------|
+|registrationID|Unique ID for push notifications on the device, which may change if uninstalled and reinstalled.|
+
+##### abstract void getRegistrationID(TIMPushCallback callback)
+
+After successfully registering for the push service, obtain the push ID identifier, i.e., RegistrationID.
+
+##### abstract void addPushListener(TIMPushListener listener)
+
+Add Push listener
+
+##### abstract void removePushListener(TIMPushListener listener)
+
+Remove Push listener
+
+##### abstract void forceUseFCMPushChannel(boolean enable)
+
+Specify offline push to use the FCM channel for the device. This needs to be called before registering the push service.
+
+Parameter description:
+| Parameter | Description |
+| --- | --- |
+| enable | - true: Use FCM channel.<br>- false: use the native channel. |
+
+##### abstract void disablePostNotificationInForeground(boolean disable)
+
+Disable notification bar pop-ups when the app is in the foreground. When the Push SDK receives an online Push, it will automatically add a Notification to the notification bar. If you want to handle the online Push messages yourself, you can call this interface to disable the automatic notification bar pop-up feature.
+
+Parameter description:
+| Parameter | Description |
+| --- | --- |
+| disable | - true: disable<br>- false: enable |
+
+## TIMPush - TIMPushListener
+
+public abstract class TIMPushListener: Push Listener class
+
+### API overview
+
+|API|Description|
+|---------|---------|
+|onRecvPushMessage|Received Push message.|
+|onRevokePushMessage|Received a notification of Push message recall.|
+|onNotificationClicked|Notification bar message click callback.|
+
+### Interface Details
+
+#### Member Function Description
+
+##### void onRecvPushMessage(TIMPushMessage message)
+
+Received Push message, message content.
+
+##### void onRevokePushMessage(String messageID)
+
+Received a notification of Push message recall, messageID uniquely identifies the message.
+
+##### void onNotificationClicked(String ext)
+
+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/flutter.md

@@ -0,0 +1,176 @@
+## TencentCloudChatPush
+
+class TencentCloudChatPush: Push Plugin Interface Class.
+
+## API overview
+
+### Register/Unregister Push Service Interface
+
+|API|Description|
+|---------|---------|
+|registerPush|Register Push Service, optionally override push information from interface parameter JSON.|
+|unRegisterPush|Unregister Push Service.|
+|setRegistrationID|RegistrationID is the unique identifier ID of the push receiving device. By default, this ID is automatically generated when the push service is successfully registered, but you can also customize the setting. You can push messages to the specified device based on the RegistrationID. Note that uninstalling and reinstalling the device will change the RegistrationID, so you need to call the setRegistrationID interface before registering the push service.|
+|getRegistrationID|After successfully registering the push service, you can get the unique identifier ID of the push receiving device, that is, the RegistrationID, by calling the getRegistrationID interface. You can push messages to the specified device based on the RegistrationID.|
+
+### Push global listening interface
+
+|API|Description|
+|---------|---------|
+|addPushListener|Add Push listener.|
+|removePushListener|Remove Push listener.|
+
+### Custom Configuration Interface
+
+|API|Description|
+|---------|---------|
+|forceUseFCMPushChannel|Specify offline push to use the FCM channel for the device. This needs to be called before registering the push service.|
+|disablePostNotificationInForeground|Disable the notification bar when the app is in the foreground.|
+
+## Interface Details
+
+### Push Plugin Class
+
+TencentCloudChatPush(): Get the TencentCloudChatPush plugin instance, which is a static singleton. Subsequent steps are performed through this singleton instance for method calls.
+
+### Member Function Description
+
+#### registerPush
+
+Register Push Service, to be called after Chat account login is successful.
+
+**Sample code:**
+``` java
+void _onNotificationClicked({required String ext, String? userID, String? groupID}) {
+  print("_onNotificationClicked: $ext, userID: $userID, groupID: $groupID");
+  /// Custom Processing
+}
+TencentCloudChatPush().registerPush(
+    onNotificationClicked: _onNotificationClicked,
+    sdkAppId: Your sdkAppId,
+    appKey: "client key",
+    apnsCertificateID: Your configured Certificate ID);
+```
+
+**Parameter description:**
+| Parameter | Type | Description |  |
+| --- | --- | --- | --- |
+| onNotificationClicked | ext | String | The complete ext information carried by the message is specified by the sender. If not specified, there is a default value. You can parse this field to navigate to the corresponding page. |
+| userID | String? | This parameter corresponds to userID. It automatically tries to parse the ext JSON String to obtain the userID of the other party in a single chat.<br><strong>Note:</strong><br>If you have not customized the ext field, which is specified by the SDK or UIKit by default, you can use the default parsing here. If the parsing attempt fails, it will be null. |  |
+| groupID | String? | This parameter corresponds to groupID. It automatically tries to parse the ext JSON String to obtain the groupID information for group chats.<br><strong>Note:</strong><br>If you have not customized the ext field, which is specified by the SDK or UIKit by default, you can use the default parsing here. If the parsing attempt fails, it will be null. |  |
+| sdkAppId | int? | The application ID assigned to you by the Chat console |  |
+| appKey | String? | Client key assigned to you by the Chat console |  |
+| apnsCertificateID | int? | This item can be omitted if the setApnsCertificateID method is already configured separately. |  |
+
+#### unRegisterPush
+
+Unregister offline push service.
+
+**Sample code:**
+``` java
+TencentCloudChatPush().unRegisterPush();
+```
+
+#### setRegistrationID
+
+Set the push ID used for registering the offline push service, that is, the RegistrationID, which needs to be called before registering the push service.
+
+Parameter description:
+
+|Parameter|Description|
+|---------|---------|
+|registrationID|Device push ID, which will change after uninstalling and reinstalling.|
+
+**Sample code:**
+``` java
+TencentCloudChatPush().setRegistrationID(registrationID: registrationID);
+```
+
+#### getRegistrationID
+
+After successfully registering for the offline push service, obtain the push ID, that is, the RegistrationID.
+
+**Sample code:**
+``` java
+TencentCloudChatPush().getRegistrationID();
+```
+
+#### addPushListener
+
+Add Push listener
+
+**Sample code:**
+``` java
+TIMPushListener timPushListener = TIMPushListener(
+  onRecvPushMessage: (TimPushMessage message) {
+      String messageLog = message.toLogString();
+      debugPrint(
+          "message: $messageLog");
+      },
+
+  onRevokePushMessage: (String messageId) {
+    debugPrint(
+        "message: $messageId");
+  },
+
+  onNotificationClicked: (String ext) {
+    debugPrint(
+        "ext: $ext");
+  }
+);
+TencentCloudChatPush.addPushListener(listener: timPushListener);
+```
+
+#### removePushListener
+
+Remove Push listener
+
+**Sample code:**
+``` java
+TIMPushListener timPushListener = TIMPushListener(
+  onRecvPushMessage: (TimPushMessage message) {
+      String messageLog = message.toLogString();
+      debugPrint(
+          "message: $messageLog");
+      },
+
+  onRevokePushMessage: (String messageId) {
+    debugPrint(
+        "message: $messageId");
+  },
+
+  onNotificationClicked: (String ext) {
+    debugPrint(
+        "ext: $ext");
+  }
+);
+TencentCloudChatPush.removePushListener(listener: timPushListener);
+```
+
+#### forceUseFCMPushChannel
+
+Specify offline push to use the FCM channel for the device. This needs to be called before registering the push service.
+
+Parameter description:
+| Parameter | Description |
+| --- | --- |
+| enable | - true: Use FCM channel.<br>- false: use the native channel. |
+
+**Sample code:**
+``` java
+TencentCloudChatPush.forceUseFCMPushChannel(enable: true);
+```
+
+#### disablePostNotificationInForeground
+
+Disable notification bar pop-ups when the app is in the foreground. When the Push SDK receives an online Push, it will automatically add a Notification to the notification bar. If you want to handle the online Push messages yourself, you can call this interface to disable the automatic notification bar pop-up feature.
+
+Parameter description:
+| Parameter | Description |
+| --- | --- |
+| disable | - true: disable<br>- false: enable |
+
+**Sample code:**
+``` java
+TencentCloudChatPush.disablePostNotificationInForeground(disable: true);
+```

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

@@ -0,0 +1,138 @@
+## TIMPushManager API Overview
+| API | Description |
+| --- | --- |
+| registerPush | Register push service (call this API to use push service only after obtaining user consent for the privacy policy). |
+| unRegisterPush | Unregister and disable push service. |
+| setRegistrationID | - RegistrationID is the unique identifier of the push reception device.<br>- By default, it is system-generated when push service registration succeeds. You can also set custom registration ID.<br>- Based on RegistrationID, you can send push messages to specified devices.<br>- Note that uninstalling and reinstalling the device will change the RegistrationID, so you need to call the setRegistrationID API before registering the push service. |
+| getRegistrationID | After successfully registering the push service, call this API to get the unique identifier of the push reception device, namely RegistrationID. |
+| addPushListener | Add a Push Listener. |
+| removePushListener | Remove a Push Listener. |
+| disablePostNotificationInForeground | Enable/disable notification bar notifications when the app is in the foreground (default: enabled). |
+
+## API Detail
+
+### Register Push Service
+
+#### API
+``` tsx
+registerPush(
+  context: Context,
+  sdkAppId?: number,
+  appKey?: string,
+  businessId?: number
+): Promise<TIMPushResult>;
+```
+
+#### Parameter description:
+| Parameter | Type | Description | Access Path |
+| --- | --- | --- | --- |
+| context | Context | application context | - |
+| sdkAppId | number | Push Service SDKAppID. | <a href="https://console.trtc.io/chat/push-plugin-push-identifier">Chat > Push > Access Settings</a> page |
+| appKey | String | Push Service client key. |  |
+| businessId | number | Certificate ID assigned in the Chat console. |  |
+
+### Unregistering and Disabling Push Service
+
+#### API
+``` tsx
+unRegisterPush(): Promise<TIMPushResult>;
+```
+
+### Setting Push ID Identifier RegistrationID
+
+> **Note:**
+>
+> 1. If you call this API, ensure to call it before `registerPush`.
+
+#### API
+``` tsx
+setRegistrationID(registrationID: string): Promise<TIMPushResult>;
+```
+
+#### Parameter description:
+
+|Parameter|Type|Description|
+|---------|---------|---------|
+|registrationID|String|Custom push ID identifier.|
+
+### 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.
+>
+
+#### API
+``` tsx
+getRegistrationID(): Promise<TIMPushResult>;
+```
+
+### Adding a Push Listener
+
+#### API
+``` tsx
+addPushListener(listener: TIMPushListener): void;
+```
+
+#### Parameter description:
+
+|Parameter|Type|Description|
+|---------|---------|---------|
+|listener|TIMPushListener|Push event processing method|
+
+### Removing a Push Listener
+
+#### API
+``` tsx
+removePushListener(listener: TIMPushListener): void;
+```
+
+#### Parameter description:
+
+|Parameter|Type|Description|
+|---------|---------|---------|
+|listener|TIMPushListener|Push event processing method|
+
+### Enabling/Disabling Notification Bar Notifications When the App Is in the Foreground
+
+#### API
+``` tsx
+disablePostNotificationInForeground(disable: boolean): void;
+```
+
+#### Parameter description:
+| Parameter | Type | Description |
+| --- | --- | --- |
+| disable | boolean | Enable/disable notification bar notifications when the app is in the foreground (default: off).<br>- Disable notification bar notifications when the app is in the foreground.<br>- false: Enable notification bar notifications when the app is in the foreground. |
+
+## TIMPushListener API Overview
+
+|API|Description|
+|---------|---------|
+|onRecvPushMessage|Received a Push message.|
+|onRevokePushMessage|Received a Push message recall notification.|
+|onNotificationClicked|Click the notification bar message Webhook.|
+
+### API Detail
+
+#### Member Function Description
+
+##### onMessageReceived(message: TIMPushMessage): void;
+
+Received a Push message. Received a message.
+
+##### onRevokePushMessage(messageID: string): void;
+
+Received a Push message recall notification with the unique message identifier messageID.
+
+##### onNotificationClicked(ext: string): void;
+
+Click the notification bar message Webhook.
+
+## TIMPushResult API Overview
+
+|Field|Description|Type|
+|---------|---------|---------|
+|code|Error code|number|
+|message|Error Description|string|
+|data|Return Values|unknown|