@tencent-rtc/mcp 1.6.7 → 1.7.0

package/resource/knowledge/callkit/best-practice/common/callkit-user-register-and-kicked.md

@@ -0,0 +1,98 @@
+---
+title: "TUICallKit user registration and Multi-Instance Kick-Out Explained（TUICallKit 用户注册 / 多实例登录）"
+product: call
+frameworks: [react, vue, miniprogram, web]
+scope: platform_common
+tags: [TUICallKit, user registration, init, userSig, auto-create user, multi-instance login, kicked out, KICKED_OUT, troubleshooting, same browser, multi-instance, web multi-instance]
+version_range: ">=4.0.0"
+---
+
+# TUICallKit User Registration and Multi-Instance Kick-Out Explained
+
+## 1. Key Takeaways
+
+### User Registration
+
+- TUICallKit **does not have a dedicated frontend registration API**. User registration is completed through the `init` API: passing `userID` and `userSig` completes authentication and login.
+- When a `userID` and `userSig` issued by the backend are used to log in to TUICallKit for the first time, the system automatically creates the user if that `userID` does not yet exist in Tencent Cloud IM.
+- Alternatively, users can be batch-imported via the IM Console, and then the imported `userID` with its corresponding `userSig` can be used to log in.
+
+### Multi-Instance Kick-Out
+
+- When the same `userID` is logged in simultaneously across different browser tabs or devices, the earlier session is kicked offline (`KICKED_OUT`) by default, because the Chat SDK Web allows only one instance online per user by default.
+- After enabling **Web Multi-Instance Login** in the Chat Console, the same `userID` can be online across multiple tabs or devices simultaneously without being kicked.
+- Different `userID`s logged in within the same browser are not affected by this restriction and will not kick each other offline.
+
+## 2. Field / API Reference
+
+| Field / API | Purpose | Notes |
+|---|---|---|
+| `init` | Initialize and register a user | Pass `SDKAppID`, `userID`, `userSig` to complete authentication |
+| `userID` | User identifier | Issued or defined by the business backend; auto-creates the user on first login |
+| `userSig` | User signature | Issued by the business backend for authentication |
+| `KICKED_OUT` | Kicked offline event | Triggered during same-account / multi-instance login |
+| Web Multi-Instance Login | Console configuration | Once enabled, the same browser can have multiple sessions online simultaneously |
+
+## 3. Mechanism & Sequence
+
+### User Registration Flow
+
+Backend generates `userID` + `userSig` -> frontend calls `init({ SDKAppID, userID, userSig })` -> TUICallKit logs in via the Chat SDK -> if the user does not exist, it is auto-created -> login succeeds.
+
+### Multi-Instance Kick-Out Mechanism
+
+Same `userID` logs in on tab A -> same browser opens tab B and logs in with the same `userID` -> Chat backend detects a multi-instance login -> kicks tab A offline -> tab A receives the `KICKED_OUT` event.
+
+## 4. Standard Usage
+
+### User Registration and Initialization
+
+```javascript
+// React: @trtc/calls-uikit-react
+// Vue 3: @trtc/calls-uikit-vue
+// Vue 2.7: @trtc/calls-uikit-vue2
+// Vue 2.6: @trtc/calls-uikit-vue2.6
+// uniapp 小程序: @trtc/calls-uikit-wx-uniapp
+// 微信原生小程序: @trtc/calls-uikit-wx  （API 一致，仅包名不同）
+import { TUICallKitAPI } from "@trtc/calls-uikit-react";
+
+TUICallKitAPI.init({
+  SDKAppID: 0,         // 控制台获取的 SDKAppID
+  userID: 'user_xxx',  // 业务后端签发的用户 ID
+  userSig: 'xxx',      // 业务后端签发的用户签名
+});
+```
+
+### Enabling Web Multi-Instance Login (Resolving Kick-Out)
+
+1. Log in to the Tencent Cloud IM Console.
+2. Navigate to the target application's feature configuration page.
+3. Enable the **Web Multi-Instance Login** toggle.
+4. Save. The change takes effect immediately without restarting the client.
+
+## 5. Expected Results
+
+- After calling `init`, login succeeds with no errors.
+- With Web Multi-Instance enabled in the console, the same `userID` can be online across multiple tabs or devices simultaneously.
+- Without the feature enabled, logging in with the same `userID` on a new tab causes the old tab to receive the `KICKED_OUT` event.
+
+## 6. Common Pitfalls
+
+- Pitfall 1: Assuming TUICallKit has a dedicated frontend registration API (registration and login are actually done through `init`).
+- Pitfall 2: Treating kick-out as a TUICallKit bug (it is actually the Chat SDK's multi-device login restriction).
+- Pitfall 3: Assuming different origins also cause kick-out (different origins are treated as different instances and are unaffected).
+- Pitfall 4: Assuming different `userID`s in the same browser kick each other out (the multi-instance restriction applies to the same `userID`; different `userID`s are independent).
+- Pitfall 5: Thinking `KICKED_OUT` can only be resolved by closing other logins (enabling Web Multi-Instance Login avoids it).
+
+## 7. Problem Definition (retrieval hint)
+
+Users ask about TUICallKit Web user registration (whether there is a dedicated registration API, whether users are auto-created), and the cause and solution for multi-account kick-out within the same browser.
+
+## 8. Alternative Queries (retrieval recall)
+
+- What is the TUICallKit user registration API?
+- Does first-time login auto-create a user?
+- What to do when two accounts in the same browser get kicked out?
+- How to troubleshoot `KICKED_OUT`?
+- Does logging in from a different domain cause kick-out?
+- How to let multiple users log in on the same page simultaneously?

package/resource/knowledge/callkit/core-sdk/android/answer-call.md

@@ -616,9 +616,6 @@ Before starting a call, use [setSelfInfo](https://liteav.sdk.cloudcachetci.com/d
 ### Switch Layout Modes
 
 Use [setLayoutTemplate](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-call-core-view/set-layout-template.html) to switch layout modes. If not set, CallCoreView adapts automatically: **Float** mode for 1v1 calls, **Grid** mode for multi-party calls.
-| <strong>Float Mode</strong> | <strong>Grid Mode</strong> | <strong>PIP Mode</strong> |
-| --- | --- | --- |
-|  |  |  |
 | - <strong>Layout Logic:</strong> Full screen shows own video while waiting; after answering, full screen shows the other party's video, own video floats as a small window.<br>- <strong>Interaction:</strong> Supports dragging and swapping windows. | - <strong>Layout Logic:</strong> All participant videos are tiled in a grid. Suitable for 2+ participants; supports click-to-enlarge.<br>- <strong>Interaction:</strong> Click to enlarge a participant's video. | - <strong>Layout Logic:</strong> In 1v1, always shows the other party's video; in multi-party, uses active speaker strategy.<br>- <strong>Interaction:</strong> Shows own video while waiting, displays call timer after answering. |
 
 - **setLayoutTemplate Sample Code:**
@@ -821,7 +818,3 @@ Congratulations! You have implemented the answer call feature. Next, see Make Yo
 ### Can an invitee receive a call event if they go offline and then come back online within the call timeout period?
 
 For one-on-one calls, if the callee comes online within the timeout, they will receive the incoming call invitation. For group calls, if the callee comes online within the timeout, up to 20 unprocessed group messages will be retrieved, and if there is a call invitation, the incoming call event will be triggered.
-
-## Contact Us
-
-If you have any questions or suggestions during the integration or usage process, feel free to join our [Telegram technical group](https://t.me/+EPk6TMZEZMM5OGY1) or [contact us](https://trtc.io/contact) for support.

package/resource/knowledge/callkit/core-sdk/android/make-call.md

@@ -70,7 +70,6 @@ class MainActivity : ComponentActivity() {
 ## Implementation
 
 > **Note：**
->
 > You must log in before making a call. The following steps show how to make a call.
 >
 
@@ -661,9 +660,6 @@ Before a call starts, use [setSelfInfo](https://liteav.sdk.cloudcachetci.com/doc
 ### Switch Layout Mode
 
 Use [setLayoutTemplate](https://liteav.sdk.cloudcachetci.com/doc/product/tuikit/atomic-x/android/en/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.view/-call-core-view/set-layout-template.html) to switch between layout modes. If not set, **CallCoreView** adapts automatically: 1v1 calls use `Float` mode by default, while multi-party calls use `Grid` mode. Layout mode descriptions:
-| <strong>Float Mode</strong> | <strong>Grid Mode</strong> | <strong>PIP Mode</strong> |
-| --- | --- | --- |
-|  |  |  |
 | - <strong>Layout:</strong> Full screen self-view while waiting; after connecting, full screen remote view with self-view as a floating window.<br>- <strong>Interaction:</strong> Floating window supports drag and click-to-swap with the main view. | - <strong>Layout:</strong> Grid layout for all participants, suitable for 2+ users. Supports click-to-enlarge.<br>- <strong>Interaction:</strong> Click any participant's view to enlarge. | - <strong>Layout:</strong> 1v1 shows fixed remote view; multi-party uses active speaker strategy with full screen for the current speaker.<br>- <strong>Interaction:</strong> Waiting state shows self-view; after connecting, call duration is displayed. |
 
 - **setLayoutTemplate Example:**
@@ -889,7 +885,3 @@ Congratulations! You've completed the "Make a Call" feature. Next, you can imple
 ### If the callee comes online before the call invitation times out, do they get the incoming call?
 
 For single calls, if the callee comes online within the timeout, they will receive an incoming call invitation. For group calls, up to 20 unhandled group messages are pulled when coming online within the timeout; if a call invitation exists, the incoming call event is triggered.
-
-## Contact Us
-
-If you have any questions or suggestions during the integration or usage process, feel free to join our [Telegram technical group](https://t.me/+EPk6TMZEZMM5OGY1) or [contact us](https://trtc.io/contact) for support.

package/resource/knowledge/callkit/core-sdk/android/offline-push.md

@@ -3,7 +3,6 @@ On Android, incoming audio/video call invitations won't trigger notifications wh
 To solve this, you need to integrate offline push notifications using FCM Data Messages. This allows critical signaling—like call invitations—to reach the device and wake up your app, even when it's completely closed, launching the call interface so users can answer incoming calls.
 
 > **Note:**
->
 > Offline push is not required if users are only calling always-online web agents.
 >
 
@@ -14,7 +13,6 @@ This guide shows you how to integrate FCM Data Message push for audio/video call
 Go to the [Chat Console > App Push > Access settings](https://console.trtc.io/chat/push-plugin-push-identifier) , and click **Purchase Now** or **Free Trial** (each app is eligible for one free trial, valid for 7 days).
 
 > **Note:**
->
 > When your push plugin trial or subscription expires, all push services (including offline push for regular messages, broadcast/tag push, etc.) will be automatically suspended. To ensure uninterrupted service, please [purchase](https://buy.intl.cloud.tencent.com/avc) or [renew](https://console.tencentcloud.com/expense/renewal) your subscription in advance.
 >
 
@@ -336,12 +334,10 @@ Listen for incoming call events. After a successful login (Step 1), if there are
 
 ### Demo Effect
 
-After completing all three steps above, the incoming call notification will appear as shown below:
-
 ## FAQs
 
 ### Unable to Display Incoming Call Interface After App Is Killed?
-- Check if push notifications are being received. If not, verify that the IM Console certificate was uploaded correctly. Refer to Step 1 of **Quick Integration** in this guide.
+- Check if push notifications are being received. If not, verify that the IM Console certificate was uploaded correctly. .
 
 - Ensure that FCM Data Message is selected in the console, as described in Step 2 of **Prerequisites** above.
 
@@ -355,7 +351,3 @@ To force your app to always use the FCM channel, call the following method:
 ``` java
 TIMPushManager.getInstance().forceUseFCMPushChannel(true);
 ```
-
-## Contact Us
-
-If you have any questions or suggestions during integration or use, join the [Telegram](https://t.me/+EPk6TMZEZMM5OGY1) technical group or [Contact Us](https://trtc.io/contact) for support.

package/resource/knowledge/callkit/core-sdk/flutter/answer-call.md

@@ -43,6 +43,7 @@ flutter pub add atomic_x_core
           }
       }
       ```
+
       ``` java
       android {
           buildTypes {
@@ -297,6 +298,7 @@ Check audio/video permissions before starting a call. If permissions are missing
    ``` bash
    flutter pub add permission_handler
    ```
+
    ``` java
    import 'package:permission_handler/permission_handler.dart';
 
@@ -645,9 +647,6 @@ Before the call starts, use [setSelfInfo](https://liteav.sdk.qcloud.com/doc/prod
 ### Switch Layout Modes
 
 Use [setLayoutTemplate](https://liteav.sdk.qcloud.com/doc/product/tuikit/atomic-x/flutter/v1.0/en/api_view_call_call_core_view/CallCoreController/setLayoutTemplate.html) for flexible layout switching. If unset, **CallCoreView** adapts automatically: 1-on-1 calls use `Float` mode, group calls use `Grid` mode.
-| <strong>Float Mode</strong> | <strong>Grid Mode</strong> | <strong>PIP Mode</strong> |
-| --- | --- | --- |
-|  |  |  |
 | - <strong>Layout:</strong> Full screen self-view while waiting; after connecting, full screen remote view with self-view as a floating window.<br>- <strong>Interaction:</strong> Floating window supports drag and click-to-swap with the main view. | - <strong>Layout:</strong> Grid layout for all participants, suitable for 2+ users. Supports click-to-enlarge.<br>- <strong>Interaction:</strong> Click any participant's view to enlarge. | - <strong>Layout:</strong> 1v1 shows fixed remote view; multi-party uses active speaker strategy with full screen for the current speaker.<br>- <strong>Interaction:</strong> Waiting state shows self-view; after connecting, call duration is displayed. |
 
 - **Sample Code:**
@@ -868,7 +867,6 @@ Picture-in-Picture requires Android 8.0 (API 26) or later.
 iOS supports system PiP with the underlying TRTC engine. When the app goes to background, the call view floats above other apps as a PiP window, letting users multitask.
 
 > **Note:**
->
 > Add `Background Modes` in Xcode's `Signing & Capabilities` and check `Audio, AirPlay, and Picture in Picture`.
 >
 > Requires iOS 15.0 or later.
@@ -1101,7 +1099,3 @@ Since tencent_rtc_sdk uses Flutter FFI, Xcode's symbol stripping during Release
 ### If the callee goes offline and then comes online within the call invitation timeout, will they receive the incoming call event?
 
 For single calls, if the callee comes online within the timeout, they will receive the call invitation. For group calls, if the callee comes online within the timeout, up to 20 unprocessed group messages will be pulled; if there is a call invitation, the incoming call event is triggered.
-
-## Contact Us
-
-If you have questions or suggestions during integration or usage, join our [Telegram](https://t.me/+Lmw2MSqW6ethMGM1) technical group or [Contact Us](https://trtc.io/contact) for support.

package/resource/knowledge/callkit/core-sdk/flutter/make-call.md

@@ -43,6 +43,7 @@ flutter pub add atomic_x_core
           }
       }
       ```
+
       ``` java
       android {
           buildTypes {
@@ -363,6 +364,7 @@ Check for audio/video permissions before starting a call. If permissions are mis
    ``` bash
    flutter pub add permission_handler
    ```
+
    ``` java
    import 'package:permission_handler/permission_handler.dart';
 
@@ -648,9 +650,6 @@ if (result.errorCode == 0) {
 ### Switch Layout Modes
 
 Switch layouts flexibly using [setLayoutTemplate](https://liteav.sdk.qcloud.com/doc/product/tuikit/atomic-x/flutter/v1.0/en/api_view_call_call_core_view/CallCoreController/setLayoutTemplate.html). If not set, **CallCoreView** adapts automatically: 1v1 defaults to `Float`, group calls use `Grid`.
-| <strong>Float Mode</strong> | <strong>Grid Mode</strong> | <strong>PIP Mode</strong> |
-| --- | --- | --- |
-|  |  |  |
 | - <strong>Layout:</strong> Full screen self-view while waiting; after connecting, full screen remote view with self-view as a floating window.<br>- <strong>Interaction:</strong> Floating window supports drag and click-to-swap with the main view. | - <strong>Layout:</strong> Grid layout for all participants, suitable for 2+ users. Supports click-to-enlarge.<br>- <strong>Interaction:</strong> Click any participant's view to enlarge. | - <strong>Layout:</strong> 1v1 shows fixed remote view; multi-party uses active speaker strategy with full screen for the current speaker.<br>- <strong>Interaction:</strong> Waiting state shows self-view; after connecting, call duration is displayed. |
 
 - **Sample usage:**
@@ -863,7 +862,6 @@ Picture-in-Picture requires Android 8.0 (API 26) or above.
 iOS supports Picture-in-Picture outside the app using the underlying TRTC engine. When the app goes to background, the call interface floats over other apps as a system PiP window.
 
 > **Note：**
->
 > In Xcode, add `Background Modes` under `Signing & Capabilities` and check `Audio, AirPlay, and Picture in Picture`.
 >
 > Requires iOS 15.0 or above.
@@ -1122,7 +1120,3 @@ If you see `symbol not found` errors in your iOS Release build, it’s likely be
 - For single calls: If the callee comes online within the timeout period, they will receive the incoming call invite.
 
 - For group calls: If the callee returns within the timeout, up to 20 unprocessed group messages will be pulled; if there is a call invite, the incoming call event will be triggered.
-
-## Contact Us
-
-If you have any questions or suggestions during integration or use, join our [Telegram](https://t.me/+Lmw2MSqW6ethMGM1) technical group or [Contact Us](https://trtc.io/contact) for support.

package/resource/knowledge/callkit/core-sdk/flutter/offline-push.md

@@ -2,16 +2,11 @@ This document provides step-by-step instructions for implementing offline push n
 
 ## Effect Preview
 
-|**Android (FCM)**|**iOS (APNs)**|
-|---------|---------|
-|||
-
 ## Activate the Service
 
 Navigate to [Chat Console > App Push > Integration Settings](https://console.trtc.io/chat/push-plugin-push-identifier), then click **Purchase Now** or **Free Trial** (each app can try the free trial once, valid for 7 days).
 
 > **Note:**
->
 > After the push plugin trial or purchase expires, push services (including offline push for standard messages, broadcast/tag push, etc.) will be automatically disabled. To avoid business interruption, please [purchase](https://buy.intl.cloud.tencent.com/avc) or [renew](https://console.tencentcloud.com/expense/renewal) the service in advance.
 >
 
@@ -57,10 +52,6 @@ flutter pub add tencent_cloud_chat_push
 
 Once you complete the vendor push setup in the console, download and add the configuration files to your project. Place the downloaded `timpush-configs.json` in your app module's `assets` directory, and add `google-services.json` to your app directory.
 
-|**Select and download timpush-configs.json**|**Download google-services.json**|**Add to your project**|
-|---------|---------|---------|
-||||
-
 ### Step 2: Integrate Android Push Plugin
 
 Add the following dependency to your project's `android/app/build.gradle` file:
@@ -73,7 +64,6 @@ implementation "com.tencent.timpush:fcm:latest.release"
 ```
 
 > **Note:**
->
 > - TIMPush requires IM SDK version **7.9.5666** or higher. You can check version and update info in the [Changelog](https://pub.dev/packages/tencent_cloud_chat_push/changelog).
 > - The dependency version in `build.gradle` must match the version of `tencent_cloud_chat_push`.
 
@@ -96,7 +86,6 @@ public class MyApplication extends TencentCloudChatPushApplication {
 ```
 
 > **Note:**
->
 > If you have an existing Application class, simply extend `TencentCloudChatPushApplication` and ensure `onCreate()` calls `super.onCreate();`.
 >
 
@@ -396,7 +385,7 @@ This is typically caused by APNs service instability. Try the following:
 4. Test on a different iOS device.
 
 ### Incoming call UI does not appear after app is killed?
-- Confirm that push notifications are received. If not, check if the IM console certificate was uploaded correctly. Refer to Step 1 of **Vendor Configuration.**
+- Confirm that push notifications are received. If not, check if the IM console certificate was uploaded correctly. .**
 
 - Verify that FCM Data Message is selected in the console.
 
@@ -410,7 +399,3 @@ To enforce FCM channel usage, call:
 ``` java
 TIMPushManager.getInstance().forceUseFCMPushChannel(true);
 ```
-
-## Contact Us
-
-If you have any questions or suggestions during integration or usage, join the [Telegram](https://t.me/+Lmw2MSqW6ethMGM1) technical discussion group or [contact us](https://trtc.io/contact) for support.

package/resource/knowledge/callkit/core-sdk/ios/answer-call.md

@@ -664,9 +664,6 @@ LoginStore.shared.setSelfInfo(userProfile: userProfile) { result in
 ### Switch Layout Modes
 
 **CallCoreView** supports three built-in layout modes. Use [setLayoutTemplate](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callcoreview/setlayouttemplate(_:)) to set the layout. If not set, **CallCoreView** will automatically use `Float` mode for 1v1 calls and `Grid` mode for multi-party calls.
-| <strong>Float Mode</strong> | <strong>Grid Mode</strong> | <strong>PIP Mode</strong> |
-| --- | --- | --- |
-|  |  |  |
 | - <strong>Layout:</strong> While waiting, display your own video full screen. After answering, show the remote video full screen and your own video as a floating window.<br>- <strong>Interaction:</strong> Drag the small window or tap to swap big/small video. | - <strong>Layout:</strong> All participant videos are tiled in a grid. Best for 2+ participants. Tap to enlarge a video.<br>- <strong>Interaction:</strong> Tap a participant to enlarge their video. | - <strong>Layout:</strong> In 1v1, remote video is fixed; in multi-party, the active speaker is shown full screen.<br>- <strong>Interaction:</strong> Shows your own video while waiting, displays call timer after answering. |
 
 ``` swift
@@ -917,7 +914,6 @@ class CallViewController: UIViewController {
 AtomicXCore SDK supports system PiP via the underlying TRTC engine. When the app goes to the background, the call video can float as a system PiP window above other apps, allowing users to continue video calls while multitasking.
 
 > **Note：**
->
 > 1. Add the `Background Modes` capability in Xcode's `Signing & Capabilities` and enable `Audio, AirPlay, and Picture in Picture`.
 > 2. Requires iOS 15.0 or later.
 
@@ -1075,7 +1071,3 @@ Congratulations! You have implemented the answer call feature. Next, see Making
 ### If the callee is offline and comes online within the call invitation timeout, will they receive the incoming call event?
 
 For one-on-one calls, if the callee comes online within the timeout, they will receive the incoming call invitation. For group calls, if the callee comes online within the timeout, up to 20 unprocessed group messages will be retrieved, and if there is a call invitation, the incoming call event will be triggered.
-
-## Contact Us
-
-If you have any questions or suggestions during the integration or usage process, feel free to join our [Telegram technical group](https://t.me/+Lmw2MSqW6ethMGM1) or [contact us](https://trtc.io/contact) for support.

package/resource/knowledge/callkit/core-sdk/ios/make-call.md

@@ -744,9 +744,6 @@ LoginStore.shared.setSelfInfo(userProfile: userProfile) { result in
 ### Switching Layout Modes
 
 **CallCoreView** supports three built-in layout modes. Use [setLayoutTemplate](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callcoreview/setlayouttemplate(_:)) to set the layout. If not set, **CallCoreView** will automatically use `Float` mode for 1-on-1 calls and `Grid` mode for multi-party calls.
-| <strong>Float Mode</strong> | <strong>Grid Mode</strong> | <strong>PIP Mode</strong> |
-| --- | --- | --- |
-|  |  |  |
 | - <strong>Layout:</strong> While waiting, display your own video full screen. After answering, show the remote video full screen and your own video as a floating window.<br>- <strong>Interaction:</strong> Drag the small window or tap to swap big/small video. | - <strong>Layout:</strong> All participant videos are tiled in a grid. Best for 2+ participants. Tap to enlarge a video.<br>- <strong>Interaction:</strong> Tap a participant to enlarge their video. | - <strong>Layout:</strong> In 1v1, remote video is fixed; in multi-party, the active speaker is shown full screen.<br>- <strong>Interaction:</strong> Shows your own video while waiting, displays call timer after answering. |
 
 - **setLayoutTemplate Sample code:**
@@ -1012,7 +1009,6 @@ class CallViewController: UIViewController {
 AtomicXCore SDK supports system-level PiP via the underlying TRTC engine. When your app goes to the background, the call video can float above other apps as a system PiP window, so users can continue their video call while multitasking.
 
 > **Note：**
->
 > 1. In Xcode, add `Background Modes` under `Signing & Capabilities` and enable `Audio, AirPlay, and Picture in Picture`.
 > 2. Requires iOS 15.0 or later.
 
@@ -1243,7 +1239,3 @@ Congratulations! You’ve completed the "Make a Call" feature. Next, see Answer
 ### If the callee is offline and comes online within the call invitation timeout, will they receive the incoming call event?
 
 For one-on-one calls, if the callee comes online within the timeout, they will receive an incoming call invitation. For group calls, if the callee comes online within the timeout, up to 20 pending group messages will be retrieved. If there is a call invitation, the incoming call event will be triggered.
-
-## Contact Us
-
-If you have any questions or suggestions during the integration or usage process, feel free to join our [Telegram technical group](https://t.me/+EPk6TMZEZMM5OGY1) or [contact us](https://trtc.io/contact) for support.

package/resource/knowledge/callkit/core-sdk/ios/offline-push.md

@@ -1,15 +1,11 @@
 This guide walks you through integrating VoIP Push functionality using the TIMPush service, designed for headless (UI-less) scenarios with AtomicXCore.
 
 > **Note：**
->
 > - You must [activate the TIMPush service]( the Service) before using **VoIP** Push.
 > - LiveCommunicationKit requires iOS 17.4 or later.
 > - VoIP Push requires a dedicated certificate. Standard APNs push certificates cannot be reused. You must apply for a VoIP Push certificate separately through the Apple Developer portal.
 
 After following this guide to integrate Apple LiveCommunicationKit, your app will support native call experiences similar to WeChat. Even if your app is terminated or the device is locked, the system will present a full-screen incoming call interface automatically:
-| <strong>Before Answering</strong> | <strong>After Answering</strong> |
-| --- | --- |
-|  |  |
 
 # Prerequisites
 
@@ -18,7 +14,6 @@ After following this guide to integrate Apple LiveCommunicationKit, your app wil
 Go to the [Chat Console > Plugin Marketplace](https://console.trtc.io/) and click  **Purchase Now** or **Free Trial** (each app is eligible for a one-time, 7-day free trial).
 
 > **Note：**
->
 > The push plugin will stop providing push services (including offline message push and broadcast/tag push) when your trial or subscription expires. To prevent service interruption, please purchase or renew your subscription in advance.
 >
 
@@ -244,7 +239,6 @@ extension VoIPPushManager: PKPushRegistryDelegate {
 ```
 
 > **Note：**
->
 > Only report the VoIP Token after the Chat SDK login is successful. Do not report immediately when the token is obtained.
 >
 
@@ -387,7 +381,6 @@ You can customize the caller information and call type shown on the incoming cal
 | capabilities | Conversation.Capabilities | Required | Call type:<br>- .video: video call (shows video icon)<br>- .playingTones: audio call (shows audio icon) |
 
 > **Note：**
->
 > - After the user taps "Answer" or "Hang Up", the system will invoke the [ConversationManagerDelegate](https://developer.apple.com/documentation/livecommunicationkit/conversationmanagerdelegate) callback. Implement your answer/hang up logic in this callback (e.g., navigate to your call page, call the [CallStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/callstore/) API, etc.).
 > - Reference: [Apple LiveCommunicationKit](https://developer.apple.com/documentation/livecommunicationkit) Official Documentation
 
@@ -522,7 +515,3 @@ You can customize the incoming call notification using Conversation.Update, incl
 - Call type (capabilities: .video or .playingTones)
 
 - Other custom fields for more details, refer to the [Apple LiveCommunicationKit](https://developer.apple.com/documentation/livecommunicationkit) official documentation.
-
-# Contact Us
-
-If you have any questions or suggestions during integration or use, join the [Telegram](https://t.me/+Lmw2MSqW6ethMGM1) technical group or [Contact Us](https://trtc.io/contact) for support.