@tencent-rtc/mcp 1.6.4 → 1.6.6

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.
Files changed (251) hide show
  1. package/knowledge/chunker.js +83 -54
  2. package/knowledge/path-meta.js +179 -26
  3. package/knowledge/search/exact-lookup.js +168 -10
  4. package/knowledge/search/filter-pool.js +73 -19
  5. package/knowledge/search/product-scope-intent.js +2 -2
  6. package/knowledge/search/requires-framework.js +2 -2
  7. package/knowledge/search/search-knowledge.js +247 -61
  8. package/package.json +1 -1
  9. package/resource/index/manifest.json +1 -1
  10. package/resource/integration/callkit/preset/android/integration.md +2 -4
  11. package/resource/integration/callkit/preset/flutter/integration.md +4 -5
  12. package/resource/integration/callkit/preset/ios/integration.md +1 -4
  13. package/resource/integration/callkit/preset/react/integration.md +13 -20
  14. package/resource/integration/callkit/preset/vue/integration.md +14 -21
  15. package/resource/integration/chat/preset/android/integration.md +6 -9
  16. package/resource/integration/chat/preset/flutter/integration.md +9 -12
  17. package/resource/integration/chat/preset/ios/integration.md +2 -4
  18. package/resource/integration/chat/preset/react/integration.md +0 -10
  19. package/resource/integration/livekit/preset/live/android/live-audience-integration.md +129 -0
  20. package/resource/integration/livekit/preset/live/android/live-host-integration.md +219 -0
  21. package/resource/integration/livekit/preset/live/android/live-list-integration.md +261 -0
  22. package/resource/integration/livekit/preset/live/android/prepare-integration.md +254 -0
  23. package/resource/integration/livekit/preset/live/ios/live-audience-integration.md +202 -0
  24. package/resource/integration/livekit/preset/live/ios/live-host-integration.md +369 -0
  25. package/resource/integration/livekit/preset/live/ios/live-list-integration.md +229 -0
  26. package/resource/integration/livekit/preset/live/ios/prepare-integration.md +204 -0
  27. package/resource/integration/livekit/preset/live/vue/live-list-integration.md +0 -3
  28. package/resource/integration/livekit/preset/live/vue/live-player-desk-integration.md +0 -5
  29. package/resource/integration/livekit/preset/live/vue/live-player-h5-integration.md +0 -6
  30. package/resource/integration/livekit/preset/live/vue/live-pusher-integration.md +5 -10
  31. package/resource/integration/roomkit/preset/vue/integration.md +0 -4
  32. package/resource/knowledge/callkit/best-practice/web/callengine-invitation.md +80 -0
  33. package/resource/knowledge/callkit/best-practice/web/callengine-log-control.md +24 -0
  34. package/resource/knowledge/callkit/best-practice/web/callkit-call-vs-calls.md +116 -0
  35. package/resource/knowledge/callkit/core-sdk/android/answer-call.md +7 -8
  36. package/resource/knowledge/callkit/core-sdk/android/make-call.md +5 -7
  37. package/resource/knowledge/callkit/core-sdk/android/offline-push.md +3 -5
  38. package/resource/knowledge/callkit/core-sdk/flutter/answer-call.md +2 -6
  39. package/resource/knowledge/callkit/core-sdk/flutter/make-call.md +2 -6
  40. package/resource/knowledge/callkit/core-sdk/flutter/offline-push.md +4 -9
  41. package/resource/knowledge/callkit/core-sdk/ios/answer-call.md +1 -4
  42. package/resource/knowledge/callkit/core-sdk/ios/make-call.md +8 -11
  43. package/resource/knowledge/callkit/core-sdk/ios/offline-push.md +17 -23
  44. package/resource/knowledge/callkit/core-sdk/web/call-engine.md +33 -0
  45. package/resource/knowledge/callkit/core-sdk/web/call-event.md +327 -0
  46. package/resource/knowledge/callkit/core-sdk/web/callengine-api-overview.md +33 -0
  47. package/resource/knowledge/callkit/faq/android.md +0 -2
  48. package/resource/knowledge/callkit/faq/error-code.md +0 -2
  49. package/resource/knowledge/callkit/faq/flutter.md +2 -2
  50. package/resource/knowledge/callkit/faq/ios.md +3 -5
  51. package/resource/knowledge/callkit/faq/web.md +2 -3
  52. package/resource/knowledge/callkit/preset/android/api.md +2 -5
  53. package/resource/knowledge/callkit/preset/ios/api.md +0 -2
  54. package/resource/knowledge/callkit/preset/react/api.md +445 -0
  55. package/resource/knowledge/callkit/preset/react/uikit-api-reference.md +445 -0
  56. package/resource/knowledge/callkit/preset/vue/api.md +465 -0
  57. package/resource/knowledge/callkit/preset/vue/uikit-api-reference.md +465 -0
  58. package/resource/knowledge/chat/best-practice/web/image-message-url-handling.md +16 -0
  59. package/resource/knowledge/chat/preset/android/features/chat-setting.md +1 -1
  60. package/resource/knowledge/chat/preset/android/features/conversation-list.md +1 -1
  61. package/resource/knowledge/chat/preset/android/features/language.md +0 -1
  62. package/resource/knowledge/chat/preset/android/features/message-input.md +1 -1
  63. package/resource/knowledge/chat/preset/android/features/message-list.md +2 -3
  64. package/resource/knowledge/chat/preset/android/features/search.md +0 -1
  65. package/resource/knowledge/chat/preset/android/features/theme.md +1 -1
  66. package/resource/knowledge/chat/preset/android-view/integration.md +3 -11
  67. package/resource/knowledge/chat/preset/flutter/features/conversation-list.md +0 -1
  68. package/resource/knowledge/chat/preset/flutter/features/message-list.md +1 -2
  69. package/resource/knowledge/chat/preset/flutter/features/search.md +5 -6
  70. package/resource/knowledge/chat/preset/flutter/features/theme.md +2 -2
  71. package/resource/knowledge/chat/preset/ios/features/chat-setting.md +1 -1
  72. package/resource/knowledge/chat/preset/ios/features/conversation-list.md +1 -2
  73. package/resource/knowledge/chat/preset/ios/features/message-list.md +1 -2
  74. package/resource/knowledge/chat/preset/ios/features/search.md +0 -1
  75. package/resource/knowledge/chat/preset/ios-uikit/integration.md +13 -15
  76. package/resource/knowledge/chat/preset/react/features/conversation-list.md +5 -5
  77. package/resource/knowledge/chat/preset/react/features/message-input.md +2 -3
  78. package/resource/knowledge/chat/preset/react/features/search.md +0 -1
  79. package/resource/knowledge/chat/preset/react/features/theme.md +0 -1
  80. package/resource/knowledge/chat/urls/sdk/android.md +3 -3
  81. package/resource/knowledge/chat/urls/sdk/flutter.md +3 -3
  82. package/resource/knowledge/chat/urls/sdk/ios.md +3 -3
  83. package/resource/knowledge/chat/urls/sdk/web.md +3 -3
  84. package/resource/knowledge/livekit/core-sdk/api-reference/android/AudioEffectStore.md +7 -14
  85. package/resource/knowledge/livekit/core-sdk/api-reference/android/BarrageStore.md +5 -8
  86. package/resource/knowledge/livekit/core-sdk/api-reference/android/BattleStore.md +15 -18
  87. package/resource/knowledge/livekit/core-sdk/api-reference/android/CameraView.md +1 -2
  88. package/resource/knowledge/livekit/core-sdk/api-reference/android/CoGuestStore.md +15 -20
  89. package/resource/knowledge/livekit/core-sdk/api-reference/android/CoHostStore.md +10 -13
  90. package/resource/knowledge/livekit/core-sdk/api-reference/android/DeviceStore.md +2 -4
  91. package/resource/knowledge/livekit/core-sdk/api-reference/android/GiftStore.md +4 -6
  92. package/resource/knowledge/livekit/core-sdk/api-reference/android/LikeStore.md +2 -4
  93. package/resource/knowledge/livekit/core-sdk/api-reference/android/LiveAudienceStore.md +2 -4
  94. package/resource/knowledge/livekit/core-sdk/api-reference/android/LiveCoreView.md +1 -2
  95. package/resource/knowledge/livekit/core-sdk/api-reference/android/LiveSeatStore.md +8 -10
  96. package/resource/knowledge/livekit/core-sdk/api-reference/android/LoginStore.md +5 -7
  97. package/resource/knowledge/livekit/core-sdk/api-reference/flutter/AudioEffectStore.md +7 -14
  98. package/resource/knowledge/livekit/core-sdk/api-reference/flutter/BarrageStore.md +6 -9
  99. package/resource/knowledge/livekit/core-sdk/api-reference/flutter/BaseBeautyStore.md +1 -2
  100. package/resource/knowledge/livekit/core-sdk/api-reference/flutter/BattleStore.md +15 -18
  101. package/resource/knowledge/livekit/core-sdk/api-reference/flutter/CoGuestStore.md +15 -20
  102. package/resource/knowledge/livekit/core-sdk/api-reference/flutter/CoHostStore.md +10 -13
  103. package/resource/knowledge/livekit/core-sdk/api-reference/flutter/DeviceStore.md +2 -4
  104. package/resource/knowledge/livekit/core-sdk/api-reference/flutter/GiftStore.md +4 -6
  105. package/resource/knowledge/livekit/core-sdk/api-reference/flutter/LikeStore.md +2 -4
  106. package/resource/knowledge/livekit/core-sdk/api-reference/flutter/LiveAudienceStore.md +2 -4
  107. package/resource/knowledge/livekit/core-sdk/api-reference/flutter/LiveCoreView.md +1 -2
  108. package/resource/knowledge/livekit/core-sdk/api-reference/flutter/LiveSeatStore.md +8 -10
  109. package/resource/knowledge/livekit/core-sdk/api-reference/flutter/LoginStore.md +3 -5
  110. package/resource/knowledge/livekit/core-sdk/api-reference/ios/AudioEffectStore.md +7 -14
  111. package/resource/knowledge/livekit/core-sdk/api-reference/ios/BarrageStore.md +5 -8
  112. package/resource/knowledge/livekit/core-sdk/api-reference/ios/BaseBeautyStore.md +1 -2
  113. package/resource/knowledge/livekit/core-sdk/api-reference/ios/BattleStore.md +6 -9
  114. package/resource/knowledge/livekit/core-sdk/api-reference/ios/CoGuestStore.md +5 -10
  115. package/resource/knowledge/livekit/core-sdk/api-reference/ios/CoHostStore.md +3 -6
  116. package/resource/knowledge/livekit/core-sdk/api-reference/ios/DeviceStore.md +2 -4
  117. package/resource/knowledge/livekit/core-sdk/api-reference/ios/GiftStore.md +4 -6
  118. package/resource/knowledge/livekit/core-sdk/api-reference/ios/LikeStore.md +2 -4
  119. package/resource/knowledge/livekit/core-sdk/api-reference/ios/LiveAudienceStore.md +2 -4
  120. package/resource/knowledge/livekit/core-sdk/api-reference/ios/LiveCoreView.md +1 -2
  121. package/resource/knowledge/livekit/core-sdk/api-reference/ios/LiveSeatStore.md +4 -6
  122. package/resource/knowledge/livekit/core-sdk/api-reference/ios/LoginStore.md +3 -5
  123. package/resource/knowledge/livekit/core-sdk/api-reference/{web → vue}/index.md +24 -24
  124. package/resource/knowledge/livekit/core-sdk/{voice/android/voice-audio-effect.md → features/android/audio-effect.md} +1 -2
  125. package/resource/knowledge/livekit/core-sdk/{live/android/live-gift.md → features/android/gift.md} +2 -3
  126. package/resource/knowledge/livekit/core-sdk/{voice/android/voice-room-list.md → features/android/live-list.md} +2 -4
  127. package/resource/knowledge/livekit/core-sdk/{live/flutter/live-audio-effect.md → features/flutter/audio-effect.md} +0 -2
  128. package/resource/knowledge/livekit/core-sdk/{voice/flutter/voice-barrage.md → features/flutter/barrage.md} +2 -2
  129. package/resource/knowledge/livekit/core-sdk/{live/flutter/live-gift.md → features/flutter/gift.md} +2 -3
  130. package/resource/knowledge/livekit/core-sdk/{voice/flutter/voice-room-list.md → features/flutter/live-list.md} +1 -1
  131. package/resource/knowledge/livekit/core-sdk/{voice/ios/voice-audience-list.md → features/ios/audience-list.md} +1 -2
  132. package/resource/knowledge/livekit/core-sdk/{voice/ios/voice-audio-effect.md → features/ios/audio-effect.md} +1 -3
  133. package/resource/knowledge/livekit/core-sdk/{live/ios/live-base-beauty.md → features/ios/base-beauty.md} +2 -2
  134. package/resource/knowledge/livekit/core-sdk/{voice/ios/voice-gift.md → features/ios/gift.md} +2 -3
  135. package/resource/knowledge/livekit/core-sdk/{voice/ios/voice-room-list.md → features/ios/live-list.md} +2 -4
  136. package/resource/knowledge/livekit/core-sdk/live/android/{live-co-guest-interaction.md → co-guest-interaction.md} +0 -1
  137. package/resource/knowledge/livekit/core-sdk/live/android/{live-host-interaction.md → host-interaction.md} +5 -7
  138. package/resource/knowledge/livekit/core-sdk/live/android/{live-integration.md → integration.md} +3 -6
  139. package/resource/knowledge/livekit/core-sdk/live/flutter/{live-co-guest-interaction.md → co-guest-interaction.md} +1 -1
  140. package/resource/knowledge/livekit/core-sdk/live/flutter/{live-host-interaction.md → host-interaction.md} +0 -2
  141. package/resource/knowledge/livekit/core-sdk/live/flutter/{live-integration.md → integration.md} +1 -4
  142. package/resource/knowledge/livekit/core-sdk/live/ios/{live-co-guest-interaction.md → co-guest-interaction.md} +0 -1
  143. package/resource/knowledge/livekit/core-sdk/live/ios/{live-host-interaction.md → host-interaction.md} +2 -4
  144. package/resource/knowledge/livekit/core-sdk/live/ios/{live-integration.md → integration.md} +2 -5
  145. package/resource/knowledge/livekit/core-sdk/voice/android/{voice-host-interaction.md → host-interaction.md} +3 -5
  146. package/resource/knowledge/livekit/core-sdk/voice/android/{voice-integration.md → integration.md} +3 -6
  147. package/resource/knowledge/livekit/core-sdk/voice/flutter/{voice-co-guest-interaction.md → co-guest-interaction.md} +1 -2
  148. package/resource/knowledge/livekit/core-sdk/voice/flutter/{voice-integration.md → integration.md} +6 -9
  149. package/resource/knowledge/livekit/core-sdk/voice/ios/{voice-co-guest-interaction.md → co-guest-interaction.md} +2 -2
  150. package/resource/knowledge/livekit/core-sdk/voice/ios/{voice-host-interaction.md → host-interaction.md} +4 -6
  151. package/resource/knowledge/livekit/core-sdk/voice/ios/{voice-integration.md → integration.md} +1 -4
  152. package/resource/knowledge/livekit/preset/live/vue/features/barrage.md +0 -2
  153. package/resource/knowledge/push/api-reference/android.md +123 -0
  154. package/resource/knowledge/push/api-reference/flutter.md +176 -0
  155. package/resource/knowledge/push/api-reference/harmonyos.md +138 -0
  156. package/resource/knowledge/push/api-reference/ios.md +176 -0
  157. package/resource/knowledge/push/api-reference/react-native.md +147 -0
  158. package/resource/knowledge/push/api-reference/uni-app.md +147 -0
  159. package/resource/knowledge/push/api-reference/unity.md +119 -0
  160. package/resource/knowledge/push/api-reference/unreal-engine.md +123 -0
  161. package/resource/knowledge/push/config/android.md +4 -7
  162. package/resource/knowledge/push/config/harmonyos.md +0 -3
  163. package/resource/knowledge/push/config/ios.md +12 -20
  164. package/resource/knowledge/push/config/react-native.md +18 -26
  165. package/resource/knowledge/push/config/unity.md +20 -28
  166. package/resource/knowledge/push/config/unreal-engine.md +21 -29
  167. package/resource/knowledge/push/integration/android.md +6 -8
  168. package/resource/knowledge/push/integration/flutter.md +6 -9
  169. package/resource/knowledge/push/integration/harmonyos.md +1 -0
  170. package/resource/knowledge/push/integration/ios.md +7 -9
  171. package/resource/knowledge/push/integration/react-native.md +9 -13
  172. package/resource/knowledge/push/integration/uni-app.md +7 -7
  173. package/resource/knowledge/push/integration/unity.md +10 -13
  174. package/resource/knowledge/push/integration/unreal-engine.md +6 -9
  175. package/resource/knowledge/push/overview/prepare.md +2 -2
  176. package/resource/knowledge/roomkit/core-sdk/android/call-user-to-room.md +3 -3
  177. package/resource/knowledge/roomkit/core-sdk/android/capability-matrix.md +46 -0
  178. package/resource/knowledge/roomkit/core-sdk/android/room-participant-state.md +1 -1
  179. package/resource/knowledge/roomkit/core-sdk/android/room-state.md +2 -2
  180. package/resource/knowledge/roomkit/core-sdk/android/schedule-room.md +6 -6
  181. package/resource/knowledge/roomkit/core-sdk/android/unsupported-features.md +79 -0
  182. package/resource/knowledge/roomkit/core-sdk/flutter/capability-matrix.md +46 -0
  183. package/resource/knowledge/roomkit/core-sdk/flutter/room-participant-state.md +1 -1
  184. package/resource/knowledge/roomkit/core-sdk/flutter/unsupported-features.md +79 -0
  185. package/resource/knowledge/roomkit/core-sdk/ios/capability-matrix.md +46 -0
  186. package/resource/knowledge/roomkit/core-sdk/ios/room-participant-state.md +1 -1
  187. package/resource/knowledge/roomkit/core-sdk/ios/unsupported-features.md +79 -0
  188. package/resource/knowledge/roomkit/preset/android/integration.md +5 -7
  189. package/resource/knowledge/roomkit/preset/flutter/integration.md +2 -7
  190. package/resource/knowledge/roomkit/preset/ios/integration.md +3 -9
  191. package/resource/knowledge/roomkit/preset/react/integration.md +12 -16
  192. package/resource/knowledge/trtc/android/TRTCCloud.md +154 -238
  193. package/resource/knowledge/trtc/android/TRTCCloudDef.md +133 -134
  194. package/resource/knowledge/trtc/android/TRTCCloudListener.md +86 -120
  195. package/resource/knowledge/trtc/android/TRTCStatistics.md +10 -10
  196. package/resource/knowledge/trtc/android/TXAudioEffectManager.md +10 -30
  197. package/resource/knowledge/trtc/android/TXBeautyManager.md +25 -25
  198. package/resource/knowledge/trtc/android/TXDeviceManager.md +2 -2
  199. package/resource/knowledge/trtc/android/TXLiteAVCode.md +12 -12
  200. package/resource/knowledge/trtc/c++/ITRTCCloud.md +166 -261
  201. package/resource/knowledge/trtc/c++/ITRTCStatistics.md +12 -12
  202. package/resource/knowledge/trtc/c++/ITXAudioEffectManager.md +10 -30
  203. package/resource/knowledge/trtc/c++/ITXDeviceManager.md +9 -11
  204. package/resource/knowledge/trtc/c++/TRTCCloudCallback.md +96 -130
  205. package/resource/knowledge/trtc/c++/TRTCTypeDef.md +122 -123
  206. package/resource/knowledge/trtc/c++/TXLiteAVCode.md +12 -12
  207. package/resource/knowledge/trtc/ios/TRTCCloud.md +168 -255
  208. package/resource/knowledge/trtc/ios/TRTCCloudDef.md +124 -125
  209. package/resource/knowledge/trtc/ios/TRTCCloudDelegate.md +89 -124
  210. package/resource/knowledge/trtc/ios/TRTCStatistics.md +10 -10
  211. package/resource/knowledge/trtc/ios/TXAudioEffectManager.md +9 -28
  212. package/resource/knowledge/trtc/ios/TXBeautyManager.md +25 -25
  213. package/resource/knowledge/trtc/ios/TXDeviceManager.md +9 -11
  214. package/resource/knowledge/trtc/ios/TXLiteAVCode.md +12 -12
  215. package/server.js +21 -21
  216. package/tools/common/finalize_answer.js +1 -1
  217. package/tools/common/present_framework_choice.js +2 -2
  218. package/tools/common/search_trtc_knowledge.js +3 -3
  219. package/tools/common/submit_feedback.js +1 -1
  220. package/tools/definitions/get_native_live_uikit_integration_def.js +61 -0
  221. package/tools/definitions/get_native_livekit_core_integration_def.js +3 -3
  222. package/tools/definitions/present_framework_choice_def.js +2 -2
  223. package/tools/definitions/search_trtc_knowledge_def.js +5 -5
  224. package/tools/index.js +2 -0
  225. package/tools/live/get_native_live_uikit_integration.js +69 -0
  226. package/tools/live/get_native_livekit_core_integration.js +6 -6
  227. package/utils/report-cls-client.js +1 -1
  228. package/utils/report-es-client.js +1 -1
  229. package/resource/knowledge/callkit/preset/web/api.md +0 -83
  230. package/resource/knowledge/livekit/core-sdk/live/android/live-audio-effect.md +0 -226
  231. package/resource/knowledge/livekit/core-sdk/live/android/live-live-list.md +0 -438
  232. package/resource/knowledge/livekit/core-sdk/live/flutter/live-barrage.md +0 -490
  233. package/resource/knowledge/livekit/core-sdk/live/flutter/live-live-list.md +0 -726
  234. package/resource/knowledge/livekit/core-sdk/live/ios/live-audience-list.md +0 -264
  235. package/resource/knowledge/livekit/core-sdk/live/ios/live-audio-effect.md +0 -216
  236. package/resource/knowledge/livekit/core-sdk/live/ios/live-gift.md +0 -407
  237. package/resource/knowledge/livekit/core-sdk/live/ios/live-live-list.md +0 -349
  238. package/resource/knowledge/livekit/core-sdk/voice/android/voice-audience-list.md +0 -269
  239. package/resource/knowledge/livekit/core-sdk/voice/android/voice-barrage.md +0 -456
  240. package/resource/knowledge/livekit/core-sdk/voice/android/voice-gift.md +0 -455
  241. package/resource/knowledge/livekit/core-sdk/voice/flutter/voice-audience-list.md +0 -260
  242. package/resource/knowledge/livekit/core-sdk/voice/flutter/voice-audio-effect.md +0 -598
  243. package/resource/knowledge/livekit/core-sdk/voice/flutter/voice-gift.md +0 -424
  244. package/resource/knowledge/livekit/core-sdk/voice/ios/voice-barrage.md +0 -408
  245. /package/resource/knowledge/livekit/core-sdk/{live/android/live-audience-list.md → features/android/audience-list.md} +0 -0
  246. /package/resource/knowledge/livekit/core-sdk/{live/android/live-barrage.md → features/android/barrage.md} +0 -0
  247. /package/resource/knowledge/livekit/core-sdk/{live/android/live-base-beauty.md → features/android/base-beauty.md} +0 -0
  248. /package/resource/knowledge/livekit/core-sdk/{live/flutter/live-audience-list.md → features/flutter/audience-list.md} +0 -0
  249. /package/resource/knowledge/livekit/core-sdk/{live/flutter/live-base-beauty.md → features/flutter/base-beauty.md} +0 -0
  250. /package/resource/knowledge/livekit/core-sdk/{live/ios/live-barrage.md → features/ios/barrage.md} +0 -0
  251. /package/resource/knowledge/livekit/core-sdk/voice/android/{voice-co-guest-interaction.md → co-guest-interaction.md} +0 -0
