@tencentcloud/sdk-mcp 1.7.0 → 1.7.2
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 +16 -0
- package/README.md +11 -6
- package/knowledge/doc-url-resolver.js +70 -19
- package/knowledge/search/exact-lookup.js +116 -18
- package/knowledge/search/intent-router.js +21 -5
- package/knowledge/search/l1-enrich.js +159 -0
- package/knowledge/search/query-normalizer.js +8 -1
- package/knowledge/search/search-core.js +27 -8
- package/knowledge/search/search-knowledge.js +159 -46
- package/knowledge/search/search-message.js +37 -36
- package/knowledge/search/url-row-idf.js +120 -0
- package/knowledge/search/url-row-scorer.js +306 -227
- package/package.json +3 -1
- package/resource/index/manifest.json +1 -1
- package/resource/integration/callkit/preset/flutter/integration.md +7 -3
- package/resource/integration/chat/preset/android/integration.md +1 -0
- package/resource/integration/chat/preset/flutter/integration.md +110 -10
- package/resource/integration/chat/preset/ios/integration.md +1 -0
- package/resource/integration/chat/preset/react/integration.md +1 -0
- package/resource/integration/chat/preset/uni-app/integration.md +1 -0
- package/resource/integration/chat/preset/vue/integration.md +1 -0
- package/resource/integration/livekit/preset/live/android/prepare-integration.md +1 -0
- package/resource/integration/livekit/preset/live/vue/live-player-desk-integration.md +2 -2
- package/resource/integration/livekit/preset/live/vue/live-pusher-integration.md +3 -3
- package/resource/integration/roomkit/preset/vue/integration.md +1 -0
- package/resource/knowledge/callkit/core-sdk/android/answer-call.md +1 -0
- package/resource/knowledge/callkit/core-sdk/android/make-call.md +1 -0
- package/resource/knowledge/callkit/core-sdk/flutter/answer-call.md +1 -0
- package/resource/knowledge/callkit/core-sdk/flutter/make-call.md +1 -0
- package/resource/knowledge/callkit/core-sdk/ios/answer-call.md +1 -0
- package/resource/knowledge/callkit/core-sdk/ios/make-call.md +1 -0
- package/resource/knowledge/callkit/core-sdk/ios/offline-push.md +1 -1
- package/resource/knowledge/callkit/core-sdk/uni-app/answer-call.md +1 -0
- package/resource/knowledge/callkit/core-sdk/uni-app/make-call.md +1 -0
- package/resource/knowledge/callkit/faq/flutter.md +1 -0
- package/resource/knowledge/callkit/faq/uniapp-app.md +1 -0
- package/resource/knowledge/chat/preset/android-view/integration.md +1 -0
- package/resource/knowledge/chat/preset/ios-uikit/integration.md +1 -0
- package/resource/knowledge/chat/preset/react/features/message-input.md +61 -3
- package/resource/knowledge/chat/preset/react/features/message-list.md +7 -0
- package/resource/knowledge/chat/preset/vue/features/message-input.md +58 -5
- package/resource/knowledge/chat/preset/vue/features/message-list.md +7 -0
- package/resource/knowledge/chat/urls/product.md +8 -8
- package/resource/knowledge/chat/urls/restapi.md +3 -3
- package/resource/knowledge/chat/urls/sdk/android.md +5 -5
- package/resource/knowledge/chat/urls/sdk/flutter.md +5 -5
- package/resource/knowledge/chat/urls/sdk/ios.md +5 -5
- package/resource/knowledge/chat/urls/sdk/web.md +7 -7
- package/resource/knowledge/chat/urls/webhook.md +11 -17
- package/resource/knowledge/push/config/harmonyos.md +1 -1
- package/resource/knowledge/push/config/ios.md +2 -2
- package/resource/knowledge/push/integration/android.md +1 -0
- package/resource/knowledge/push/integration/donut.md +2 -2
- package/resource/knowledge/push/integration/flutter.md +1 -0
- package/resource/knowledge/push/integration/harmonyos.md +1 -1
- package/resource/knowledge/push/integration/ios.md +1 -0
- package/resource/knowledge/push/integration/uni-app.md +1 -0
- package/resource/knowledge/push/integration/unity.md +4 -4
- package/resource/knowledge/push/integration/unreal-engine.md +37 -35
- package/resource/knowledge/roomkit/core-sdk/android/call-user-to-room.md +1 -0
- package/resource/knowledge/roomkit/core-sdk/android/room-participant-state.md +1 -0
- package/resource/knowledge/roomkit/core-sdk/android/room-state.md +1 -0
- package/resource/knowledge/roomkit/core-sdk/android/schedule-room.md +1 -0
- package/resource/knowledge/roomkit/core-sdk/flutter/call-user-to-room.md +1 -0
- package/resource/knowledge/roomkit/core-sdk/flutter/room-participant-state.md +1 -0
- package/resource/knowledge/roomkit/core-sdk/flutter/room-state.md +1 -0
- package/resource/knowledge/roomkit/core-sdk/flutter/schedule-room.md +1 -0
- package/resource/knowledge/roomkit/core-sdk/ios/call-user-to-room.md +1 -0
- package/resource/knowledge/roomkit/core-sdk/ios/room-participant-state.md +1 -0
- package/resource/knowledge/roomkit/core-sdk/ios/room-state.md +1 -0
- package/resource/knowledge/roomkit/core-sdk/ios/schedule-room.md +1 -0
- package/resource/knowledge/roomkit/core-sdk/vue/room-view.md +1 -0
- package/resource/knowledge/roomkit/preset/react/integration.md +1 -0
- package/resource/knowledge/trtc/android/TRTCCloud.md +1 -0
- package/resource/knowledge/trtc/c++/ITRTCCloud.md +1 -0
- package/resource/knowledge/trtc/ios/TRTCCloud.md +1 -0
- package/server.js +4 -4
- package/streamable-http.js +19 -54
- package/tools/common/finalize_answer.js +1 -9
- package/tools/common/search_trtc_knowledge.js +25 -11
- package/tools/definitions/finalize_answer_def.js +2 -2
- package/tools/definitions/search_trtc_knowledge_def.js +4 -2
- package/utils/fetch-doc-content.js +198 -0
- package/utils/preflight-route.js +197 -0
- package/utils/report-cls-client.js +1 -1
- package/utils/report-es-client.js +1 -1
|
@@ -1,10 +1,10 @@
|
|
|
1
1
|
# 服务端 REST API — 官方文档 URL 映射
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
## 通用技术
|
|
4
4
|
|
|
5
5
|
| 子问题 | 目标文档 |
|
|
6
6
|
|--------|---------|
|
|
7
|
-
| UserSig
|
|
7
|
+
| UserSig 生成方法 | `https://cloud.tencent.com/document/product/269/32688` |
|
|
8
8
|
| 服务端消息格式 | `https://cloud.tencent.com/document/product/269/2720` |
|
|
9
9
|
|
|
10
10
|
## 消息相关 REST API
|
|
@@ -19,8 +19,8 @@
|
|
|
19
19
|
| 发送 C2C 流式消息 | `https://cloud.tencent.com/document/product/269/128596` |
|
|
20
20
|
| 发送群流式消息 | `https://cloud.tencent.com/document/product/269/128597` |
|
|
21
21
|
| 直播群广播消息 | `https://cloud.tencent.com/document/product/269/77402` |
|
|
22
|
-
| 导入群消息 | `https://cloud.tencent.com/document/product/269/1635` |
|
|
23
22
|
| 导入单聊消息 | `https://cloud.tencent.com/document/product/269/2568` |
|
|
23
|
+
| 导入群消息 | `https://cloud.tencent.com/document/product/269/1635` |
|
|
24
24
|
| 公众号用户发送广播消息 | `https://cloud.tencent.com/document/product/269/102298` |
|
|
25
25
|
|
|
26
26
|
### 历史消息
|
|
@@ -1,20 +1,20 @@
|
|
|
1
1
|
# Android — SDK 官方文档 URL 映射
|
|
2
2
|
|
|
3
|
-
##
|
|
3
|
+
## SDK 集成和初始化（Android）
|
|
4
4
|
|
|
5
5
|
| 子问题 | 目标文档 |
|
|
6
6
|
|--------|---------|
|
|
7
7
|
| Android SDK 集成 | `https://cloud.tencent.com/document/product/269/75283` |
|
|
8
8
|
| Android SDK 初始化 | `https://cloud.tencent.com/document/product/269/75291` |
|
|
9
9
|
|
|
10
|
-
##
|
|
10
|
+
## 登录与鉴权
|
|
11
11
|
|
|
12
12
|
| 子问题 | 目标文档 |
|
|
13
13
|
|--------|---------|
|
|
14
|
-
| 登录（`login
|
|
15
|
-
| 登出（`logout
|
|
14
|
+
| 登录（`login`） | `https://cloud.tencent.com/document/product/269/75294` |
|
|
15
|
+
| 登出（`logout`） | `https://cloud.tencent.com/document/product/269/75294` |
|
|
16
16
|
|
|
17
|
-
##
|
|
17
|
+
## SDK API 使用
|
|
18
18
|
|
|
19
19
|
| 子问题 | 目标文档 |
|
|
20
20
|
|--------|---------|
|
|
@@ -1,20 +1,20 @@
|
|
|
1
1
|
# Flutter — SDK 官方文档 URL 映射
|
|
2
2
|
|
|
3
|
-
##
|
|
3
|
+
## SDK 集成和初始化（Flutter）
|
|
4
4
|
|
|
5
5
|
| 子问题 | 目标文档 |
|
|
6
6
|
|--------|---------|
|
|
7
7
|
| Flutter SDK 集成 | `https://cloud.tencent.com/document/product/269/75286` |
|
|
8
8
|
| Flutter SDK 初始化 | `https://cloud.tencent.com/document/product/269/75293` |
|
|
9
9
|
|
|
10
|
-
##
|
|
10
|
+
## 登录与鉴权
|
|
11
11
|
|
|
12
12
|
| 子问题 | 目标文档 |
|
|
13
13
|
|--------|---------|
|
|
14
|
-
| 登录（`login
|
|
15
|
-
| 登出（`logout
|
|
14
|
+
| 登录（`login`） | `https://cloud.tencent.com/document/product/269/75296` |
|
|
15
|
+
| 登出（`logout`） | `https://cloud.tencent.com/document/product/269/75296` |
|
|
16
16
|
|
|
17
|
-
##
|
|
17
|
+
## SDK API 使用
|
|
18
18
|
|
|
19
19
|
| 子问题 | 目标文档 |
|
|
20
20
|
|--------|---------|
|
|
@@ -1,20 +1,20 @@
|
|
|
1
1
|
# iOS — SDK 官方文档 URL 映射
|
|
2
2
|
|
|
3
|
-
##
|
|
3
|
+
## SDK 集成和初始化（iOS）
|
|
4
4
|
|
|
5
5
|
| 子问题 | 目标文档 |
|
|
6
6
|
|--------|---------|
|
|
7
7
|
| iOS SDK 集成 | `https://cloud.tencent.com/document/product/269/75284` |
|
|
8
8
|
| iOS SDK 初始化 | `https://cloud.tencent.com/document/product/269/75291` |
|
|
9
9
|
|
|
10
|
-
##
|
|
10
|
+
## 登录与鉴权
|
|
11
11
|
|
|
12
12
|
| 子问题 | 目标文档 |
|
|
13
13
|
|--------|---------|
|
|
14
|
-
| 登录（`login
|
|
15
|
-
| 登出（`logout
|
|
14
|
+
| 登录（`login`） | `https://cloud.tencent.com/document/product/269/75294` |
|
|
15
|
+
| 登出（`logout`） | `https://cloud.tencent.com/document/product/269/75294` |
|
|
16
16
|
|
|
17
|
-
##
|
|
17
|
+
## SDK API 使用
|
|
18
18
|
|
|
19
19
|
| 子问题 | 目标文档 |
|
|
20
20
|
|--------|---------|
|
|
@@ -1,25 +1,25 @@
|
|
|
1
1
|
# Web — SDK 官方文档 URL 映射
|
|
2
2
|
|
|
3
|
-
##
|
|
3
|
+
## SDK 集成和初始化（Web & 小程序）
|
|
4
4
|
|
|
5
5
|
| 子问题 | 目标文档 |
|
|
6
6
|
|--------|---------|
|
|
7
7
|
| Web 端集成和初始化（V4） | `https://cloud.tencent.com/document/product/269/75285` |
|
|
8
8
|
| 小程序端集成和初始化（V4） | `https://cloud.tencent.com/document/product/269/117335` |
|
|
9
9
|
|
|
10
|
-
##
|
|
10
|
+
## 登录与鉴权
|
|
11
11
|
|
|
12
12
|
| 子问题 | 目标文档 |
|
|
13
13
|
|--------|---------|
|
|
14
|
-
| 登录（`login
|
|
15
|
-
| 登出（`logout
|
|
14
|
+
| 登录（`login`） | `https://cloud.tencent.com/document/product/269/75295` |
|
|
15
|
+
| 登出（`logout`） | `https://cloud.tencent.com/document/product/269/75295` |
|
|
16
16
|
|
|
17
|
-
##
|
|
17
|
+
## SDK API 使用
|
|
18
18
|
|
|
19
19
|
| 子问题 | 目标文档 |
|
|
20
20
|
|--------|---------|
|
|
21
21
|
| SDK 消息类型介绍 | `https://cloud.tencent.com/document/product/269/75314` |
|
|
22
|
-
|
|
|
22
|
+
| 消息结构与 Payload 字段（Message payload） | `https://web.sdk.qcloud.com/im/doc/v3/zh-cn/Message.html` |
|
|
23
23
|
| 文本消息（createTextMessage → sendMessage） | `https://cloud.tencent.com/document/product/269/75316` |
|
|
24
24
|
| 群 @ 消息（createTextAtMessage → sendMessage） | `https://cloud.tencent.com/document/product/269/75316` |
|
|
25
25
|
| 图片消息（createImageMessage → sendMessage） | `https://cloud.tencent.com/document/product/269/75316` |
|
|
@@ -76,7 +76,7 @@
|
|
|
76
76
|
| 云端搜索群组（searchGroups） | `https://cloud.tencent.com/document/product/269/114760` |
|
|
77
77
|
| 云端搜索群成员（searchGroupMembers） | `https://cloud.tencent.com/document/product/269/114763` |
|
|
78
78
|
|
|
79
|
-
##
|
|
79
|
+
## 版本升级指南
|
|
80
80
|
|
|
81
81
|
| 子问题 | 目标文档 |
|
|
82
82
|
|--------|---------|
|
|
@@ -1,49 +1,43 @@
|
|
|
1
1
|
# 服务端回调（Webhook）— 官方文档 URL 映射
|
|
2
2
|
|
|
3
|
-
##
|
|
4
|
-
|
|
5
|
-
| 子问题 | 目标文档 |
|
|
6
|
-
|--------|---------|
|
|
7
|
-
| 第三方回调概览 / 配置方法 / 规范 | `https://cloud.tencent.com/document/product/269/1522` |
|
|
8
|
-
|
|
9
|
-
## 在线状态相关回调
|
|
3
|
+
## 在线状态回调
|
|
10
4
|
|
|
11
5
|
| 子问题 | 目标文档 |
|
|
12
6
|
|--------|---------|
|
|
13
7
|
| 用户状态变更回调 | `https://cloud.tencent.com/document/product/269/2570` |
|
|
14
8
|
| 更新用户资料后回调 | `https://cloud.tencent.com/document/product/269/76489` |
|
|
15
9
|
|
|
16
|
-
##
|
|
10
|
+
## 资料关系链回调
|
|
17
11
|
|
|
18
12
|
| 子问题 | 目标文档 |
|
|
19
13
|
|--------|---------|
|
|
20
14
|
| 添加好友之前回调 | `https://cloud.tencent.com/document/product/269/61698` |
|
|
21
|
-
|
|
|
15
|
+
| 添加好友请求回应之前回调 | `https://cloud.tencent.com/document/product/269/61699` |
|
|
22
16
|
| 添加好友之后回调 | `https://cloud.tencent.com/document/product/269/1657` |
|
|
23
17
|
| 删除好友之后回调 | `https://cloud.tencent.com/document/product/269/1659` |
|
|
24
18
|
| 添加黑名单之后回调 | `https://cloud.tencent.com/document/product/269/1660` |
|
|
25
19
|
| 删除黑名单之后回调 | `https://cloud.tencent.com/document/product/269/1661` |
|
|
26
20
|
|
|
27
|
-
##
|
|
21
|
+
## 关注与粉丝回调
|
|
28
22
|
|
|
29
23
|
| 子问题 | 目标文档 |
|
|
30
24
|
|--------|---------|
|
|
31
25
|
| 关注用户之后回调 | `https://cloud.tencent.com/document/product/269/118915` |
|
|
32
26
|
| 取关用户之后回调 | `https://cloud.tencent.com/document/product/269/118916` |
|
|
33
27
|
|
|
34
|
-
##
|
|
28
|
+
## 单聊消息回调
|
|
35
29
|
|
|
36
30
|
| 子问题 | 目标文档 |
|
|
37
31
|
|--------|---------|
|
|
38
32
|
| 设置单聊消息扩展回调 | `https://cloud.tencent.com/document/product/269/126475` |
|
|
39
|
-
|
|
|
40
|
-
|
|
|
33
|
+
| 单聊消息发送之前回调 | `https://cloud.tencent.com/document/product/269/1632` |
|
|
34
|
+
| 单聊消息发送之后回调 | `https://cloud.tencent.com/document/product/269/2716` |
|
|
41
35
|
| 单聊消息已读上报后回调 | `https://cloud.tencent.com/document/product/269/61696` |
|
|
42
36
|
| 单聊消息撤回后回调 | `https://cloud.tencent.com/document/product/269/61697` |
|
|
43
37
|
| 单聊单条消息已读回执之后回调 | `https://cloud.tencent.com/document/product/269/128223` |
|
|
44
38
|
| 单聊消息编辑之后回调 | `https://cloud.tencent.com/document/product/269/128224` |
|
|
45
39
|
|
|
46
|
-
##
|
|
40
|
+
## 群组系统回调
|
|
47
41
|
|
|
48
42
|
| 子问题 | 目标文档 |
|
|
49
43
|
|--------|---------|
|
|
@@ -54,14 +48,14 @@
|
|
|
54
48
|
| 拉人入群之前回调 | `https://cloud.tencent.com/document/product/269/1666` |
|
|
55
49
|
| 新成员入群之后回调 | `https://cloud.tencent.com/document/product/269/1667` |
|
|
56
50
|
| 群成员离开之后回调 | `https://cloud.tencent.com/document/product/269/1668` |
|
|
57
|
-
|
|
|
58
|
-
|
|
|
51
|
+
| 群消息发送之前回调 | `https://cloud.tencent.com/document/product/269/1619` |
|
|
52
|
+
| 群消息发送之后回调 | `https://cloud.tencent.com/document/product/269/2661` |
|
|
59
53
|
| 群组满员之后回调 | `https://cloud.tencent.com/document/product/269/1669` |
|
|
60
54
|
| 群组解散之后回调 | `https://cloud.tencent.com/document/product/269/1670` |
|
|
61
55
|
| 群组资料变动之后回调 | `https://cloud.tencent.com/document/product/269/2930` |
|
|
62
56
|
| 撤回群消息之后回调 | `https://cloud.tencent.com/document/product/269/73141` |
|
|
63
57
|
| 直播群成员在线状态回调 | `https://cloud.tencent.com/document/product/269/76156` |
|
|
64
|
-
|
|
|
58
|
+
| 群消息发送异常回调 | `https://cloud.tencent.com/document/product/269/78619` |
|
|
65
59
|
| 创建话题之前回调 | `https://cloud.tencent.com/document/product/269/78206` |
|
|
66
60
|
| 创建话题之后回调 | `https://cloud.tencent.com/document/product/269/78207` |
|
|
67
61
|
| 解散话题之后回调 | `https://cloud.tencent.com/document/product/269/78208` |
|
|
@@ -77,7 +77,7 @@ Push Kit 支持多种场景化消息类型，其中部分场景化消息类型
|
|
|
77
77
|
登录 [AppGallery Connect](https://developer.huawei.com/consumer/cn/service/josp/agc/index.html)，选择**开发与服务**，单击**推送服务**，在**配置**页，单击申请自分类权益。按照提示申请并激活。详情介绍请参考 [推送场景化消息权益](https://developer.huawei.com/consumer/cn/doc/harmonyos-guides/push-apply-right)。
|
|
78
78
|
|
|
79
79
|
## 腾讯云 IM 控制台配置
|
|
80
|
-
1. 登录腾讯云 [即时通信 IM 控制台](https://console.qcloud.com/avc) ，在**推送服务 Push > 推送设置 >
|
|
80
|
+
1. 登录腾讯云 [即时通信 IM 控制台](https://console.qcloud.com/avc) ，在**推送服务 Push > 推送设置 > 厂商配置** 中添加 HarmonyOS 证书。
|
|
81
81
|
|
|
82
82
|
2. 选择上面步骤3 生成的证书凭证，上传至新添加的鸿蒙证书。
|
|
83
83
|
|
|
@@ -259,8 +259,8 @@ p8 证书是 APNs Auth Key，用于腾讯云服务端向 APNs 鉴权。创建 p8
|
|
|
259
259
|
7. 记录控制台生成的证书 ID。
|
|
260
260
|
|
|
261
261
|
> **注意：**
|
|
262
|
-
> 上传证书时，请确认 Bundle ID 与主 App 的 Bundle Identifier 一致。发布到 App Store 的 App 需要使用生产环境证书配置。
|
|
263
|
-
>
|
|
262
|
+
> - 上传证书时，请确认 Bundle ID 与主 App 的 Bundle Identifier 一致。发布到 App Store 的 App 需要使用生产环境证书配置。
|
|
263
|
+
> - 若对 IPA 做了重签（尤其企业证书重签），请确认重签用的企业证书 / Provisioning Profile 也在 Apple Developer 上开启了 Push Notifications，并确保重签后 IPA 内仍包含 aps-environment entitlement。
|
|
264
264
|
|
|
265
265
|
## 触达统计资源配置（可选）
|
|
266
266
|
|
|
@@ -77,7 +77,7 @@
|
|
|
77
77
|
请参见 [Apple Developer 平台 Bundle ID 配置指引](https://dev.weixin.qq.com/docs/miniapp/handbook/web/set-bundleid.html)，配置时请勾选以下能力：
|
|
78
78
|
- **Push Notification**
|
|
79
79
|
|
|
80
|
-
- **App Group (按需配置：字段配置可参见** [生成 App GroupID](https://cloud.tencent.com/document/product/269/100624#
|
|
80
|
+
- **App Group (按需配置：字段配置可参见** [生成 App GroupID](https://cloud.tencent.com/document/product/269/100624#778049b7-7ce0-4953-95fd-da523cca0bd4)**)**
|
|
81
81
|
|
|
82
82
|
- Donut 建议的权限：Access WiFi Information、Associated Domains、Hotspot、Wireless Accessory Configuration；如果使用苹果登录，还需开启 Sign In with Apple（更多其他权限开发者按需开启，并非越多越好哈）
|
|
83
83
|
|
|
@@ -87,7 +87,7 @@
|
|
|
87
87
|
|
|
88
88
|
4. 苹果推送服务 (APNs) 证书 ID 配置。
|
|
89
89
|
|
|
90
|
-
**当您需要接入 APNs 时开启厂商通道推送时，**`businessID` 为**必传项**，请先按照 [证书配置文档](https://cloud.tencent.com/document/product/269/100624#
|
|
90
|
+
**当您需要接入 APNs 时开启厂商通道推送时，**`businessID` 为**必传项**，请先按照 [证书配置文档](https://cloud.tencent.com/document/product/269/100624#e60424bc-0e30-43cc-9583-3ede9de495f5) 上传证书到推送控制台，之后控制台会为您分配此 ID。
|
|
91
91
|
|
|
92
92
|
5. 运行前准备。
|
|
93
93
|
|
|
@@ -10,7 +10,7 @@
|
|
|
10
10
|
|Push 服务开通状态|腾讯云控制台 > 即时通信 IM > **推送服务 Push** > **概览**|创建 Push 应用不等于已开通 Push 服务，请确认 Push 服务已开通。|
|
|
11
11
|
|TIMPush iOS `VERSION`|更新日志|`VERSION` 是 Podfile 中 TIMPush 依赖的版本号占位符，例如 `8.9.7537`、`8.8.7357`、`8.7.7201` 等，请以实际接入版本为准。|
|
|
12
12
|
|
|
13
|
-
本文示例中的 `VERSION`、`SDKAppID`、`
|
|
13
|
+
本文示例中的 `VERSION`、`SDKAppID`、`appKey`均为占位符，请勿在代码仓库中提交真实密钥。
|
|
14
14
|
|
|
15
15
|
## 操作步骤
|
|
16
16
|
|
|
@@ -54,9 +54,9 @@
|
|
|
54
54
|
|
|
55
55
|
【Android】
|
|
56
56
|
|
|
57
|
-
|
|
57
|
+
完成 厂商配置 后，下载并添加配置文件到工程。将下载的 `timpush-configs.json` 文件添加到项目的 `Assets/Plugins/Android` 目录下，如果该目录不存在，请手动创建。
|
|
58
58
|
|
|
59
|
-
### 步骤3
|
|
59
|
+
### 步骤3：客户端厂商配置
|
|
60
60
|
|
|
61
61
|
【iOS】
|
|
62
62
|
|
|
@@ -262,7 +262,7 @@ PushListener listener = new PushListener(onRecvPushMessage: (message) => {
|
|
|
262
262
|
PushManager.AddPushListener(listener);
|
|
263
263
|
```
|
|
264
264
|
|
|
265
|
-
### 步骤5
|
|
265
|
+
### 步骤5：注册推送插件
|
|
266
266
|
|
|
267
267
|
调用 `PushManager.RegisterPush` 方法成功后，就可以收到离线推送通知了。
|
|
268
268
|
|
|
@@ -278,7 +278,7 @@ PushManager.RegisterPush(sdkAppId: 您的sdkAppId, appKey: "客户端密钥", ne
|
|
|
278
278
|
}));
|
|
279
279
|
```
|
|
280
280
|
|
|
281
|
-
### 步骤6
|
|
281
|
+
### 步骤6：消息推送触达统计
|
|
282
282
|
|
|
283
283
|
如果你需要统计设备触达数据，请按照 华为/荣耀/vivo/魅族/iOS 完成配置。其余支持厂商不需要配置，FCM 暂不支持推送统计功能。
|
|
284
284
|
|
|
@@ -4,11 +4,11 @@
|
|
|
4
4
|
|
|
5
5
|
## 操作步骤
|
|
6
6
|
|
|
7
|
-
### 步骤1
|
|
7
|
+
### 步骤1：集成 TIMPush
|
|
8
8
|
|
|
9
9
|
各原生平台厂商配置后集成推送插件，下载 [TIMPush](https://github.com/TencentCloud/TIMSDK/tree/master/UE5/Push/pushdemo/Plugins/TIMPush) 并拷贝到项目的 `Plugins` 目录下，在项目主模块的 Build.cs 文件中，引入 TIMPush。
|
|
10
10
|
|
|
11
|
-
### 步骤2
|
|
11
|
+
### 步骤2：推送参数配置
|
|
12
12
|
|
|
13
13
|
【iOS】
|
|
14
14
|
|
|
@@ -20,21 +20,22 @@
|
|
|
20
20
|
|
|
21
21
|
3. 开启远程推送能力。完成证书 ID 配置之后，您需要开启应用的 Push Notifications 能力：
|
|
22
22
|
|
|
23
|
-
- 如果您的 UE 引擎是从源代码自行编译构建的，您可以通过 “项目设置 > iOS 中勾选 Enable Remote Notifications Support” 来开启对应能力；
|
|
23
|
+
- 如果您的 UE 引擎是从源代码自行编译构建的，您可以通过 “项目设置 > iOS 中勾选 Enable Remote Notifications Support” 来开启对应能力；
|
|
24
24
|
|
|
25
|
-
- 如果您的 UE 引擎是从 Epic Game 下载的，您可以通过打开 “`<proj_dir>/Config/DefaultEngine.ini`” ，在脚本的 `IOSRuntimeSettings` 中添加：
|
|
25
|
+
- 如果您的 UE 引擎是从 Epic Game 下载的，您可以通过打开 “`<proj_dir>/Config/DefaultEngine.ini`” ，在脚本的 `IOSRuntimeSettings` 中添加：
|
|
26
26
|
|
|
27
27
|
``` plaintext
|
|
28
28
|
// Some code
|
|
29
29
|
[/Script/IOSRuntimeSettings.IOSRuntimeSettings]
|
|
30
30
|
bEnableRemoteNotificationsSupport=True
|
|
31
31
|
```
|
|
32
|
-
- 或者，您也可以选择在项目根目录中使用 Xcode 打开 UE 生成的 YourProject.xcworkspace，在 Project > Target 中，点击 Signing & Capabilities 选项，点击左上角 Capability，搜索添加 Push Notifications 能力到您的项目中
|
|
32
|
+
- 或者，您也可以选择在项目根目录中使用 Xcode 打开 UE 生成的 YourProject.xcworkspace，在 Project > Target 中，点击 Signing & Capabilities 选项，点击左上角 Capability，搜索添加 Push Notifications 能力到您的项目中
|
|
33
33
|
|
|
34
34
|
【Android】
|
|
35
|
-
1. 完成厂商配置后，在 [腾讯云即时通信 IM 控制台](https://console.cloud.tencent.com/im/push-plugin-push-identifier) 下载并添加配置文件到工程。将下载的 `timpush-configs.json` 文件添加到 TIMPush 的 `Source/ThirdParty/TIMPushLibrary/Android/TIMPush/Assets` 目录下。
|
|
36
35
|
|
|
37
|
-
|
|
36
|
+
完成 厂商配置 后，在 [腾讯云即时通信 IM 控制台](https://console.cloud.tencent.com/im/push-plugin-push-identifier) 下载并添加配置文件到工程。将下载的 `timpush-configs.json` 文件添加到 TIMPush 的 `Source/ThirdParty/TIMPushLibrary/Android/TIMPush/Assets` 目录下。
|
|
37
|
+
|
|
38
|
+
### 步骤3：客户端厂商配置
|
|
38
39
|
|
|
39
40
|
【iOS】
|
|
40
41
|
|
|
@@ -89,9 +90,10 @@ APL 相关配置 TIMPush 已配置好，只需要替换成应用自己的配置
|
|
|
89
90
|
|
|
90
91
|
按照厂商方法，集成对应的 plugin 和 json 配置文件。
|
|
91
92
|
|
|
92
|
-
> **注意：**
|
|
93
|
-
>
|
|
94
|
-
>
|
|
93
|
+
> **注意：**
|
|
94
|
+
>
|
|
95
|
+
> 以下荣耀的适配仅 7.7.5283 及以上版本需要配置。
|
|
96
|
+
>
|
|
95
97
|
|
|
96
98
|
3.1 下载 json 配置文件，添加到插件 TIMPush 目录 `Source/ThirdParty/TIMPushLibrary/Android/TIMPush/` 目录下。
|
|
97
99
|
|
|
@@ -256,37 +258,37 @@ PushManager::GetInstance()->RegisterPush(您的 sdkAppId, "您的 appKey", callb
|
|
|
256
258
|
```
|
|
257
259
|
|
|
258
260
|
### 步骤6：消息推送触达统计
|
|
261
|
+
- 如果你需要统计 Android 设备触达数据，请按照 华为/荣耀/vivo/魅族 配置。
|
|
259
262
|
|
|
260
|
-
如果你需要统计
|
|
263
|
+
- 如果你需要统计 iOS 设备触达数据，
|
|
261
264
|
|
|
262
|
-
1. 在上文的推送参数配置章节中，将“YourGroupID”修改为自己的 App Group ID。
|
|
265
|
+
1. 在上文的推送参数配置章节中，将“YourGroupID”修改为自己的 App Group ID。
|
|
263
266
|
|
|
264
|
-
2. 参考 iOS 配置消息触达统计 完成 App Group ID、Notification Service Extension 和 mutable-content 配置。
|
|
267
|
+
2. 参考 iOS 配置消息触达统计 完成 App Group ID、Notification Service Extension 和 mutable-content 配置。
|
|
265
268
|
|
|
266
|
-
3. 将项目根目录的 Plugins-TIMPush-Source-ThirdParty-TIMPushLibrary-iOS 路径中的两个 framework 压缩包解压缩，并在 Xcode 项目中将内部的 .framework 文件夹添加到您的 pushservice target 之中。
|
|
269
|
+
3. 将项目根目录的 Plugins-TIMPush-Source-ThirdParty-TIMPushLibrary-iOS 路径中的两个 framework 压缩包解压缩，并在 Xcode 项目中将内部的 .framework 文件夹添加到您的 pushservice target 之中。
|
|
267
270
|
|
|
268
|
-
4. 在 Notification Service Extension 的 -didReceiveNotificationRequest:withContentHandler: 方法中调用推送抵达率统计函数:
|
|
271
|
+
4. 在 Notification Service Extension 的 -didReceiveNotificationRequest:withContentHandler: 方法中调用推送抵达率统计函数:
|
|
269
272
|
|
|
270
|
-
|
|
271
|
-
|
|
273
|
+
``` objectivec
|
|
274
|
+
@implementation NotificationService
|
|
272
275
|
|
|
273
|
-
|
|
274
|
-
|
|
275
|
-
|
|
276
|
-
|
|
277
|
-
|
|
278
|
-
|
|
279
|
-
|
|
280
|
-
|
|
281
|
-
|
|
282
|
-
|
|
283
|
-
|
|
284
|
-
|
|
285
|
-
|
|
286
|
-
|
|
287
|
-
@end
|
|
288
|
-
```
|
|
276
|
+
- (void)didReceiveNotificationRequest:(UNNotificationRequest *)request withContentHandler:(void (^)(UNNotificationContent * _Nonnull))contentHandler {
|
|
277
|
+
//appGroup 标识当前主 APP 和 Extension 之间共享的 APP Group，需要在主 APP 的 Capability 中配置 App Groups 能力。
|
|
278
|
+
//格式为group + [主bundleID]+ key
|
|
279
|
+
//如group.com.tencent.im.pushkey
|
|
280
|
+
NSString * appGroupID = kTIMPushAppGroupKey;
|
|
281
|
+
__weak typeof(self) weakSelf = self;
|
|
282
|
+
[TIMPushManager handleNotificationServiceRequest:request appGroupID:appGroupID callback:^(UNNotificationContent *content) {
|
|
283
|
+
weakSelf.bestAttemptContent = [content mutableCopy];
|
|
284
|
+
// Modify the notification content here...
|
|
285
|
+
// self.bestAttemptContent.title = [NSString stringWithFormat:@"%@ [modified]", self.bestAttemptContent.title];
|
|
286
|
+
weakSelf.contentHandler(weakSelf.bestAttemptContent);
|
|
287
|
+
}];
|
|
288
|
+
}
|
|
289
289
|
|
|
290
|
-
|
|
290
|
+
@end
|
|
291
|
+
```
|
|
292
|
+
- 其余支持厂商不需要配置，FCM 暂不支持推送统计功能。
|
|
291
293
|
|
|
292
|
-
|
|
294
|
+
如果接入完成却收不到推送，请使用 [排查工具](https://cloud.tencent.com/document/product/269/100629) 查看具体原因。
|
|
@@ -232,3 +232,4 @@ fun rejectCall(roomID: String, reason: CallRejectionReason = CallRejectionReason
|
|
|
232
232
|
| <strong>Store/Component</strong> | <strong>功能描述</strong> | <strong>API文档</strong> |
|
|
233
233
|
| --- | --- | --- |
|
|
234
234
|
| <strong>RoomStore</strong> | 房间全生命周期管理：创建并加入 / 加入 / 离开 / 结束房间 / 更新、获取房间信息 / 房间预约 / 呼叫房间外成员 / 监听房间内被动事件（例如房间解散，房间信息更新等）。 | <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-store/index.html">API 文档</a> |
|
|
235
|
+
|
|
@@ -675,3 +675,4 @@ private fun subscribeParticipantState() {
|
|
|
675
675
|
| <strong>Store/Component</strong> | <strong>功能描述</strong> | <strong>API 文档</strong> |
|
|
676
676
|
| --- | --- | --- |
|
|
677
677
|
| <strong>RoomParticipantStore</strong> | 房间内参与者管理：设置管理员 / 转移房主 / 获取参与者列表 / 移出房间 / 参与者设备控制（例如关闭、邀请打开摄像头、麦克风等）/ 申请打开设备（例如申请打开摄像头、麦克风等）。 | <a href="https://tencent-rtc.github.io/TUIKit_Android/-atomic-x%20-core%20-a-p-i/io.trtc.tuikit.atomicxcore.api.room/-room-participant-store/index.html">API 文档</a> |
|
|
678
|
+
|
|
@@ -226,3 +226,4 @@ Future<void> rejectCall(String roomID, {CallRejectionReason reason = CallRejecti
|
|
|
226
226
|
| <strong>Store/Component</strong> | <strong>功能描述</strong> | <strong>API 文档</strong> |
|
|
227
227
|
| --- | --- | --- |
|
|
228
228
|
| <strong>RoomStore</strong> | 房间全生命周期管理：创建并加入 / 加入 / 离开 / 结束房间 / 更新、获取房间信息 / 预定房间 / 呼叫房间外成员 / 监听房间内被动事件（例如房间解散，房间信息更新等）。 | <a href="https://tencent-rtc.github.io/TUIKit_Flutter/api_room_room_store/RoomStore-class.html">API 文档</a> |
|
|
229
|
+
|
|
@@ -793,3 +793,4 @@ Widget buildSpeakingUsersWidget() {
|
|
|
793
793
|
| <strong>Store</strong> | <strong>功能描述</strong> | <strong>API文档</strong> |
|
|
794
794
|
| --- | --- | --- |
|
|
795
795
|
| <strong>RoomParticipantStore</strong> | 房间内参与者管理：设置管理员 / 转移房主 / 获取参与者列表 / 移出房间 / 参与者设备控制（例如关闭、邀请打开摄像头、麦克风等）/ 申请打开设备（例如申请打开摄像头、麦克风等）。 | <a href="https://tencent-rtc.github.io/TUIKit_Flutter/api_room_room_participant_store/RoomParticipantStore-class.html">API 文档</a> |
|
|
796
|
+
|
|
@@ -224,3 +224,4 @@ func rejectCall(roomID: String, reason: CallRejectionReason = .rejected) {
|
|
|
224
224
|
| <strong>Store/Component</strong> | <strong>功能描述</strong> | <strong>API文档</strong> |
|
|
225
225
|
| --- | --- | --- |
|
|
226
226
|
| <strong>RoomStore</strong> | 房间全生命周期管理：创建并加入 / 加入 / 离开 / 结束房间 / 更新、获取房间信息 / 预定房间 / 呼叫房间外成员 / 监听房间内被动事件（例如房间解散，房间信息更新等）。 | <a href="https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/roomstore">API 文档</a> |
|
|
227
|
+
|
|
@@ -648,3 +648,4 @@ private func subscribeParticipantState() {
|
|
|
648
648
|
| <strong>Store/Component</strong> | <strong>功能描述</strong> | <strong>API 文档</strong> |
|
|
649
649
|
| --- | --- | --- |
|
|
650
650
|
| <strong>RoomParticipantStore</strong> | 房间内参与者管理：设置管理员 / 转移房主 / 获取参与者列表 / 移出房间 / 参与者设备控制（例如关闭、邀请打开摄像头、麦克风等）/ 申请打开设备（例如申请打开摄像头、麦克风等）。 | <a href="https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/roomparticipantstore">API 文档</a> |
|
|
651
|
+
|
package/server.js
CHANGED
|
@@ -28,9 +28,9 @@ You are using Tencent RTC MCP Server for SDK documentation retrieval.
|
|
|
28
28
|
|
|
29
29
|
Workflow:
|
|
30
30
|
1. Call search_trtc_knowledge. Reuse the same queryID for all retries/searches in this consultation.
|
|
31
|
-
2. Draft the
|
|
32
|
-
3. MUST call finalize_answer with the same prompt
|
|
33
|
-
4. Reply with
|
|
31
|
+
2. Draft the complete answer from fragments. Include References from meta.references/doc_urls when available.
|
|
32
|
+
3. MUST call finalize_answer with the same prompt, answer, and queryID before replying.
|
|
33
|
+
4. Reply with that answer + finalize_answer follow-up text.
|
|
34
34
|
5. After finalize_answer follow-up, check the next user reply before any normal response. If it means Yes/已解决/thanks/OK, MUST call submit_feedback(resolved="1") before replying. If it means No/未解决/still not working, MUST call submit_feedback(resolved="0") before replying. Never say feedback was submitted unless submit_feedback was called.
|
|
35
35
|
|
|
36
36
|
User-visible output rule (MUST):
|
|
@@ -41,7 +41,7 @@ User-visible output rule (MUST):
|
|
|
41
41
|
export function createServer() {
|
|
42
42
|
const server = new McpServer({
|
|
43
43
|
name: "Tencent RTC MCP Server",
|
|
44
|
-
version: "1.7.
|
|
44
|
+
version: "1.7.2",
|
|
45
45
|
}, {
|
|
46
46
|
instructions: SERVER_INSTRUCTIONS,
|
|
47
47
|
});
|