@tencentcloud/sdk-mcp 1.7.7 → 1.7.9-beta.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +13 -0
- package/README.md +7 -9
- package/index.js +8 -8
- package/knowledge/chunker.js +1 -0
- package/knowledge/doc-url-resolver.js +16 -9
- package/knowledge/embedding/build-vectors.js +92 -0
- package/knowledge/embedding/embed-model.js +41 -0
- package/knowledge/embedding/vector-augment.js +126 -0
- package/knowledge/embedding/vector-index.js +70 -0
- package/knowledge/frontmatter-meta.js +23 -0
- package/knowledge/path-meta.js +56 -0
- package/knowledge/search/exact-lookup.js +145 -16
- package/knowledge/search/filter-pool.js +77 -33
- package/knowledge/search/rank-profile.js +25 -0
- package/knowledge/search/requires-framework.js +4 -1
- package/knowledge/search/search-core.js +74 -13
- package/knowledge/search/search-knowledge.js +24 -34
- package/knowledge/search/search-pass.js +495 -169
- package/knowledge/search/url-row-scorer.js +24 -6
- package/package.json +3 -1
- package/resource/index/manifest.json +1 -1
- package/resource/index/vectors/index.json +4 -0
- package/resource/integration/callkit/preset/android/integration.md +0 -2
- package/resource/integration/callkit/preset/ios/integration.md +0 -2
- package/resource/integration/chat/preset/react/integration.md +9 -5
- package/resource/integration/chat/preset/uni-app/integration.md +4 -0
- package/resource/integration/chat/preset/vue/integration.md +10 -6
- package/resource/integration/livekit/preset/live/android/prepare-integration.md +0 -4
- package/resource/integration/livekit/preset/live/ios/prepare-integration.md +0 -4
- package/resource/integration/roomkit/preset/vue/integration.md +154 -208
- package/resource/knowledge/callkit/best-practice/android/video-chat-dating.md +0 -2
- package/resource/knowledge/callkit/core-sdk/android/answer-call.md +0 -2
- package/resource/knowledge/callkit/core-sdk/android/make-call.md +0 -2
- package/resource/knowledge/callkit/core-sdk/flutter/answer-call.md +0 -4
- package/resource/knowledge/callkit/core-sdk/flutter/make-call.md +0 -2
- package/resource/knowledge/callkit/core-sdk/flutter/offline-push.md +0 -2
- package/resource/knowledge/callkit/core-sdk/ios/answer-call.md +0 -2
- package/resource/knowledge/callkit/core-sdk/ios/make-call.md +0 -4
- package/resource/knowledge/callkit/core-sdk/ios/offline-push.md +0 -2
- package/resource/knowledge/callkit/core-sdk/uni-app/answer-call.md +0 -2
- package/resource/knowledge/callkit/core-sdk/uni-app/make-call.md +0 -2
- package/resource/knowledge/callkit/faq/ios.md +0 -2
- package/resource/knowledge/callkit/faq/uniapp-app.md +0 -2
- package/resource/knowledge/callkit/preset/miniprogram/integration.md +2 -3
- package/resource/knowledge/callkit/preset/miniprogram/uniapp-integration.md +0 -2
- package/resource/knowledge/chat/preset/ios-uikit/integration.md +0 -16
- package/resource/knowledge/chat/preset/react/h5/integration.md +16 -5
- package/resource/knowledge/chat/preset/vue/features/conversation-list.md +6 -3
- package/resource/knowledge/chat/preset/vue/h5/integration.md +7 -4
- package/resource/knowledge/iot/app/activate-service.md +95 -0
- package/resource/knowledge/iot/app/demo/android.md +93 -0
- package/resource/knowledge/iot/app/demo/ios.md +87 -0
- package/resource/knowledge/iot/app/demo/miniprogram.md +79 -0
- package/resource/knowledge/iot/app/device-binding.md +378 -0
- package/resource/knowledge/iot/app/device-sharing.md +414 -0
- package/resource/knowledge/iot/app/family-management.md +762 -0
- package/resource/knowledge/iot/app/integration/android.md +328 -0
- package/resource/knowledge/iot/app/integration/harmonyos.md +326 -0
- package/resource/knowledge/iot/app/integration/ios.md +351 -0
- package/resource/knowledge/iot/app/integration/miniprogram.md +268 -0
- package/resource/knowledge/iot/app/monitor-playback.md +557 -0
- package/resource/knowledge/iot/app/remote-control.md +139 -0
- package/resource/knowledge/iot/app/video-call.md +559 -0
- package/resource/knowledge/iot/app/wechat-call/device-call-miniprogram.md +204 -0
- package/resource/knowledge/iot/app/wechat-call/miniprogram-call-device.md +193 -0
- package/resource/knowledge/iot/client-api/app/android/txiotcallsession.md +189 -0
- package/resource/knowledge/iot/client-api/app/android/txiotcloudstorage.md +77 -0
- package/resource/knowledge/iot/client-api/app/android/txiotdevicemanager.md +175 -0
- package/resource/knowledge/iot/client-api/app/android/txiotengine.md +172 -0
- package/resource/knowledge/iot/client-api/app/android/txiotenginedef.md +163 -0
- package/resource/knowledge/iot/client-api/app/android/txiotfamilymanager.md +146 -0
- package/resource/knowledge/iot/client-api/app/android/txiotmonitorsession.md +246 -0
- package/resource/knowledge/iot/client-api/app/harmonyos/txiotcallsession.md +191 -0
- package/resource/knowledge/iot/client-api/app/harmonyos/txiotcloudstorage.md +77 -0
- package/resource/knowledge/iot/client-api/app/harmonyos/txiotdevicemanager.md +183 -0
- package/resource/knowledge/iot/client-api/app/harmonyos/txiotengine.md +186 -0
- package/resource/knowledge/iot/client-api/app/harmonyos/txiotenginedef.md +164 -0
- package/resource/knowledge/iot/client-api/app/harmonyos/txiotfamilymanager.md +150 -0
- package/resource/knowledge/iot/client-api/app/harmonyos/txiotmonitorsession.md +252 -0
- package/resource/knowledge/iot/client-api/app/ios/txiotcallsession.md +199 -0
- package/resource/knowledge/iot/client-api/app/ios/txiotcloudstorage.md +76 -0
- package/resource/knowledge/iot/client-api/app/ios/txiotdevicemanager.md +173 -0
- package/resource/knowledge/iot/client-api/app/ios/txiotengine.md +173 -0
- package/resource/knowledge/iot/client-api/app/ios/txiotenginedef.md +171 -0
- package/resource/knowledge/iot/client-api/app/ios/txiotfamilymanager.md +146 -0
- package/resource/knowledge/iot/client-api/app/ios/txiotmonitorsession.md +250 -0
- package/resource/knowledge/iot/client-api/app/miniprogram/txiotcallsession.md +180 -0
- package/resource/knowledge/iot/client-api/app/miniprogram/txiotcloudstorage.md +76 -0
- package/resource/knowledge/iot/client-api/app/miniprogram/txiotdevicemanager.md +281 -0
- package/resource/knowledge/iot/client-api/app/miniprogram/txiotengine.md +183 -0
- package/resource/knowledge/iot/client-api/app/miniprogram/txiotenginedef.md +152 -0
- package/resource/knowledge/iot/client-api/app/miniprogram/txiotfamilymanager.md +179 -0
- package/resource/knowledge/iot/client-api/app/miniprogram/txiotmonitorsession.md +226 -0
- package/resource/knowledge/iot/client-api/device/android-smart-device.md +813 -0
- package/resource/knowledge/iot/client-api/device/linux-rtos-device.md +2027 -0
- package/resource/knowledge/iot/device/activate-service.md +167 -0
- package/resource/knowledge/iot/device/ai-voice-chat/advanced-features/custom-agent.md +171 -0
- package/resource/knowledge/iot/device/ai-voice-chat/advanced-features/smart-device-control.md +721 -0
- package/resource/knowledge/iot/device/ai-voice-chat/integration-guide/android-smart-device.md +247 -0
- package/resource/knowledge/iot/device/ai-voice-chat/integration-guide/linux-rtos-device.md +368 -0
- package/resource/knowledge/iot/device/ai-voice-chat/overview.md +84 -0
- package/resource/knowledge/iot/device/cloud-storage.md +696 -0
- package/resource/knowledge/iot/device/data-model.md +972 -0
- package/resource/knowledge/iot/device/demo/android-smart-device.md +97 -0
- package/resource/knowledge/iot/device/demo/linux-rtos-device.md +106 -0
- package/resource/knowledge/iot/device/device-ota-upgrade.md +237 -0
- package/resource/knowledge/iot/device/dynamic-registration/android-smart-device.md +275 -0
- package/resource/knowledge/iot/device/dynamic-registration/linux-rtos-device.md +297 -0
- package/resource/knowledge/iot/device/login-and-register/android-smart-device.md +131 -0
- package/resource/knowledge/iot/device/login-and-register/linux-rtos-device.md +291 -0
- package/resource/knowledge/iot/device/monitor-pushing/android-smart-device.md +237 -0
- package/resource/knowledge/iot/device/monitor-pushing/linux-rtos-device.md +493 -0
- package/resource/knowledge/iot/device/video-call/android-smart-device.md +299 -0
- package/resource/knowledge/iot/device/video-call/linux-rtos-device.md +465 -0
- package/resource/knowledge/iot/device/wechat-call/android-smart-device.md +534 -0
- package/resource/knowledge/iot/device/wechat-call/linux-rtos-device.md +681 -0
- package/resource/knowledge/iot/kids-watch/overview.md +28 -0
- package/resource/knowledge/iot/security-camera/activate-service.md +74 -0
- package/resource/knowledge/iot/security-camera/monitor-playback/app-integration.md +302 -0
- package/resource/knowledge/iot/security-camera/monitor-playback/device-integration/android.md +237 -0
- package/resource/knowledge/iot/security-camera/monitor-playback/device-integration/linux-rtos.md +493 -0
- package/resource/knowledge/iot/security-camera/overview.md +31 -0
- package/resource/knowledge/iot/security-camera/ptz-control.md +153 -0
- package/resource/knowledge/iot/security-camera/recording-and-snapshot.md +182 -0
- package/resource/knowledge/iot/security-camera/voice-intercom.md +174 -0
- package/resource/knowledge/iot/smart-vision/serviceoverview.md +114 -0
- package/resource/knowledge/iot/voice-recorder/app-demo.md +99 -0
- package/resource/knowledge/iot/voice-recorder/device-demo.md +189 -0
- package/resource/knowledge/iot/voice-recorder/overview.md +64 -0
- package/resource/knowledge/livekit/core-sdk/features/android/base-beauty.md +0 -2
- package/resource/knowledge/livekit/core-sdk/features/android/gift.md +0 -4
- package/resource/knowledge/livekit/core-sdk/features/android/live-list.md +0 -2
- package/resource/knowledge/livekit/core-sdk/features/flutter/audio-effect.md +0 -2
- package/resource/knowledge/livekit/core-sdk/features/flutter/base-beauty.md +0 -2
- package/resource/knowledge/livekit/core-sdk/features/flutter/gift.md +0 -4
- package/resource/knowledge/livekit/core-sdk/features/ios/base-beauty.md +0 -2
- package/resource/knowledge/livekit/core-sdk/features/ios/gift.md +0 -4
- package/resource/knowledge/livekit/core-sdk/features/ios/live-list.md +0 -2
- package/resource/knowledge/livekit/core-sdk/features/uni-app/base-beauty.md +0 -2
- package/resource/knowledge/livekit/core-sdk/features/uni-app/gift.md +0 -4
- package/resource/knowledge/livekit/core-sdk/live/android/co-guest-interaction.md +0 -4
- package/resource/knowledge/livekit/core-sdk/live/android/host-interaction.md +0 -10
- package/resource/knowledge/livekit/core-sdk/live/android/integration.md +0 -2
- package/resource/knowledge/livekit/core-sdk/live/flutter/co-guest-interaction.md +0 -2
- package/resource/knowledge/livekit/core-sdk/live/flutter/host-interaction.md +0 -10
- package/resource/knowledge/livekit/core-sdk/live/flutter/integration.md +0 -2
- package/resource/knowledge/livekit/core-sdk/live/ios/co-guest-interaction.md +0 -4
- package/resource/knowledge/livekit/core-sdk/live/ios/host-interaction.md +0 -10
- package/resource/knowledge/livekit/core-sdk/live/ios/integration.md +0 -2
- package/resource/knowledge/livekit/core-sdk/live/uni-app/co-guest-interaction.md +0 -4
- package/resource/knowledge/livekit/core-sdk/live/uni-app/host-interaction.md +0 -4
- package/resource/knowledge/livekit/core-sdk/live/uni-app/integration.md +0 -2
- package/resource/knowledge/livekit/core-sdk/voice/android/co-guest-interaction.md +0 -2
- package/resource/knowledge/livekit/core-sdk/voice/android/host-interaction.md +0 -4
- package/resource/knowledge/livekit/core-sdk/voice/android/integration.md +0 -4
- package/resource/knowledge/livekit/core-sdk/voice/flutter/integration.md +0 -2
- package/resource/knowledge/livekit/core-sdk/voice/ios/co-guest-interaction.md +0 -2
- package/resource/knowledge/livekit/core-sdk/voice/ios/host-interaction.md +0 -4
- package/resource/knowledge/livekit/core-sdk/voice/ios/integration.md +0 -4
- package/resource/knowledge/livekit/core-sdk/voice/uni-app/co-guest-interaction.md +0 -2
- package/resource/knowledge/livekit/core-sdk/voice/uni-app/integration.md +0 -2
- package/resource/knowledge/livekit/faq/error-code.md +0 -2
- package/resource/knowledge/push/config/android/honor.md +16 -1
- package/resource/knowledge/push/config/android/huawei.md +20 -4
- package/resource/knowledge/push/config/android/meizu.md +19 -5
- package/resource/knowledge/push/config/android/vivo.md +20 -1
- package/resource/knowledge/push/config/donut.md +0 -2
- package/resource/knowledge/push/config/harmonyos.md +21 -5
- package/resource/knowledge/push/integration/android.md +0 -5
- package/resource/knowledge/push/integration/donut.md +0 -3
- package/resource/knowledge/push/integration/flutter.md +1 -4
- package/resource/knowledge/push/integration/harmonyos.md +0 -3
- package/resource/knowledge/push/integration/ios.md +0 -3
- package/resource/knowledge/push/integration/react-native.md +0 -5
- package/resource/knowledge/push/integration/uni-app.md +0 -3
- package/resource/knowledge/push/integration/unity.md +0 -3
- package/resource/knowledge/push/integration/unreal-engine.md +0 -3
- package/resource/knowledge/roomkit/core-sdk/android/call-user-to-room.md +0 -2
- package/resource/knowledge/roomkit/core-sdk/android/room-participant-state.md +0 -2
- package/resource/knowledge/roomkit/core-sdk/android/room-state.md +0 -2
- package/resource/knowledge/roomkit/core-sdk/android/schedule-room.md +0 -2
- package/resource/knowledge/roomkit/core-sdk/flutter/call-user-to-room.md +0 -2
- package/resource/knowledge/roomkit/core-sdk/flutter/room-participant-state.md +0 -2
- package/resource/knowledge/roomkit/core-sdk/flutter/room-state.md +0 -2
- package/resource/knowledge/roomkit/core-sdk/flutter/schedule-room.md +0 -2
- package/resource/knowledge/roomkit/core-sdk/ios/call-user-to-room.md +0 -2
- package/resource/knowledge/roomkit/core-sdk/ios/room-participant-state.md +0 -2
- package/resource/knowledge/roomkit/core-sdk/ios/room-state.md +0 -2
- package/resource/knowledge/roomkit/core-sdk/ios/schedule-room.md +0 -2
- package/resource/knowledge/roomkit/core-sdk/vue/room-view.md +0 -3
- package/resource/knowledge/roomkit/preset/uniapp-app/integration.md +18 -14
- package/resource/knowledge/rtcengine/web/how_to_run_web_sdk_demo.md +0 -2
- package/resource/knowledge/rtcengine/web/plugin/23-advanced-support-detection.md +30 -0
- package/resource/knowledge/rtcengine/web/plugin/24-advanced-network-quality.md +0 -2
- package/resource/knowledge/rtcengine/web/plugin/31-advanced-plugins-overview.md +1 -1
- package/resource/knowledge/rtcengine/web/plugin/35-advanced-ai-denoiser.md +1 -1
- package/resource/knowledge/rtcengine/web/plugin/36-advanced-virtual-background.md +4 -0
- package/resource/knowledge/trtc/android/TRTCCloud.md +94 -85
- package/resource/knowledge/trtc/android/TRTCCloudDef.md +48 -46
- package/resource/knowledge/trtc/android/TRTCCloudListener.md +48 -48
- package/resource/knowledge/trtc/android/TXAudioEffectManager.md +18 -18
- package/resource/knowledge/trtc/android/TXDeviceManager.md +4 -4
- package/resource/knowledge/trtc/android/TXLiteAVCode.md +1 -0
- package/resource/knowledge/trtc/c++/ITRTCCloud.md +90 -90
- package/resource/knowledge/trtc/c++/ITXAudioEffectManager.md +18 -18
- package/resource/knowledge/trtc/c++/ITXDeviceManager.md +9 -9
- package/resource/knowledge/trtc/c++/TRTCCloudCallback.md +47 -47
- package/resource/knowledge/trtc/c++/TRTCTypeDef.md +47 -45
- package/resource/knowledge/trtc/c++/TXLiteAVCode.md +1 -0
- package/resource/knowledge/trtc/ios/TRTCCloud.md +93 -93
- package/resource/knowledge/trtc/ios/TRTCCloudDelegate.md +50 -50
- package/resource/knowledge/trtc/ios/TXAudioEffectManager.md +8 -8
- package/resource/knowledge/trtc/ios/TXDeviceManager.md +9 -9
- package/resource/knowledge/trtc/ios/TXLiteAVCode.md +1 -0
- package/resource/knowledge/trtc/ios/TXLiveSDKTypeDef.md +48 -46
- package/server-config.js +8 -9
- package/server.js +1 -1
- package/tools/common/finalize_answer.js +1 -1
- package/tools/common/present_framework_choice.js +1 -1
- package/tools/common/search_trtc_knowledge.js +22 -3
- package/tools/definitions/search_trtc_knowledge_def.js +3 -2
- package/utils/preflight-route.js +19 -2
- package/utils/report-cls-client.js +1 -1
- package/utils/report-es-client.js +1 -1
|
@@ -13,8 +13,6 @@
|
|
|
13
13
|
|**CoHostLayoutTemplate**|枚举|连线时,用于指定房间麦位布局模板,例如 `HOST_STATIC_VOICE_6V6`。|
|
|
14
14
|
|**BattleConfig**|数据模型|配置 PK 的详细信息,例如 PK 时长 (`duration`) 和是否需要二次响应 (`needResponse`)。|
|
|
15
15
|
|
|
16
|
-
## 前提条件
|
|
17
|
-
|
|
18
16
|
## 主播发起一场连线
|
|
19
17
|
|
|
20
18
|
### 步骤1:查看正在开播中的主播列表
|
|
@@ -430,8 +428,6 @@ override fun onCoHostRequestReceived(inviter: SeatUserInfo, extensionInfo: Strin
|
|
|
430
428
|
|高级礼物|礼物价值 × 12|100元礼物 → 1200分|
|
|
431
429
|
|特效礼物|固定高分数|520元礼物 → 1314分|
|
|
432
430
|
|
|
433
|
-
#### REST API 调用流程
|
|
434
|
-
|
|
435
431
|
#### 关键流程说明
|
|
436
432
|
1. **获取 PK 状态**:
|
|
437
433
|
|
|
@@ -12,8 +12,6 @@
|
|
|
12
12
|
|
|
13
13
|
## 准备工作
|
|
14
14
|
|
|
15
|
-
### 步骤1:开通服务
|
|
16
|
-
|
|
17
15
|
### 步骤2:在当前项目中导入 AtomicXCore
|
|
18
16
|
|
|
19
17
|
**安装组件**:请在您的 `build.gradle` 文件中添加 `implementation 'com.tencent.atomicx:atomicxcore:latest'` 依赖,然后执行 `Gradle Sync`。
|
|
@@ -422,8 +420,6 @@ class YourAudienceActivity : AppCompatActivity() {
|
|
|
422
420
|
|
|
423
421
|
在语聊房场景中,一个常见的需求是当麦上用户说话时,在其头像上显示一个波浪动画,以提示全房间用户“谁在说话”,`LiveSeatStore` 提供了 `speakingUsers` 数据流,专门用于实现此功能。
|
|
424
422
|
|
|
425
|
-
#### 实现效果
|
|
426
|
-
|
|
427
423
|
#### 实现方式
|
|
428
424
|
|
|
429
425
|
> **提示:**
|
|
@@ -11,8 +11,6 @@
|
|
|
11
11
|
|**CoHostLayoutTemplate**|enum|连线时,用于指定房间麦位布局模板,例如`.hostStaticVoice6v6`。|
|
|
12
12
|
|**BattleConfig**|struct|配置 PK 的详细信息,例如 PK 时长 (`duration`) 和是否需要二次响应 (`needResponse`)。|
|
|
13
13
|
|
|
14
|
-
## 前提条件
|
|
15
|
-
|
|
16
14
|
## 主播发起一场连线
|
|
17
15
|
|
|
18
16
|
### 步骤1:查看正在开播中的主播列表
|
|
@@ -526,8 +524,6 @@ coHostStore.coHostEventPublisher
|
|
|
526
524
|
|高级礼物|礼物价值 × 12|100元礼物 → 1200分|
|
|
527
525
|
|特效礼物|固定高分数|520元礼物 → 1314分<br>|
|
|
528
526
|
|
|
529
|
-
#### REST API 调用流程
|
|
530
|
-
|
|
531
527
|
#### 关键流程说明
|
|
532
528
|
1. **获取 PK 状态**:
|
|
533
529
|
|
|
@@ -12,8 +12,6 @@
|
|
|
12
12
|
|
|
13
13
|
## 准备工作
|
|
14
14
|
|
|
15
|
-
### 步骤1:开通服务
|
|
16
|
-
|
|
17
15
|
### 步骤2:在当前项目中导入 AtomicXCore
|
|
18
16
|
1. **安装组件**:请在您的 **Podfile** 文件中添加 `pod 'AtomicXCore'` 依赖,然后执行 `pod install`。
|
|
19
17
|
|
|
@@ -390,8 +388,6 @@ class YourAudienceViewController: UIViewController {
|
|
|
390
388
|
|
|
391
389
|
在语聊房场景中,一个常见的需求是当麦上用户说话时,在其头像上显示一个波浪动画,以提示全房间用户“谁在说话”,`LiveSeatStore` 提供了 `speakingUsers` 数据流,专门用于实现此功能。
|
|
392
390
|
|
|
393
|
-
#### 实现效果
|
|
394
|
-
|
|
395
391
|
#### 实现方式
|
|
396
392
|
|
|
397
393
|
> **提示:**
|
|
@@ -57,7 +57,22 @@
|
|
|
57
57
|
|
|
58
58
|
### 配置回执和点击统计
|
|
59
59
|
|
|
60
|
-
如需统计消息触达或点击数据,请在厂商配置阶段设置回执地址为:`https
|
|
60
|
+
如需统计消息触达或点击数据,请在厂商配置阶段设置回执地址为:`https://<domain>/v3/offline_push_report/honor`,其中 domain 取决于你的站点。目前支持的站点有:
|
|
61
|
+
- 中 国: `https://api.im.qcloud.com/v3/offline_push_report/honor`
|
|
62
|
+
|
|
63
|
+
- 新加坡: `https://apisgp.im.qcloud.com/v3/offline_push_report/honor`
|
|
64
|
+
|
|
65
|
+
- 德 国: `https://apiger.im.qcloud.com/v3/offline_push_report/honor`
|
|
66
|
+
|
|
67
|
+
- 美 国: `https://apiusa.im.qcloud.com/v3/offline_push_report/honor`
|
|
68
|
+
|
|
69
|
+
- 韩 国: `https://apikr.im.qcloud.com/v3/offline_push_report/honor`
|
|
70
|
+
|
|
71
|
+
- 印 尼:`https://apiidn.im.qcloud.com/v3/offline_push_report/honor`
|
|
72
|
+
|
|
73
|
+
- 日 本: `https://apijpn.im.qcloud.com/v3/offline_push_report/honor`
|
|
74
|
+
|
|
75
|
+
- 中 东: `https://apiksa.im.qcloud.com/v3/offline_push_report/honor`
|
|
61
76
|
|
|
62
77
|
## 合规提示
|
|
63
78
|
|
|
@@ -55,11 +55,27 @@
|
|
|
55
55
|
|
|
56
56
|
### 配置回执和点击统计
|
|
57
57
|
|
|
58
|
-
|
|
58
|
+
如需统计消息触达或点击数据,请在厂商配置阶段设置回执地址为:`https://<domain>/v3/offline_push_report/huawei`,其中 domain 取决于你的站点。目前支持的站点有:
|
|
59
|
+
- 中 国: `https://api.im.qcloud.com/v3/offline_push_report/huawei`
|
|
59
60
|
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
61
|
+
- 新加坡: `https://apisgp.im.qcloud.com/v3/offline_push_report/huawei`
|
|
62
|
+
|
|
63
|
+
- 德 国: `https://apiger.im.qcloud.com/v3/offline_push_report/huawei`
|
|
64
|
+
|
|
65
|
+
- 美 国: `https://apiusa.im.qcloud.com/v3/offline_push_report/huawei`
|
|
66
|
+
|
|
67
|
+
- 韩 国: `https://apikr.im.qcloud.com/v3/offline_push_report/huawei`
|
|
68
|
+
|
|
69
|
+
- 印 尼:`https://apiidn.im.qcloud.com/v3/offline_push_report/huawei`
|
|
70
|
+
|
|
71
|
+
- 日 本: `https://apijpn.im.qcloud.com/v3/offline_push_report/huawei`
|
|
72
|
+
|
|
73
|
+
- 中 东: `https://apiksa.im.qcloud.com/v3/offline_push_report/huawei`
|
|
74
|
+
|
|
75
|
+
> **注意:**
|
|
76
|
+
>
|
|
77
|
+
> 华为推送证书 ID <= 11344 时,使用华为推送 v2 版本接口,不支持触达和点击回执,请重新生成更新证书 ID 。
|
|
78
|
+
>
|
|
63
79
|
|
|
64
80
|
## 消息分类限制对推送效果的影响
|
|
65
81
|
|
|
@@ -56,13 +56,27 @@
|
|
|
56
56
|
|
|
57
57
|
### 配置回执和点击统计
|
|
58
58
|
|
|
59
|
-
|
|
59
|
+
如需统计消息触达或点击数据,请在厂商配置阶段设置回执地址为:`https://<domain>/v3/offline_push_report/meizu`,其中 domain 取决于你的站点。目前支持的站点有:
|
|
60
|
+
- 中 国: `https://api.im.qcloud.com/v3/offline_push_report/meizu`
|
|
60
61
|
|
|
61
|
-
|
|
62
|
+
- 新加坡: `https://apisgp.im.qcloud.com/v3/offline_push_report/meizu`
|
|
62
63
|
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
64
|
+
- 德 国: `https://apiger.im.qcloud.com/v3/offline_push_report/meizu`
|
|
65
|
+
|
|
66
|
+
- 美 国: `https://apiusa.im.qcloud.com/v3/offline_push_report/meizu`
|
|
67
|
+
|
|
68
|
+
- 韩 国: `https://apikr.im.qcloud.com/v3/offline_push_report/meizu`
|
|
69
|
+
|
|
70
|
+
- 印 尼:`https://apiidn.im.qcloud.com/v3/offline_push_report/meizu`
|
|
71
|
+
|
|
72
|
+
- 日 本: `https://apijpn.im.qcloud.com/v3/offline_push_report/meizu`
|
|
73
|
+
|
|
74
|
+
- 中 东: `https://apiksa.im.qcloud.com/v3/offline_push_report/meizu`
|
|
75
|
+
|
|
76
|
+
> **注意:**
|
|
77
|
+
>
|
|
78
|
+
> 打开回执开关后,请务必确保回执地址正确配置。不配置或者配置地址错误,都会影响推送功能。
|
|
79
|
+
>
|
|
66
80
|
|
|
67
81
|
## 消息分类限制对推送效果的影响
|
|
68
82
|
|
|
@@ -49,7 +49,26 @@
|
|
|
49
49
|
|
|
50
50
|
### 配置回执和点击统计
|
|
51
51
|
|
|
52
|
-
|
|
52
|
+
如需统计消息触达或点击数据,请在厂商配置阶段设置 App 回执地址为:`https://<domain>/v3/offline_push_report/vivo`,并在腾讯云控制台设置回执 ID,其中 domain 取决于你的站点。目前支持的站点有:
|
|
53
|
+
- 中 国: `https://api.im.qcloud.com/v3/offline_push_report/vivo`
|
|
54
|
+
|
|
55
|
+
- 新加坡: `https://apisgp.im.qcloud.com/v3/offline_push_report/vivo`
|
|
56
|
+
|
|
57
|
+
- 德 国: `https://apiger.im.qcloud.com/v3/offline_push_report/vivo`
|
|
58
|
+
|
|
59
|
+
- 美 国: `https://apiusa.im.qcloud.com/v3/offline_push_report/vivo`
|
|
60
|
+
|
|
61
|
+
- 韩 国: `https://apikr.im.qcloud.com/v3/offline_push_report/vivo`
|
|
62
|
+
|
|
63
|
+
- 印 尼:`https://apiidn.im.qcloud.com/v3/offline_push_report/vivo`
|
|
64
|
+
|
|
65
|
+
- 日 本: `https://apijpn.im.qcloud.com/v3/offline_push_report/vivo`
|
|
66
|
+
|
|
67
|
+
- 中 东: `https://apiksa.im.qcloud.com/v3/offline_push_report/vivo`
|
|
68
|
+
|
|
69
|
+
|**回调地址配置**|**腾讯云即时通信 IM 控制台**|
|
|
70
|
+
|---------|---------|
|
|
71
|
+
|||
|
|
53
72
|
|
|
54
73
|
## 消息分类限制对推送效果的影响
|
|
55
74
|
|
|
@@ -332,8 +332,6 @@ p8 证书:p8 证书没有到期日期,因此您无需担心证书过期。
|
|
|
332
332
|
|
|
333
333
|
【p12 证书】
|
|
334
334
|
|
|
335
|
-
#### 步骤1:申请 APNs 证书
|
|
336
|
-
|
|
337
335
|
#### 开启 App 远程推送
|
|
338
336
|
1. 登录 [苹果开发者中心](https://developer.apple.com/account/) 网站,单击 **Certificates, Identifiers & Profiles** 或者侧栏的 **Certificates, Identifiers & Profiles**,进入 **Certificates, IDs & Profiles** 页面。
|
|
339
337
|
|
|
@@ -14,7 +14,14 @@
|
|
|
14
14
|
### 步骤1:开启推送服务
|
|
15
15
|
1. 登录 [AppGallery Connect](https://developer.huawei.com/consumer/cn/service/josp/agc/index.html#/),在首页选择**开发与服务**,选择对应的项目,单击**立即开通**以开启推送服务。
|
|
16
16
|
|
|
17
|
-
2.
|
|
17
|
+
2. 若项目当前未配置数据处理位置,请在提示中点击**确定**,会弹出设置数据处理位置的弹窗。完成数据处理位置的设置,点击**确定**。
|
|
18
|
+
|
|
19
|
+
5-10 分钟后访问 [AppGallery Connect](https://developer.huawei.com/consumer/cn/service/josp/agc/index.html),**项目设置 > 开放能力管理** 中推送服务能力会显示已勾选。同时,**增长 > 推送服务**中“推送服务”会自动开通。
|
|
20
|
+
|
|
21
|
+
> **说明:**
|
|
22
|
+
>
|
|
23
|
+
> 详情请参考 HarmonyOS 官方文档:[开通推送服务](https://developer.huawei.com/consumer/cn/doc/harmonyos-guides/push-config-setting)。
|
|
24
|
+
>
|
|
18
25
|
|
|
19
26
|
### 步骤2:证书与签名申请
|
|
20
27
|
1. **证书申请:调试阶段必须申请调试证书,发布阶段必须申请发布证书。**
|
|
@@ -42,7 +49,7 @@
|
|
|
42
49
|
|
|
43
50
|
> **说明:**
|
|
44
51
|
>
|
|
45
|
-
> 关于各类型设备如何获取 UDID,请参见 [UDID 获取方法](https://developer.huawei.com/consumer/cn/doc/app/agc-help-add-device-0000002283189937#section67331926102911)。
|
|
52
|
+
> 关于各类型设备如何获取 UDID,请参见 HarmonyOS 官方文档:[UDID 获取方法](https://developer.huawei.com/consumer/cn/doc/app/agc-help-add-device-0000002283189937#section67331926102911)。
|
|
46
53
|
>
|
|
47
54
|
|
|
48
55
|
3. **申请 Profile 文件:调试阶段必须申请调试 Profile 文件,发布阶段必须申请发布 Profile 文件。**
|
|
@@ -59,22 +66,31 @@
|
|
|
59
66
|
|
|
60
67
|
5. **调试阶段自动签名(仅适用调试阶段,不适用发布阶段)**
|
|
61
68
|
|
|
62
|
-
针对开发调试场景,从 DevEco Studio 6.0.0 Beta5 版本开始,新增了更高效的自动签名以及开通 Push Kit 开放能力方案,请参考
|
|
69
|
+
针对开发调试场景,从 DevEco Studio 6.0.0 Beta5 版本开始,新增了更高效的自动签名以及开通 Push Kit 开放能力方案,请参考 HarmonyOS 官方文档:[开通推送服务](https://developer.huawei.com/consumer/cn/doc/harmonyos-guides/push-config-setting)。
|
|
63
70
|
|
|
64
71
|
### 步骤3:创建 IM 控制台证书凭证
|
|
65
72
|
1. 登录 [API Console](https://developer.huawei.com/consumer/cn/console/overview),在页面左侧的导航栏中,单击**我的 API**,确保所选项目已开通推送服务(Push Kit),若未开通,请单击右侧 申请新 HMS API 服务 进行**申请新 HMS API 服务。**
|
|
66
73
|
|
|
67
74
|
2. 单击左侧导航栏中 **API 服务** > **凭证**,在项目下单击**服务账号密钥**下的**创建凭证。**
|
|
68
75
|
|
|
69
|
-
3.
|
|
76
|
+
3. 填写必填项,并单击**生成公私钥**。创建并下载 JSON,下载后的文件就是您的 Service Account 凭据文件。
|
|
70
77
|
|
|
71
78
|
4. 将下载好的文件保存,待下一步 IM 控制台配置使用。
|
|
72
79
|
|
|
80
|
+
> **说明:**
|
|
81
|
+
>
|
|
82
|
+
> 详情请参考 HarmonyOS 官方文档:[API 服务操作指南](https://developer.huawei.com/consumer/cn/doc/start/api-0000001062522591)。
|
|
83
|
+
>
|
|
84
|
+
|
|
73
85
|
### 步骤4:申请场景化权益
|
|
74
86
|
|
|
75
87
|
Push Kit 支持多种场景化消息类型,其中部分场景化消息类型需要您申请特殊权益才能正常发送,像 IM 消息类型场景。
|
|
76
88
|
|
|
77
|
-
登录 [AppGallery Connect](https://developer.huawei.com/consumer/cn/service/josp/agc/index.html)
|
|
89
|
+
登录 [AppGallery Connect](https://developer.huawei.com/consumer/cn/service/josp/agc/index.html),选择**开发与服务**,单击**推送服务**,在**配置**页,单击申请自分类权益。按照提示申请并激活。
|
|
90
|
+
|
|
91
|
+
> **说明:**
|
|
92
|
+
> 详情请参考 HarmonyOS 官方文档:[申请推送场景化消息权益](https://developer.huawei.com/consumer/cn/doc/harmonyos-guides/push-apply-right)。
|
|
93
|
+
>
|
|
78
94
|
|
|
79
95
|
## 腾讯云 IM 控制台配置
|
|
80
96
|
1. 登录腾讯云 [即时通信 IM 控制台](https://console.qcloud.com/avc) ,在**推送服务 Push > 推送设置 > 厂商配置** 中添加 HarmonyOS 证书。
|
|
@@ -36,8 +36,6 @@ implementation 'com.tencent.timpush:xiaomi:latest'
|
|
|
36
36
|
|
|
37
37
|
【华为】
|
|
38
38
|
|
|
39
|
-
#### **1. 添加厂商配置文件**
|
|
40
|
-
|
|
41
39
|
#### **2. 配置 Gradle 插件**
|
|
42
40
|
|
|
43
41
|
##### **追加厂商 Maven 仓库**
|
|
@@ -490,6 +488,3 @@ V2TIMManager.getMessageManager().sendMessage(v2TIMMessage, userID, null, V2TIMMe
|
|
|
490
488
|
`sendMessage` 属于 IMSDK 消息发送能力。仅集成 TIMPush 的用户不需要为了验证离线推送而额外接入完整 Chat 初始化、登录和消息发送流程。
|
|
491
489
|
|
|
492
490
|
如果要实现自定义点击 Push 消息跳转,参考文档 自定义点击推送跳转 处理。
|
|
493
|
-
|
|
494
|
-
## 接入排查
|
|
495
|
-
|
|
@@ -37,7 +37,7 @@ flutter pub add tencent_cloud_chat_push
|
|
|
37
37
|
|
|
38
38
|
【Android】
|
|
39
39
|
|
|
40
|
-
请先按 Android TIMPush
|
|
40
|
+
请先按 Android 集成 TIMPush 和 Android 厂商通道集成 完成原生工程配置。
|
|
41
41
|
|
|
42
42
|
与原生 Android 的差异如下,请按下方完成:
|
|
43
43
|
1. **厂商通道包**:Flutter 插件已处理 TIMPush 基础依赖,**不要**再添加 `com.tencent.timpush:timpush` / `tuicore`。只需按需引入目标厂商通道包。
|
|
@@ -513,6 +513,3 @@ Future<void> removeTIMPushListener() async {
|
|
|
513
513
|
> - 若 App 冷启动后需要立即处理点击事件,建议尽早注册 `listener`,例如在登录流程完成后、业务首页初始化前完成注册。
|
|
514
514
|
|
|
515
515
|
发送离线推送时如需设置 Android 厂商消息分类或通知渠道 ID,可通过 Flutter Chat SDK 的 [OfflinePushInfo](https://pub.dev/documentation/tencent_cloud_chat_sdk/latest/enum_offlinePushInfo/OfflinePushInfo-class.html) 设置;具体字段含义与厂商规则见 Android 厂商通道集成。
|
|
516
|
-
|
|
517
|
-
## 接入排查
|
|
518
|
-
|
|
@@ -1,5 +1,3 @@
|
|
|
1
|
-
### 效果展示
|
|
2
|
-
|
|
3
1
|
## 前提条件
|
|
4
2
|
|
|
5
3
|
开始接入前,请先完成对应原生平台的推送前提配置:请参见 [iOS 前提条件](https://cloud.tencent.com/document/product/269/100627#.E5.89.8D.E6.8F.90.E6.9D.A1.E4.BB.B6) 和 [Android 前提条件](https://cloud.tencent.com/document/product/269/100626#.E5.89.8D.E6.8F.90.E6.9D.A1.E4.BB.B6)。
|
|
@@ -279,6 +277,3 @@ npm run ios
|
|
|
279
277
|
### 步骤7:消息推送触达统计
|
|
280
278
|
|
|
281
279
|
如果您需要统计设备触达数据,请按照 华为/荣耀/vivo/魅族/iOS 步骤完成配置。其余支持厂商不需要配置,FCM 暂不支持推送统计功能。
|
|
282
|
-
|
|
283
|
-
## 接入排查
|
|
284
|
-
|
|
@@ -1,24 +1,28 @@
|
|
|
1
1
|
本文档介绍如何在 uniapp 业务项目中集成 TUIRoomKit,快速获得开箱即用的多人音视频会议能力。
|
|
2
2
|
|
|
3
3
|
## 前提条件
|
|
4
|
+
- **IDE**: HBuilderX 版本 ≥ 4.66。
|
|
4
5
|
|
|
5
|
-
|
|
6
|
+
- **Vue 版本**: Vue3。
|
|
6
7
|
|
|
7
|
-
|
|
8
|
-
- **SDKAppID**:应用标识(必填),腾讯云基于 SDKAppID 完成计费统计。
|
|
8
|
+
- **Node 版本**:Node.js ≥ 18.0.0。
|
|
9
9
|
|
|
10
|
-
-
|
|
10
|
+
- **支持平台**: 仅支持打包为 Android / iOS App,不支持 H5 和小程序。
|
|
11
11
|
|
|
12
|
-
|
|
13
|
-
- **IDE**: HBuilderX 升级到新版本。
|
|
12
|
+
- **支持项目**: uni-app 项目。
|
|
14
13
|
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
14
|
+
> **说明:**
|
|
15
|
+
>
|
|
16
|
+
> Vue2 暂不支持,可通过 [视频会议 SDK 接入反馈问卷](https://wj.qq.com/s2/27395009/ac34/) 进行反馈。
|
|
17
|
+
>
|
|
18
|
+
> uniappx 暂不支持,可通过 [视频会议 SDK 接入反馈问卷](https://wj.qq.com/s2/27395009/ac34/) 进行反馈。
|
|
19
|
+
>
|
|
20
|
+
> H5 和小程序项目,如有需要请参考以下替代方案:
|
|
21
|
+
>
|
|
22
|
+
> - 打包 Web H5,可参考:Web&H5(Vue3)。
|
|
23
|
+
> - 打包小程序,可参考:uni-app(小程序)。
|
|
24
|
+
> 接入过程中遇到任何卡点或有改进建议,欢迎通过 [视频会议 SDK 接入反馈问卷](https://wj.qq.com/s2/27395009/ac34/) 反馈,官方会及时跟进处理。
|
|
25
|
+
>
|
|
22
26
|
|
|
23
27
|
## 集成步骤
|
|
24
28
|
|
|
@@ -176,7 +180,7 @@ cp -r uni_modules/tuikit-atomic-x/quickstart_room/static/* static/ && cp -r uni_
|
|
|
176
180
|
在 `pages/login/login.vue` 中,填入 `SDKAppID`、 `userID`、`SecretKey`,点击**登录**。
|
|
177
181
|
| 参数 | 类型 | 说明 |
|
|
178
182
|
| --- | --- | --- |
|
|
179
|
-
| SDKAppID | Number | SDKAppID 是 RoomKit 客户应用的唯一标识。您可以在 <a href="https://console.cloud.tencent.com/trtc">TRTC 控制台 > 应用管理</a> 创建新应用获取 。<br><strong>说明:</strong><br
|
|
183
|
+
| SDKAppID | Number | SDKAppID 是 RoomKit 客户应用的唯一标识。您可以在 <a href="https://console.cloud.tencent.com/trtc">TRTC 控制台 > 应用管理</a> 创建新应用获取 。<br><strong>说明:</strong><br>- SDKAppID 是 RoomKit 客户应用的唯一标识。每个独立的 App 都应单独申请一个 SDKAppID。不同 SDKAppID 之间天然隔离、互不相通,请勿混用。<br>- 开始使用前,<strong>请先领取 TUIRoomKit 体验版</strong>,领取方式见「开通服务 」。 |
|
|
180
184
|
| SecretKey | String | SecretKey 是 RoomKit 客户应用的密钥。您可以在 <a href="https://console.cloud.tencent.com/trtc">TRTC 控制台 > 应用管理</a> 对应应用获取。<br><strong>安全提示:</strong><br>- 项目示例支持通过 <code>genTestUserSig</code> 函数生成 <code>userSig</code>。该方法中 <code>SecretKey</code> 很容易被反编译逆向破解,一旦您的密钥泄露,攻击者就可以盗用您的腾讯云流量。<strong>该方法仅适合本地跑通功能调试</strong>。 正确的 UserSig 签发方式请参见 <a href="https://cloud.tencent.com/document/product/647/17275#formal">服务端生成 UserSig</a>。<br>- 敏感信息(SecretKey)仅用于 Demo 测试,不可提交到代码仓库或用于生产环境。 |
|
|
181
185
|
| userID | String | 用户的唯一标识符,由您定义,只能包含大小写字母(a-z,A-Z)、数字(0-9)、下划线和连字符。 |
|
|
182
186
|
|