@@ -54,16 +54,15 @@ dependencies {
54
54
 
55
55
  > **Note:**
56
56
  >
57
-
58
57
  > The TUICallKit project internally depends on `TRTC SDK`,`IM SDK`,`tuicallengine` and public library `tuicore` by default. Developers do not need to configure them separately. If needed, just modify the version number in `tuicallkit-kt/build.gradle` file to upgrade.
59
58
  >
60
59
 
61
- 3. `proguard-rules.pro`**Configuration**:Since the SDK internally uses Java reflection, certain classes must be added to the non-obfuscation list (ProGuard exclusion list). Please add the following configuration to the end of the `proguard-rules.pro` file:
60
+ 3. `proguard-rules.pro` **Configuration**:Since the SDK internally uses Java reflection, certain classes must be added to the non-obfuscation list (ProGuard exclusion list). Please add the following configuration to the end of the `proguard-rules.pro` file:
62
61
 
63
62
  ``` java
64
63
  -keep class com.tencent.** { *; }
65
64
  ```
66
- 4. `AndroidManifest.xml`**Configuration**:In the AndroidManifest.xml file within the app directory, add `tools:replace="android:allowBackup"` within the <application> node to overwrite the component's default settings and apply your own configuration.
65
+ 4. `AndroidManifest.xml` **Configuration**:In the AndroidManifest.xml file within the app directory, add `tools:replace="android:allowBackup"` within the <application> node to overwrite the component's default settings and apply your own configuration.
67
66
 
68
67
  ``` java
69
68
  // app/src/main/AndroidManifest.xml
@@ -358,7 +357,6 @@ public class MainActivity extends BaseActivity {
358
357
 
359
358
  > **Note:**
360
359
  >
361
-
362
360
  > If you need to set up other languages, please contact us at **info_rtc@tencent.com** for assistance.
363
361
  >
364
362
 
@@ -84,12 +84,12 @@ Grant Camera and Microphone Permissions:Because TUICallKit requires audio and vi
84
84
 
85
85
  > **Note:**
86
86
  >
87
-
88
87
  > Since tencent_rtc_sdk calls interfaces through Flutter FFI, Xcode's symbol stripping optimization during iOS Release builds may mistakenly remove TRTC's C symbols, causing a `symbol not found` error. The solution is as follows:
89
88
  >
90
89
  > 1. In the project's Build Settings, find `deployment postprocessing` and set it to **Yes.**
91
-
90
+ >
92
91
  > 2. In the project's Build Settings, find `strip style` and set the Release value to **Non-Global Symbols.**
92
+ >
93
93
 
94
94
  - Flutter Project Configuration:
95
95
 
@@ -293,20 +293,19 @@ void join() {
293
293
  |callId|String|The unique ID for this call.|
294
294
 
295
295
  ### Language Settings
296
- - **Supported Languages: **We currently support Simplified Chinese, English, and Japanese. The default language is English.
296
+ - **Supported Languages:** We currently support Simplified Chinese, English, and Japanese. The default language is English.
297
297
 
298
298
  - **Switching Languages:** TUICallKit does not provide a separate language switching API. Its interface language will automatically align with the language setting used by the application's current root component (such as MaterialApp or CupertinoApp).
299
299
 
300
300
  > **Note:**
301
301
  >
302
-
303
302
  > If you need to set up other languages, please contact us at **info_rtc@tencent.com** for assistance.
304
303
  >
305
304
 
306
305
  ### Ringtone Setting
307
306
 
308
307
  You can set the default ringtone, and incoming call silent mode in the following ways:
309
- - **Setting Default Ringtone: **If you include TUICallKit component via source code, you can replace the resource file([ringtone when initiating a call](https://github.com/Tencent-RTC/TUICallKit/blob/main/Flutter/assets/audios/phone_dialing.mp3)、[ringtone when initiating a call](https://github.com/Tencent-RTC/TUICallKit/blob/main/Flutter/assets/audios/phone_ringing.mp3))to set a custom default ringtone.
308
+ - **Setting Default Ringtone:** If you include TUICallKit component via source code, you can replace the resource file([ringtone when initiating a call](https://github.com/Tencent-RTC/TUICallKit/blob/main/Flutter/assets/audios/phone_dialing.mp3)、[ringtone when initiating a call](https://github.com/Tencent-RTC/TUICallKit/blob/main/Flutter/assets/audios/phone_ringing.mp3))to set a custom default ringtone.
310
309
 
311
310
  - **Incoming call silent mode:** You can set mute mode through `enableMuteMode`.
312
311
 
@@ -57,7 +57,6 @@ pod init
57
57
 
58
58
  > **Tips:**
59
59
  >
60
-
61
60
  > After the installation is complete, open the project using the `YourProjectName.xcworkspace` file.
62
61
  >
63
62
 
@@ -168,7 +167,6 @@ The caller initiates a call by invoking the `calls` function and specifying the
168
167
 
169
168
  > **Note:**
170
169
  >
171
-
172
170
  > The `calls` interface cannot be written in the `viewDidLoad` method; it should be called in the button's click event or other user interaction response methods.
173
171
  >
174
172
 
@@ -328,7 +326,6 @@ func setLanguage() {
328
326
 
329
327
  > **Note:**
330
328
  >
331
-
332
329
  > If you need to set up other languages, please contact us at **info_rtc@tencent.com** for assistance.
333
330
  >
334
331
 
@@ -373,7 +370,7 @@ TUICallKit.createInstance().enableMuteMode(enable: true)
373
370
 
374
371
  **Details:** When turned on, incoming call requests will not trigger ring.
375
372
 
376
- - **Custom offline push ringtone: **By default, the system determines the ringtone for offline push notifications. To use a custom sound, follow the instructions below:
373
+ - **Custom offline push ringtone:** By default, the system determines the ringtone for offline push notifications. To use a custom sound, follow the instructions below:
377
374
 
378
375
  1. **Prepare your file:** Name your custom ringtone file `phone_ringing.mp3`.
379
376
 
@@ -61,7 +61,7 @@ You can choose to import the sample code in the `/src/App.tsx` file.
61
61
  </>
62
62
  );
63
63
  ```
64
- 3. using the [TUICallKitAPI.init](https://trtc.io/document/51015#call#init) API to log in to the component, you need to `fill in``SDKAppID, SDKSecretKey `as two parameters in the code.
64
+ 3. using the [TUICallKitAPI.init](https://trtc.io/document/51015#call#init) API to log in to the component, you need to `fill in` `SDKAppID, SDKSecretKey` as two parameters in the code.
65
65
 
66
66
  ``` javascript
67
67
  const SDKAppID = 0; // TODO: Replace with your SDKAppID (Notice: SDKAppID is of type number)
@@ -87,15 +87,15 @@ You can choose to import the sample code in the `/src/App.tsx` file.
87
87
  ```
88
88
  |**Parameter**|**Type**|**Note**|
89
89
  |---------|---------|---------|
90
- |userID|String|**Unique identifier of the user, **`defined by you`**, **it is allowed to contain only upper and lower case letters (a-z, A-Z), numbers (0-9), underscores, and hyphens.|
90
+ |userID|String|**Unique identifier of the user,** `defined by you`**,** it is allowed to contain only upper and lower case letters (a-z, A-Z), numbers (0-9), underscores, and hyphens.|
91
91
  |SDKAppID|Number|The unique identifier for the audio and video application created in the [Tencent RTC Console](https://console.trtc.io/).|
92
92
  |SDKSecretKey|String|The SDKSecretKey of the audio and video application created in the [Tencent RTC Console](https://console.trtc.io/).|
93
93
  |userSig|String|A security protection signature used for user log in authentication to confirm the user's identity and prevent malicious attackers from stealing your cloud service usage rights.|
94
94
 
95
95
  > **Explanation of userSig:**
96
96
  >
97
- > - **Development environment:** If you are running a demo locally and developing debugging, you can use the `genTestUserSig` (Refer to Step 3.2) function in the debug file to generate a `userSig`. In this method, SDKSecretKey is vulnerable to decompilation and reverse engineering. Once your key is leaked, attackers can steal your Tencent Cloud traffic.
98
- > - **Production environment: **If your project is going live, please use the [Server-side Generation of UserSig](https://trtc.io/document/35166) method.
97
+ > - **Development environment:** If you are running a demo locally and developing debugging, you can use the `genTestUserSig` (Refer to Step 3.2) function in the debug file to generate a `userSig`. In this method, SDKSecretKey is vulnerable to decompilation and reverse engineering. Once your key is leaked, attackers can steal your Tencent Cloud traffic.
98
+ > - **Production environment:** If your project is going live, please use the [Server-side Generation of UserSig](https://trtc.io/document/35166) method.
99
99
 
100
100
  ### Set Nickname and Avatar (Optional)
101
101
 
@@ -113,7 +113,6 @@ try {
113
113
 
114
114
  > **Note:**
115
115
  >
116
-
117
116
  > Due to user privacy restrictions, for calls between non-friends, there might be a delay in updating the callee's nickname and avatar. This will be updated smoothly after the first successful call.
118
117
  >
119
118
 
@@ -136,13 +135,12 @@ The caller can initiate a voice or video call by calling the [calls](https://www
136
135
 
137
136
  > **Warning:**
138
137
  >
139
-
140
- > **For local environment, please access under localhost protocol. For public network experience, please access under HTTPS protocol. For details, see **[Description of Network Access Protocol](https://web.sdk.qcloud.com/trtc/webrtc/doc/en/tutorial-05-info-browser.html#h2-3)**.**
138
+ > **For local environment, please access under localhost protocol. For public network experience, please access under HTTPS protocol. For details, see** [Description of Network Access Protocol](https://web.sdk.qcloud.com/trtc/webrtc/doc/en/tutorial-05-info-browser.html#h2-3)**.**
141
139
  >
142
140
 
143
- 3. Open two browser pages,** enter different userID (defined by you) **click `step1. init` to login (caller and callee).
141
+ 3. Open two browser pages, **enter different userID (defined by you)** click `step1. init` to login (caller and callee).
144
142
 
145
- 4. **After both userID init to successfully**, click on` step2. call`to make a call. If you have a call problem, refer to [FAQs](https://trtc.io/document/51024).
143
+ 4. **After both userID init to successfully**, click on `step2. call`to make a call. If you have a call problem, refer to [FAQs](https://trtc.io/document/51024).
146
144
 
147
145
  ### Answering a Call
148
146
 
@@ -162,7 +160,7 @@ TUICallKitAPI.enableFloatWindow(true)
162
160
  ### Setting incoming call ringtone
163
161
 
164
162
  You can configure the default ringtone and mute mode for incoming calls using the following methods:
165
- - **Set the default ringtone: **Use the setCallingBell interface to set the ringtone that the callee receives.
163
+ - **Set the default ringtone:** Use the setCallingBell interface to set the ringtone that the callee receives.
166
164
 
167
165
  - Only local MP3 format file addresses can be used, ensuring that the file is accessible.
168
166
 
@@ -197,7 +195,6 @@ To replace an icon, source code import is required first. Copy the component to
197
195
 
198
196
  > **Note:**
199
197
  >
200
-
201
198
  > The Interface Replacing icons Plan is suitable for `Vue3 + TypeScript` and `@trtc/calls-uikit-react` version number is 3.2.2 or later projects. If you are using other languages or technology stacks, please use the Custom UI Implementation.
202
199
  >
203
200
 
@@ -208,7 +205,7 @@ To replace an icon, source code import is required first. Copy the component to
208
205
  npm install @trtc/calls-uikit-react
209
206
  ```
210
207
 
211
- 2. **Copy the source code into your own project, taking copying into the **`src/components/`** directory as an example:**
208
+ 2. **Copy the source code into your own project, taking copying into the** `src/components/` **directory as an example:**
212
209
 
213
210
  【macOS + React】
214
211
  ``` bash
@@ -227,9 +224,7 @@ xcopy .\node_modules\@trtc\calls-uikit-react .\src\components\TUICallKit /i /e
227
224
  ``` javascript
228
225
  import { TUICallKit, TUICallKitAPI } from "./components/TUICallKit/src/index";
229
226
  ```
230
- 4.
231
-
232
- **Solve Errors That May Be Caused by Copying Source Code**
227
+ 4. **Solve Errors That May Be Caused by Copying Source Code**
233
228
 
234
229
  If you encounter an error while using the TUICallKit component, please don't worry. In most cases, this is due to inconsistencies between ESLint and TSConfig configurations. You can consult the documentation and configure correctly as required. If you need help, please feel free to contact us, and we will ensure that you can successfully use this component. Here are some common issues:
235
230
 
@@ -242,7 +237,7 @@ src/components/TUICallKit
242
237
  ```
243
238
 
244
239
  【TypeScript Error】
245
- 5. If you encounter the 'Cannot find module '../package.json'' error, it's because TUICallKit references a JSON file. You can add the related configuration in tsconfig.json, example:
240
+ 1. If you encounter the 'Cannot find module '../package.json'' error, it's because TUICallKit references a JSON file. You can add the related configuration in tsconfig.json, example:
246
241
 
247
242
  ``` json
248
243
  {
@@ -253,7 +248,7 @@ src/components/TUICallKit
253
248
  ```
254
249
 
255
250
  For other TSConfig issues, please refer to [TSConfig Reference](https://www.typescriptlang.org/tsconfig).
256
- 6. If you encounter the 'Uncaught SyntaxError: Invalid or unexpected token' error, it's because TUICallKit uses decorators. You can add the related configuration in tsconfig.json, example:
251
+ 2. If you encounter the 'Uncaught SyntaxError: Invalid or unexpected token' error, it's because TUICallKit uses decorators. You can add the related configuration in tsconfig.json, example:
257
252
 
258
253
  ``` json
259
254
  {
@@ -263,11 +258,10 @@ For other TSConfig issues, please refer to [TSConfig Reference](https://www.type
263
258
  }
264
259
  ```
265
260
 
266
- 7. **Modify the icon components in the TUICallKit/Components/assets folder**
261
+ 5. **Modify the icon components in the TUICallKit/Components/assets folder**
267
262
 
268
263
  > **Note:**
269
264
  >
270
-
271
265
  > To ensure the icon color and style remain consistent throughout the application, please keep the icon file name unchanged when replacing.
272
266
  >
273
267
 
@@ -324,7 +318,6 @@ TUICallKitAPI.setRemoteViewBackgroundImage('remoteUserId', 'http://xxx.png');
324
318
 
325
319
  > **Note:**
326
320
  >
327
-
328
321
  > **Only available for 1V1 video calls.**
329
322
  >
330
323
 
@@ -49,7 +49,7 @@ You can choose to import the sample code in the `src/App.vue` file.The example c
49
49
  <TUICallKit style="width: 650px; height: 500px " />
50
50
  </template>
51
51
  ```
52
- 2. Using the [TUICallKitAPI.init](https://trtc.io/document/51015#init) API to log in to the component, you need to `fill in``SDKAppID, SDKSecretKey`** as two parameters in the code.**
52
+ 2. Using the [TUICallKitAPI.init](https://trtc.io/document/51015#init) API to log in to the component, you need to `fill in` `SDKAppID, SDKSecretKey` **as two parameters in the code.**
53
53
 
54
54
  ``` javascript
55
55
  <script setup> // lang='ts'
@@ -81,15 +81,15 @@ You can choose to import the sample code in the `src/App.vue` file.The example c
81
81
  ```
82
82
  |**Parameter**|**Type**|**Note**|
83
83
  |---------|---------|---------|
84
- |userID|String|**Unique identifier of the user, **`defined by you`**, **it is allowed to contain only upper and lower case letters (a-z, A-Z), numbers (0-9), underscores, and hyphens.|
84
+ |userID|String|**Unique identifier of the user,** `defined by you`**,** it is allowed to contain only upper and lower case letters (a-z, A-Z), numbers (0-9), underscores, and hyphens.|
85
85
  |SDKAppID|Number|The unique identifier for the audio and video application created in the [Tencent RTC Console](https://console.trtc.io/).|
86
86
  |SDKSecretKey|String|The SDKSecretKey of the audio and video application created in the [Tencent RTC Console](https://console.trtc.io/).|
87
87
  |userSig|String|A security protection signature used for user log in authentication to confirm the user's identity and prevent malicious attackers from stealing your cloud service usage rights.|
88
88
 
89
89
  > **Explanation of userSig:**
90
90
  >
91
- > - **Development environment:** If you are running a demo locally and developing debugging, you can use the `genTestUserSig` (Refer to Step 3.2) function in the debug file to generate a `userSig`. In this method, SDKSecretKey is vulnerable to decompilation and reverse engineering. Once your key is leaked, attackers can steal your Tencent Cloud traffic.
92
- > - **Production environment: **If your project is going live, please use the [Server-side Generation of UserSig](https://trtc.io/document/35166) method.
91
+ > - **Development environment:** If you are running a demo locally and developing debugging, you can use the `genTestUserSig` (Refer to Step 3.2) function in the debug file to generate a `userSig`. In this method, SDKSecretKey is vulnerable to decompilation and reverse engineering. Once your key is leaked, attackers can steal your Tencent Cloud traffic.
92
+ > - **Production environment:** If your project is going live, please use the [Server-side Generation of UserSig](https://trtc.io/document/35166) method.
93
93
 
94
94
  ### Set Nickname and Avatar (Optional)
95
95
 
@@ -107,7 +107,6 @@ try {
107
107
 
108
108
  > **Note:**
109
109
  >
110
-
111
110
  > Due to user privacy restrictions, for calls between non-friends, there might be a delay in updating the callee's nickname and avatar. This will be updated smoothly after the first successful call.
112
111
  >
113
112
 
@@ -128,15 +127,14 @@ The caller can initiate a voice or video call by calling the [calls](https://www
128
127
  ```
129
128
  2. Run the project.
130
129
 
131
- > **Warning: **
130
+ > **Warning:**
132
131
  >
133
-
134
- > **For local environment, please access under **`localhost protocol`**. For public network experience, please access under HTTPS protocol. For details, see **[Description of Network Access Protocol](https://web.sdk.qcloud.com/trtc/webrtc/doc/en/tutorial-05-info-browser.html#h2-3)**.**
132
+ > **For local environment, please access under** `localhost protocol`**. For public network experience, please access under HTTPS protocol. For details, see** [Description of Network Access Protocol](https://web.sdk.qcloud.com/trtc/webrtc/doc/en/tutorial-05-info-browser.html#h2-3)**.**
135
133
  >
136
134
 
137
- 3. Open two browser pages,** enter different userID(defined by you) **click `step1. init` to login (caller and callee).
135
+ 3. Open two browser pages, **enter different userID(defined by you)** click `step1. init` to login (caller and callee).
138
136
 
139
- 4. **After both userID init to successfully**, click on` step2. call`to make a call. If you have a call problem, refer to [FAQs](https://trtc.io/document/51024).
137
+ 4. **After both userID init to successfully**, click on `step2. call`to make a call. If you have a call problem, refer to [FAQs](https://trtc.io/document/51024).
140
138
 
141
139
  ### Answering a Call
142
140
 
@@ -156,7 +154,7 @@ TUICallKitAPI.enableFloatWindow(true)
156
154
  ### Setting incoming call ringtone
157
155
 
158
156
  You can configure the default ringtone and mute mode for incoming calls using the following methods:
159
- - **Set the default ringtone: **Use the setCallingBell interface to set the ringtone that the callee receives.
157
+ - **Set the default ringtone:** Use the setCallingBell interface to set the ringtone that the callee receives.
160
158
 
161
159
  - Only local MP3 format file addresses can be used, ensuring that the file is accessible.
162
160
 
@@ -191,7 +189,6 @@ To replace an icon, source code import is required first. Copy the component to
191
189
 
192
190
  > **Note:**
193
191
  >
194
-
195
192
  > The Interface Replacing icons Plan is suitable for `Vue3 + TypeScript` and `@trtc/calls-uikit-vue` version number is 3.2.2 or later projects. If you are using other languages or technology stacks, please use the Custom UI Implementation.
196
193
  >
197
194
 
@@ -202,7 +199,7 @@ To replace an icon, source code import is required first. Copy the component to
202
199
  npm install @trtc/calls-uikit-vue
203
200
  ```
204
201
 
205
- 2. **Copy the source code into your own project, taking copying into the **`src/components/`** directory as an example:**
202
+ 2. **Copy the source code into your own project, taking copying into the** `src/components/` **directory as an example:**
206
203
 
207
204
  【macOS + Vue3】
208
205
  ``` bash
@@ -221,9 +218,7 @@ xcopy .\node_modules\@trtc\calls-uikit-vue .\src\components\TUICallKit /i /e
221
218
  ``` javascript
222
219
  import { TUICallKit, TUICallKitAPI } from "./components/TUICallKit/src/index";
223
220
  ```
224
- 4.
225
-
226
- **Solve Errors That May Be Caused by Copying Source Code**
221
+ 4. **Solve Errors That May Be Caused by Copying Source Code**
227
222
 
228
223
  If you encounter an error while using the TUICallKit component, please don't worry. In most cases, this is due to inconsistencies between ESLint and TSConfig configurations. You can consult the documentation and configure correctly as required. If you need help, please feel free to contact us, and we will ensure that you can successfully use this component. Here are some common issues:
229
224
 
@@ -236,7 +231,7 @@ src/components/TUICallKit
236
231
  ```
237
232
 
238
233
  【TypeScript Error】
239
- 5. If you encounter the 'Cannot find module '../package.json'' error, it's because TUICallKit references a JSON file. You can add the related configuration in tsconfig.json, example:
234
+ 1. If you encounter the 'Cannot find module '../package.json'' error, it's because TUICallKit references a JSON file. You can add the related configuration in tsconfig.json, example:
240
235
 
241
236
  ``` json
242
237
  {
@@ -247,7 +242,7 @@ src/components/TUICallKit
247
242
  ```
248
243
 
249
244
  For other TSConfig issues, please refer to [TSConfig Reference](https://www.typescriptlang.org/tsconfig).
250
- 6. If you encounter the 'Uncaught SyntaxError: Invalid or unexpected token' error, it's because TUICallKit uses decorators. You can add the related configuration in tsconfig.json, example:
245
+ 2. If you encounter the 'Uncaught SyntaxError: Invalid or unexpected token' error, it's because TUICallKit uses decorators. You can add the related configuration in tsconfig.json, example:
251
246
 
252
247
  ``` json
253
248
  {
@@ -257,11 +252,10 @@ For other TSConfig issues, please refer to [TSConfig Reference](https://www.type
257
252
  }
258
253
  ```
259
254
 
260
- 7. **Modify the icon components in the TUICallKit/Components/assets folder**
255
+ 5. **Modify the icon components in the TUICallKit/Components/assets folder**
261
256
 
262
257
  > **Note:**
263
258
  >
264
-
265
259
  > To ensure the icon color and style remain consistent throughout the application, please keep the icon file name unchanged when replacing.
266
260
  >
267
261
 
@@ -318,7 +312,6 @@ TUICallKitAPI.setRemoteViewBackgroundImage('remoteUserId', 'http://xxx.png');
318
312
 
319
313
  > **Note:**
320
314
  >
321
-
322
315
  > **Only available for 1V1 video calls.**
323
316
  >
324
317
 
@@ -30,11 +30,10 @@ TUIKit Compose offers a complete set of instant messaging UI components, built o
30
30
 
31
31
  > **Note:**
32
32
  >
33
- > - This project currently only supports manual integration and does not support integration via package managers such as Maven.
34
- > - To ensure a stable build environment, strictly follow the official compatibility requirements:
35
- > - For compatibility between Gradle, Android Gradle Plugin, JDK, and Android Studio, refer to the official Android documentation: [Version Notes](https://developer.android.com/build/releases/gradle-plugin#updating-gradle).
36
- > - For the version mapping between Kotlin, Android Gradle Plugin, and Gradle, refer to the official Kotlin documentation: [Kotlin-Gradle Plugin Compatibility](https://kotlinlang.org/docs/gradle-configure-project.html#apply-the-plugin).
37
-
33
+ > - This project currently only supports manual integration and does not support integration via package managers such as Maven.
34
+ > - To ensure a stable build environment, strictly follow the official compatibility requirements:
35
+ > - For compatibility between Gradle, Android Gradle Plugin, JDK, and Android Studio, refer to the official Android documentation: [Version Notes](https://developer.android.com/build/releases/gradle-plugin#updating-gradle).
36
+ > - For the version mapping between Kotlin, Android Gradle Plugin, and Gradle, refer to the official Kotlin documentation: [Kotlin-Gradle Plugin Compatibility](https://kotlinlang.org/docs/gradle-configure-project.html#apply-the-plugin).
38
37
  > We recommend selecting a version combination that matches your project requirements exactly, based on the guidelines above.
39
38
  >
40
39
 
@@ -80,7 +79,6 @@ TUIKit Compose offers a complete set of instant messaging UI components, built o
80
79
 
81
80
  > **Note:**
82
81
  >
83
-
84
82
  > TUIKit_Android_Compose can be placed anywhere, as long as the relative path is correctly set in settings.gradle.
85
83
  >
86
84
 
@@ -118,8 +116,8 @@ dependencies {
118
116
 
119
117
  > **Notice:**
120
118
  >
121
- > - When using the local integration approach, to upgrade, obtain the latest component code from GitHub and overwrite your local TUIKit Compose directory.
122
- > - If there are conflicts between your private modifications and the remote repository, you need to manually merge and resolve conflicts.
119
+ > - When using the local integration approach, to upgrade, obtain the latest component code from GitHub and overwrite your local TUIKit Compose directory.
120
+ > - If there are conflicts between your private modifications and the remote repository, you need to manually merge and resolve conflicts.
123
121
 
124
122
  ### Project Configuration
125
123
  1. Locate the AndroidManifest.xml file in your app directory, and add `tools:replace="android:allowBackup"` to the `application` node to override the component's setting with your own.
@@ -262,7 +260,6 @@ LoginStore.shared.login(context, SDKAPPID, userID, userSig,
262
260
 
263
261
  > **Warning:**
264
262
  >
265
-
266
263
  > In a production environment, generate UserSig on your server. When UserSig is needed, your app should request a dynamic UserSig from your business server for authentication. See [Server-side UserSig Generation](https://trtc.io/document/34385).
267
264
  >
268
265
 
@@ -24,12 +24,11 @@ TUIKit offers a full suite of instant messaging UI components, built on the Atom
24
24
 
25
25
  > **Note:**
26
26
  >
27
- > - This project currently supports manual integration only; pub.dev integration is not available.
28
- > - To maintain a stable build environment, strictly follow official compatibility requirements:
29
- > - For compatibility between Gradle, Android Gradle Plugin, JDK, and Android Studio, refer to the official Android documentation: [Release Notes](https://developer.android.com/build/releases/gradle-plugin#updating-gradle).
30
- > - For version mapping between Kotlin, Android Gradle Plugin, and Gradle, refer to the official Kotlin documentation: [Kotlin-Gradle Plugin Compatibility](https://kotlinlang.org/docs/gradle-configure-project.html#apply-the-plugin).
31
- > - Use JDK 17; other versions may cause build failures. See: [Switching Java Versions](https://developer.android.com/build/jdks#kts).
32
-
27
+ > - This project currently supports manual integration only; pub.dev integration is not available.
28
+ > - To maintain a stable build environment, strictly follow official compatibility requirements:
29
+ > - For compatibility between Gradle, Android Gradle Plugin, JDK, and Android Studio, refer to the official Android documentation: [Release Notes](https://developer.android.com/build/releases/gradle-plugin#updating-gradle).
30
+ > - For version mapping between Kotlin, Android Gradle Plugin, and Gradle, refer to the official Kotlin documentation: [Kotlin-Gradle Plugin Compatibility](https://kotlinlang.org/docs/gradle-configure-project.html#apply-the-plugin).
31
+ > - Use JDK 17; other versions may cause build failures. See: [Switching Java Versions](https://developer.android.com/build/jdks#kts).
33
32
  > We recommend choosing a version combination that matches your project requirements according to the guidelines above.
34
33
  >
35
34
 
@@ -78,9 +77,9 @@ TUIKit offers a full suite of instant messaging UI components, built on the Atom
78
77
 
79
78
  > **Note:**
80
79
  >
81
- > - You can modify the tuikit_atomic_x dependency in chat/uikit/pubspec.yaml to depend on the online version from pub.
82
- > - To upgrade, obtain the latest component code from GitHub and overwrite your local TUIKit_Flutter directory.
83
- > - If you make private modifications that conflict with the remote repository, manually merge and resolve conflicts.
80
+ > - You can modify the tuikit_atomic_x dependency in chat/uikit/pubspec.yaml to depend on the online version from pub.
81
+ > - To upgrade, obtain the latest component code from GitHub and overwrite your local TUIKit_Flutter directory.
82
+ > - If you make private modifications that conflict with the remote repository, manually merge and resolve conflicts.
84
83
 
85
84
  ### Project Configuration
86
85
 
@@ -115,7 +114,6 @@ end
115
114
 
116
115
  > **Note:**
117
116
  >
118
-
119
117
  > If you do not have a Gradle global configuration file `~/.gradle/init.gradle`, skip this step. If it exists and contains `allprojects.repositories`, you can remove the related content or delete `~/.gradle/init.gradle` (backup recommended) to avoid runtime errors.
120
118
  >
121
119
 
@@ -150,7 +148,6 @@ if (result.errorCode == 0) {
150
148
 
151
149
  > **Caution:**
152
150
  >
153
-
154
151
  > In production, generate UserSig on your server. When UserSig is needed, your app should request a dynamic UserSig from your business server for authentication. See [Server-side UserSig Generation](https://trtc.io/document/34385).
155
152
  >
156
153
 
@@ -357,7 +354,7 @@ Refer to the webhook descriptions and code above to implement navigation logic b
357
354
 
358
355
  ## FAQs
359
356
 
360
- ### **What should I do if I encounter errors with **`theme_state`** and **`atomic_localizations`** after integrating the tuikit_atomic_x component?**
357
+ ### **What should I do if I encounter errors with** `theme_state` **and** `atomic_localizations` **after integrating the tuikit_atomic_x component?**
361
358
 
362
359
  The component supports theme color and internationalization string switching. Wrap the root `widget` in your project's `main.dart` file with `ComponentTheme`, and add `AtomicLocalizations.delegate` to the `localizationsDelegates` of `MaterialApp`. See the Demo's `main.dart` file in the source code for reference.
363
360
 
@@ -24,7 +24,6 @@ TUIKit SwiftUI provides a comprehensive set of instant messaging UI components,
24
24
 
25
25
  > **Note:**
26
26
  >
27
-
28
27
  > This project currently only supports manual integration. Integration via package managers such as CocoaPods or SPM is not supported.
29
28
  >
30
29
 
@@ -117,8 +116,8 @@ chat/
117
116
 
118
117
  > **Notice:**
119
118
  >
120
- > - For local integration, to upgrade, download the latest component code from [GitHub](https://github.com/Tencent-RTC/TUIKit_iOS_SwiftUI/tree/main/atomic-x) and overwrite your local TUIKit SwiftUI directory.
121
- > - If you have made private modifications that conflict with the remote repository, you will need to manually merge and resolve those conflicts.
119
+ > - For local integration, to upgrade, download the latest component code from [GitHub](https://github.com/Tencent-RTC/TUIKit_iOS_SwiftUI/tree/main/atomic-x) and overwrite your local TUIKit SwiftUI directory.
120
+ > - If you have made private modifications that conflict with the remote repository, you will need to manually merge and resolve those conflicts.
122
121
 
123
122
  ### Project Configuration
124
123
  1. **Configure Build Settings**
@@ -168,7 +167,6 @@ LoginStore.shared.login(sdkAppID: sdkAppID, userID: userID, userSig: userSig, co
168
167
 
169
168
  > **Warning:**
170
169
  >
171
-
172
170
  > In a production environment, generate UserSig on your server. When UserSig is needed, your app should request a dynamic UserSig from your business server for authentication. See [Server-side UserSig Generation](https://trtc.io/document/34385).
173
171
  >
174
172
 
@@ -40,7 +40,6 @@ Download [chat-uikit-react](https://www.npmjs.com/package/@tencentcloud/chat-uik
40
40
 
41
41
  > **Tips:**
42
42
  >
43
-
44
43
  > It is recommended to use npm for installation, as npm will automatically download the required peerDependencies dependencies.
45
44
  >
46
45
 
@@ -53,7 +52,6 @@ npm i @tencentcloud/chat-uikit-react
53
52
 
54
53
  > **Note:**
55
54
  >
56
-
57
55
  > The following code does not include `SDKAppID`, `userID`, and `UserSig`. You need to replace them with the relevant information obtained in console.
58
56
  >
59
57
 
@@ -305,10 +303,8 @@ In the previously copied `App.tsx` code, the login authentication information is
305
303
 
306
304
  > **Explanation of UserSig:**
307
305
  >
308
-
309
306
  > **Development environment**: If you are running a demo locally and developing or debugging, you can use the `genTestUserSig` (Refer to Step 3.2) function in the debug file to generate a 'userSig'. In this method, SDKSecretKey is vulnerable to decompilation and reverse engineering. Once your key is leaked, attackers can steal your Tencent Cloud traffic.
310
307
  >
311
-
312
308
  > **Production environment**: If your project is going live, please use the [Server-side Generation of UserSig](https://trtc.io/document/34385) method.
313
309
  >
314
310
 
@@ -347,7 +343,6 @@ Enter your message in the input box and press Enter to send.
347
343
 
348
344
  > **Note:**
349
345
  >
350
-
351
346
  > TUICallKit is an Audio/Video Calls UI component developed by TRTC. Integrating TUICallKit allows you to add Audio/Video Calls functionality to your chat application with minimal code. For comprehensive setup instructions, see [Audio/Video Calls > Activate the service](https://trtc.io/document/59832).
352
347
  >
353
348
 
@@ -382,16 +377,12 @@ Enter your message in the input box and press Enter to send.
382
377
 
383
378
  > **Tips:**
384
379
  >
385
-
386
380
  > Search is a critical capability for customer service, social networking, online education, telemedicine, and office automation systems. It enables users to quickly find groups, users, and messages, improving both the user experience and engagement.
387
381
  >
388
-
389
382
  > Due to limitations in local storage within the Web platform, Vue does not support local search. To address these requirements, we provide Cloud Search functionality.
390
383
  >
391
-
392
384
  > Cloud Search supports both global search and in-conversation search, allowing you to search groups, users, and messages.
393
385
  >
394
-
395
386
  > Cloud Search is a value-added feature and requires the purchase of the Cloud Search plugin. To purchase, click [Purchase](https://console.trtc.io/chat/plugin/TUICloudSearch).
396
387
  >
397
388
 
@@ -437,7 +428,6 @@ The issuance method for UserSig involves integrating the calculation code of Use
437
428
 
438
429
  > **Note:**
439
430
  >
440
-
441
431
  > The exemplary code provided in this document retrieves the UserSig by embedding the SECRETKEY in the client code. This approach makes the SECRETKEY highly susceptible to decompilation and reverse engineering. Once your encryption key is compromised, attackers can misappropriate your Tencent Cloud traffic. Hence, **this procedure is exclusively recommended for running functional debugging locally**. For the correct issuance of UserSig, please refer to the previous sections.
442
432
  >
443
433