@tencent-rtc/mcp 1.2.6 → 1.2.7
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/package.json +1 -1
- package/resource/doc/chatuikit/faq/common/server_error_code.md +74 -0
- package/resource/doc/chatuikit/faq/web_sdk/error_code.md +47 -0
- package/resource/doc/chatuikit/faq/web_sdk/faq.md +105 -0
- package/resource/doc/chatuikit/flutter/faq.md +120 -0
- package/resource/doc/chatuikit/iOS/faq.md +120 -0
- package/resource/doc/chatuikit/react/faq.md +26 -0
- package/resource/doc/chatuikit/vue/faq.md +36 -0
- package/resource/doc/livekit/faq/common/error_code.md +88 -0
- package/resource/doc/livekit/vue/faq.md +0 -0
- package/resource/doc/roomkit/faq/common/error_code.md +67 -0
- package/resource/doc/roomkit/vue/faq.md +0 -0
- package/resource/doc/rtcengine/faq/common/error_code.md +0 -0
- package/resource/doc/rtcengine/faq/web_sdk/.gitkeep +0 -0
- package/resource/doc/tuicallkit/faq/common/error_code.md +47 -0
- package/resource/doc/tuicallkit/flutter/faq.md +127 -0
- package/resource/doc/tuicallkit/iOS/faq.md +127 -0
- package/resource/doc/tuicallkit/react/faq.md +36 -0
- package/resource/doc/tuicallkit/vue/faq.md +36 -0
- package/tools/call/get-native-call-integration.js +4 -10
- package/tools/call/get-native-call-integration.js.map +1 -1
- package/tools/call/get-web-call-api.js +4 -7
- package/tools/call/get-web-call-api.js.map +1 -1
- package/tools/call/get-web-call-integration.js +4 -9
- package/tools/call/get-web-call-integration.js.map +1 -1
- package/tools/chat/get-native-chat-integration.js +4 -9
- package/tools/chat/get-native-chat-integration.js.map +1 -1
- package/tools/chat/get-web-chat-component-detail.js +5 -10
- package/tools/chat/get-web-chat-component-detail.js.map +1 -1
- package/tools/chat/get-web-chat-integration.js +4 -12
- package/tools/chat/get-web-chat-integration.js.map +1 -1
- package/tools/chat/get-web-chat-uikit-init.js +5 -6
- package/tools/chat/get-web-chat-uikit-init.js.map +1 -1
- package/tools/chat/get-web-chat-window-integration.js +4 -12
- package/tools/chat/get-web-chat-window-integration.js.map +1 -1
- package/tools/chat/{create-group.js → get-web-create-group-doc.js} +5 -6
- package/tools/chat/get-web-create-group-doc.js.map +1 -0
- package/tools/common/get-faq.js +93 -0
- package/tools/common/get-faq.js.map +1 -0
- package/tools/common/get-usersig.js +9 -18
- package/tools/common/get-usersig.js.map +1 -1
- package/tools/common/present-framework-choice.js +3 -10
- package/tools/common/present-framework-choice.js.map +1 -1
- package/tools/common/record-prompt.js +5 -11
- package/tools/common/record-prompt.js.map +1 -1
- package/tools/common/record-result.js +8 -12
- package/tools/common/record-result.js.map +1 -1
- package/tools/definitions/get_faq_def.js +28 -0
- package/tools/definitions/get_faq_def.js.map +1 -0
- package/tools/definitions/get_native_call_uikit_integration_def.js +21 -0
- package/tools/definitions/get_native_call_uikit_integration_def.js.map +1 -0
- package/tools/definitions/get_native_chat_uikit_integration_def.js +21 -0
- package/tools/definitions/get_native_chat_uikit_integration_def.js.map +1 -0
- package/tools/definitions/get_usersig_def.js +32 -0
- package/tools/definitions/get_usersig_def.js.map +1 -0
- package/tools/definitions/get_web_call_uikit_api_def.js +23 -0
- package/tools/definitions/get_web_call_uikit_api_def.js.map +1 -0
- package/tools/definitions/get_web_call_uikit_integration_def.js +20 -0
- package/tools/definitions/get_web_call_uikit_integration_def.js.map +1 -0
- package/tools/definitions/get_web_chat_uikit_component_detail_def.js +24 -0
- package/tools/definitions/get_web_chat_uikit_component_detail_def.js.map +1 -0
- package/tools/definitions/get_web_chat_uikit_init_def.js +23 -0
- package/tools/definitions/get_web_chat_uikit_init_def.js.map +1 -0
- package/tools/definitions/get_web_chat_uikit_integration_def.js +26 -0
- package/tools/definitions/get_web_chat_uikit_integration_def.js.map +1 -0
- package/tools/definitions/get_web_chat_window_integration_def.js +26 -0
- package/tools/definitions/get_web_chat_window_integration_def.js.map +1 -0
- package/tools/definitions/get_web_create_group_doc_def.js +18 -0
- package/tools/definitions/get_web_create_group_doc_def.js.map +1 -0
- package/tools/definitions/get_web_live_state_detail_def.js +19 -0
- package/tools/definitions/get_web_live_state_detail_def.js.map +1 -0
- package/tools/definitions/get_web_live_uikit_component_detail_def.js +22 -0
- package/tools/definitions/get_web_live_uikit_component_detail_def.js.map +1 -0
- package/tools/definitions/get_web_room_state_detail_def.js +19 -0
- package/tools/definitions/get_web_room_state_detail_def.js.map +1 -0
- package/tools/definitions/present_framework_choice_def.js +23 -0
- package/tools/definitions/present_framework_choice_def.js.map +1 -0
- package/tools/definitions/record_prompt_def.js +22 -0
- package/tools/definitions/record_prompt_def.js.map +1 -0
- package/tools/definitions/record_result_def.js +22 -0
- package/tools/definitions/record_result_def.js.map +1 -0
- package/tools/index.js +7 -7
- package/tools/index.js.map +1 -1
- package/tools/live/get-web-live-component-detail.js +5 -7
- package/tools/live/get-web-live-component-detail.js.map +1 -1
- package/tools/live/get-web-live-state-detail.js +5 -7
- package/tools/live/get-web-live-state-detail.js.map +1 -1
- package/tools/room/get-web-room-state-detail.js +5 -7
- package/tools/room/get-web-room-state-detail.js.map +1 -1
- package/utils/report-cls-client.js +1 -1
- package/utils/report-es-client.js +1 -1
- package/libs/@tencent/aegis-node-sdk/CHANGELOG.md +0 -8
- package/libs/@tencent/aegis-node-sdk/LICENSE +0 -21
- package/libs/@tencent/aegis-node-sdk/README.md +0 -562
- package/libs/@tencent/aegis-node-sdk/lib/aegis.min.js +0 -1
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/constant/config.d.ts +0 -14
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/constant/global.d.ts +0 -1
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/constant/index.d.ts +0 -9
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/constant/report-ignore.d.ts +0 -2
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/core.d.ts +0 -85
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/hooks/afterRequestHooks.d.ts +0 -3
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/hooks/beforeRequestHooks.d.ts +0 -9
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/hooks/modifyRequestHooks.d.ts +0 -3
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/index.d.ts +0 -9
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/interface/config.d.ts +0 -62
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/interface/env.d.ts +0 -11
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/interface/index.d.ts +0 -4
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/interface/log.d.ts +0 -130
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/interface/send.d.ts +0 -34
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/format.d.ts +0 -2
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/index.d.ts +0 -18
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/length-limit.d.ts +0 -8
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/pv.d.ts +0 -8
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/remove-payload.d.ts +0 -2
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/repeat-limit.d.ts +0 -4
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/report.d.ts +0 -10
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/sample.d.ts +0 -3
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/throttle.d.ts +0 -3
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/trace/index.d.ts +0 -34
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/trace/jwt.d.ts +0 -12
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/trace/ot-js.d.ts +0 -14
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/trace/uuid.d.ts +0 -2
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/whitelist.d.ts +0 -12
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/pipes/write-before.d.ts +0 -3
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/plugin.d.ts +0 -33
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/util/destroy.d.ts +0 -2
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/util/event-emitter.d.ts +0 -18
- package/libs/@tencent/aegis-node-sdk/lib/packages/core/src/util/index.d.ts +0 -60
- package/libs/@tencent/aegis-node-sdk/lib/packages/node-sdk/src/index.d.ts +0 -15
- package/libs/@tencent/aegis-node-sdk/lib/packages/node-sdk/src/interface/selector.d.ts +0 -5
- package/libs/@tencent/aegis-node-sdk/lib/packages/node-sdk/src/pipes/batch-report-pipe.d.ts +0 -6
- package/libs/@tencent/aegis-node-sdk/lib/packages/node-sdk/src/protocol/protocol_base.d.ts +0 -18
- package/libs/@tencent/aegis-node-sdk/lib/packages/node-sdk/src/protocol/protocol_http.d.ts +0 -12
- package/libs/@tencent/aegis-node-sdk/lib/packages/node-sdk/src/selector/ip_selector.d.ts +0 -10
- package/libs/@tencent/aegis-node-sdk/lib/packages/node-sdk/src/selector/polaris_selector.d.ts +0 -20
- package/libs/@tencent/aegis-node-sdk/lib/packages/node-sdk/src/selector/selector_base.d.ts +0 -27
- package/libs/@tencent/aegis-node-sdk/lib/packages/node-sdk/src/util/eval_require.d.ts +0 -2
- package/libs/@tencent/aegis-node-sdk/package.json +0 -19
- package/libs/@tencent/polaris/README.md +0 -407
- package/libs/@tencent/polaris/dist/consumer/health.d.ts +0 -126
- package/libs/@tencent/polaris/dist/consumer/health.js +0 -283
- package/libs/@tencent/polaris/dist/consumer/health.js.map +0 -1
- package/libs/@tencent/polaris/dist/consumer/index.d.ts +0 -120
- package/libs/@tencent/polaris/dist/consumer/index.js +0 -348
- package/libs/@tencent/polaris/dist/consumer/index.js.map +0 -1
- package/libs/@tencent/polaris/dist/consumer/monitor.d.ts +0 -145
- package/libs/@tencent/polaris/dist/consumer/monitor.js +0 -343
- package/libs/@tencent/polaris/dist/consumer/monitor.js.map +0 -1
- package/libs/@tencent/polaris/dist/consumer/selector.d.ts +0 -73
- package/libs/@tencent/polaris/dist/consumer/selector.js +0 -316
- package/libs/@tencent/polaris/dist/consumer/selector.js.map +0 -1
- package/libs/@tencent/polaris/dist/errors.d.ts +0 -373
- package/libs/@tencent/polaris/dist/errors.js +0 -154
- package/libs/@tencent/polaris/dist/errors.js.map +0 -1
- package/libs/@tencent/polaris/dist/global.d.ts +0 -16
- package/libs/@tencent/polaris/dist/global.js +0 -18
- package/libs/@tencent/polaris/dist/global.js.map +0 -1
- package/libs/@tencent/polaris/dist/index.d.ts +0 -62
- package/libs/@tencent/polaris/dist/index.js +0 -145
- package/libs/@tencent/polaris/dist/index.js.map +0 -1
- package/libs/@tencent/polaris/dist/instance.d.ts +0 -109
- package/libs/@tencent/polaris/dist/instance.js +0 -38
- package/libs/@tencent/polaris/dist/instance.js.map +0 -1
- package/libs/@tencent/polaris/dist/limiter/bucket.d.ts +0 -51
- package/libs/@tencent/polaris/dist/limiter/bucket.js +0 -152
- package/libs/@tencent/polaris/dist/limiter/bucket.js.map +0 -1
- package/libs/@tencent/polaris/dist/limiter/index.d.ts +0 -73
- package/libs/@tencent/polaris/dist/limiter/index.js +0 -149
- package/libs/@tencent/polaris/dist/limiter/index.js.map +0 -1
- package/libs/@tencent/polaris/dist/limiter/ratelimit.d.ts +0 -27
- package/libs/@tencent/polaris/dist/limiter/ratelimit.js +0 -134
- package/libs/@tencent/polaris/dist/limiter/ratelimit.js.map +0 -1
- package/libs/@tencent/polaris/dist/limiter/ratelimiter/base.d.ts +0 -17
- package/libs/@tencent/polaris/dist/limiter/ratelimiter/base.js +0 -15
- package/libs/@tencent/polaris/dist/limiter/ratelimiter/base.js.map +0 -1
- package/libs/@tencent/polaris/dist/limiter/ratelimiter/global.d.ts +0 -59
- package/libs/@tencent/polaris/dist/limiter/ratelimiter/global.js +0 -397
- package/libs/@tencent/polaris/dist/limiter/ratelimiter/global.js.map +0 -1
- package/libs/@tencent/polaris/dist/limiter/ratelimiter/index.d.ts +0 -3
- package/libs/@tencent/polaris/dist/limiter/ratelimiter/index.js +0 -19
- package/libs/@tencent/polaris/dist/limiter/ratelimiter/index.js.map +0 -1
- package/libs/@tencent/polaris/dist/limiter/ratelimiter/local.d.ts +0 -17
- package/libs/@tencent/polaris/dist/limiter/ratelimiter/local.js +0 -52
- package/libs/@tencent/polaris/dist/limiter/ratelimiter/local.js.map +0 -1
- package/libs/@tencent/polaris/dist/location.d.ts +0 -48
- package/libs/@tencent/polaris/dist/location.js +0 -67
- package/libs/@tencent/polaris/dist/location.js.map +0 -1
- package/libs/@tencent/polaris/dist/logging.d.ts +0 -106
- package/libs/@tencent/polaris/dist/logging.js +0 -130
- package/libs/@tencent/polaris/dist/logging.js.map +0 -1
- package/libs/@tencent/polaris/dist/metadata.d.ts +0 -78
- package/libs/@tencent/polaris/dist/metadata.js +0 -119
- package/libs/@tencent/polaris/dist/metadata.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/breaker/polaris.d.ts +0 -47
- package/libs/@tencent/polaris/dist/plugins/breaker/polaris.js +0 -162
- package/libs/@tencent/polaris/dist/plugins/breaker/polaris.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/lb/base.d.ts +0 -24
- package/libs/@tencent/polaris/dist/plugins/lb/base.js +0 -32
- package/libs/@tencent/polaris/dist/plugins/lb/base.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/lb/edf.d.ts +0 -24
- package/libs/@tencent/polaris/dist/plugins/lb/edf.js +0 -77
- package/libs/@tencent/polaris/dist/plugins/lb/edf.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/lb/hashring.d.ts +0 -24
- package/libs/@tencent/polaris/dist/plugins/lb/hashring.js +0 -53
- package/libs/@tencent/polaris/dist/plugins/lb/hashring.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/lb/sticky.d.ts +0 -31
- package/libs/@tencent/polaris/dist/plugins/lb/sticky.js +0 -88
- package/libs/@tencent/polaris/dist/plugins/lb/sticky.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/lb/swrr.d.ts +0 -25
- package/libs/@tencent/polaris/dist/plugins/lb/swrr.js +0 -72
- package/libs/@tencent/polaris/dist/plugins/lb/swrr.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/lb/wr.d.ts +0 -17
- package/libs/@tencent/polaris/dist/plugins/lb/wr.js +0 -50
- package/libs/@tencent/polaris/dist/plugins/lb/wr.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/lb/wrr.d.ts +0 -19
- package/libs/@tencent/polaris/dist/plugins/lb/wrr.js +0 -81
- package/libs/@tencent/polaris/dist/plugins/lb/wrr.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/logging/console.d.ts +0 -10
- package/libs/@tencent/polaris/dist/plugins/logging/console.js +0 -38
- package/libs/@tencent/polaris/dist/plugins/logging/console.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/naming/local-server/index.d.ts +0 -32
- package/libs/@tencent/polaris/dist/plugins/naming/local-server/index.js +0 -88
- package/libs/@tencent/polaris/dist/plugins/naming/local-server/index.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/base.d.ts +0 -124
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/base.js +0 -398
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/base.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/discover.d.ts +0 -27
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/discover.js +0 -287
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/discover.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/index.d.ts +0 -15
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/index.js +0 -43
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/index.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/monitor.d.ts +0 -28
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/monitor.js +0 -249
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/monitor.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/ratelimit.d.ts +0 -19
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/ratelimit.js +0 -222
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/adapter/ratelimit.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/connector/grpc/bidi.d.ts +0 -26
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/connector/grpc/bidi.js +0 -99
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/connector/grpc/bidi.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/connector/grpc/index.d.ts +0 -60
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/connector/grpc/index.js +0 -259
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/connector/grpc/index.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/connector/grpc/pb/discover.proto +0 -24
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/connector/grpc/pb/monitor.proto +0 -18
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/connector/grpc/pb/ratelimit.proto +0 -12
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/connector/http/index.d.ts +0 -39
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/connector/http/index.js +0 -115
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/connector/http/index.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/discover-pb/api.proto +0 -24
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/discover-pb/client.proto +0 -22
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/discover-pb/model.proto +0 -28
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/discover-pb/ratelimit.proto +0 -80
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/discover-pb/request.proto +0 -18
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/discover-pb/response.proto +0 -65
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/discover-pb/routing.proto +0 -66
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/discover-pb/service.proto +0 -95
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/discover-pb/types.d.ts +0 -1568
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/index.d.ts +0 -36
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/index.js +0 -51
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/index.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/monitor-pb/api.proto +0 -18
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/monitor-pb/circuitbreak.proto +0 -67
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/monitor-pb/request.proto +0 -82
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/monitor-pb/response.proto +0 -11
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/monitor-pb/sdkcache.proto +0 -46
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/monitor-pb/sdkconfiguration.proto +0 -16
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/monitor-pb/sdktoken.proto +0 -10
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/monitor-pb/types.d.ts +0 -1102
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/pool.d.ts +0 -29
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/pool.js +0 -77
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/pool.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/ratelimit-pb/api.proto +0 -12
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/ratelimit-pb/ratelimit.proto +0 -28
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/ratelimit-pb/types.d.ts +0 -395
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/rules.d.ts +0 -13
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/rules.js +0 -116
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/rules.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/types.d.ts +0 -67
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/types.js +0 -67
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/types.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/utils.d.ts +0 -99
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/utils.js +0 -217
- package/libs/@tencent/polaris/dist/plugins/naming/polaris-server/utils.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/registry/memory.d.ts +0 -10
- package/libs/@tencent/polaris/dist/plugins/registry/memory.js +0 -50
- package/libs/@tencent/polaris/dist/plugins/registry/memory.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/router/polaris/nearby.d.ts +0 -51
- package/libs/@tencent/polaris/dist/plugins/router/polaris/nearby.js +0 -145
- package/libs/@tencent/polaris/dist/plugins/router/polaris/nearby.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/router/polaris/rule.d.ts +0 -11
- package/libs/@tencent/polaris/dist/plugins/router/polaris/rule.js +0 -174
- package/libs/@tencent/polaris/dist/plugins/router/polaris/rule.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/router/trpc/canary.d.ts +0 -25
- package/libs/@tencent/polaris/dist/plugins/router/trpc/canary.js +0 -36
- package/libs/@tencent/polaris/dist/plugins/router/trpc/canary.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/router/trpc/env.d.ts +0 -10
- package/libs/@tencent/polaris/dist/plugins/router/trpc/env.js +0 -34
- package/libs/@tencent/polaris/dist/plugins/router/trpc/env.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/router/trpc/set.d.ts +0 -56
- package/libs/@tencent/polaris/dist/plugins/router/trpc/set.js +0 -106
- package/libs/@tencent/polaris/dist/plugins/router/trpc/set.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/shaping/unirate.d.ts +0 -31
- package/libs/@tencent/polaris/dist/plugins/shaping/unirate.js +0 -124
- package/libs/@tencent/polaris/dist/plugins/shaping/unirate.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/shaping/warmup.d.ts +0 -61
- package/libs/@tencent/polaris/dist/plugins/shaping/warmup.js +0 -171
- package/libs/@tencent/polaris/dist/plugins/shaping/warmup.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins/weight/polaris.d.ts +0 -23
- package/libs/@tencent/polaris/dist/plugins/weight/polaris.js +0 -159
- package/libs/@tencent/polaris/dist/plugins/weight/polaris.js.map +0 -1
- package/libs/@tencent/polaris/dist/plugins.d.ts +0 -619
- package/libs/@tencent/polaris/dist/plugins.js +0 -91
- package/libs/@tencent/polaris/dist/plugins.js.map +0 -1
- package/libs/@tencent/polaris/dist/polaris.d.ts +0 -33
- package/libs/@tencent/polaris/dist/polaris.js +0 -59
- package/libs/@tencent/polaris/dist/polaris.js.map +0 -1
- package/libs/@tencent/polaris/dist/provider/index.d.ts +0 -102
- package/libs/@tencent/polaris/dist/provider/index.js +0 -168
- package/libs/@tencent/polaris/dist/provider/index.js.map +0 -1
- package/libs/@tencent/polaris/dist/registry.d.ts +0 -174
- package/libs/@tencent/polaris/dist/registry.js +0 -660
- package/libs/@tencent/polaris/dist/registry.js.map +0 -1
- package/libs/@tencent/polaris/dist/rules.d.ts +0 -163
- package/libs/@tencent/polaris/dist/rules.js +0 -24
- package/libs/@tencent/polaris/dist/rules.js.map +0 -1
- package/libs/@tencent/polaris/dist/scripts/postinstall.d.ts +0 -1
- package/libs/@tencent/polaris/dist/scripts/postinstall.js +0 -71
- package/libs/@tencent/polaris/dist/scripts/postinstall.js.map +0 -1
- package/libs/@tencent/polaris/dist/service.d.ts +0 -18
- package/libs/@tencent/polaris/dist/service.js +0 -3
- package/libs/@tencent/polaris/dist/service.js.map +0 -1
- package/libs/@tencent/polaris/dist/skeleton.d.ts +0 -87
- package/libs/@tencent/polaris/dist/skeleton.js +0 -282
- package/libs/@tencent/polaris/dist/skeleton.js.map +0 -1
- package/libs/@tencent/polaris/dist/utils.d.ts +0 -36
- package/libs/@tencent/polaris/dist/utils.js +0 -74
- package/libs/@tencent/polaris/dist/utils.js.map +0 -1
- package/libs/@tencent/polaris/dist/weak.d.ts +0 -11
- package/libs/@tencent/polaris/dist/weak.js +0 -44
- package/libs/@tencent/polaris/dist/weak.js.map +0 -1
- package/libs/@tencent/polaris/package.json +0 -114
- package/resource/doc/chatuikit/faq/generate_UserSig.md +0 -306
- package/tools/call/get-call-faq.js +0 -29
- package/tools/call/get-call-faq.js.map +0 -1
- package/tools/chat/create-group.js.map +0 -1
- package/tools/chat/get-chat-faq.js +0 -29
- package/tools/chat/get-chat-faq.js.map +0 -1
- /package/resource/doc/chatuikit/{faq/faq_sdk.md → android/faq.md} +0 -0
- /package/{libs/@tencent/aegis-node-sdk/lib/packages/core/src/polyfill.d.ts → resource/doc/chatuikit/faq/native_sdk/faq.md} +0 -0
- /package/resource/doc/tuicallkit/{faq → android}/faq.md +0 -0
package/package.json
CHANGED
|
@@ -0,0 +1,74 @@
|
|
|
1
|
+
---
|
|
2
|
+
product: 'Chat'
|
|
3
|
+
tech_stack: 'server'
|
|
4
|
+
framework: 'common'
|
|
5
|
+
title: 'Server Error Code Reference'
|
|
6
|
+
keywords: ['error code', 'error', 'login failure', '70001']
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# Server Error Code Reference
|
|
10
|
+
|
|
11
|
+
## Server Error Codes (Topic: Server)
|
|
12
|
+
|
|
13
|
+
## Error Code 70001
|
|
14
|
+
**Cause:** UserSig has expired.
|
|
15
|
+
**Solution:** Please regenerate the UserSig. It is recommended to set the UserSig validity period to no less than 24 hours.
|
|
16
|
+
|
|
17
|
+
## Error Code 70003
|
|
18
|
+
**Cause:** Invalid UserSig.
|
|
19
|
+
**Solution:** Please regenerate the UserSig. Refer to the official documentation for generation methods: https://trtc.io/document/34385?platform=android&product=chat&menulabel=core%20sdk.
|
|
20
|
+
|
|
21
|
+
## Error Code 70009
|
|
22
|
+
**Cause:** UserSig verification failed. The UserSig may have been generated using a key or private key from a different SDKAppID.
|
|
23
|
+
**Solution:** Please verify that the requested SDKAppID matches the key or private key used to generate the UserSig.
|
|
24
|
+
|
|
25
|
+
## Error Code 70013
|
|
26
|
+
**Cause:** The userID in the request does not match the userID used when generating the UserSig.
|
|
27
|
+
**Solution:** Please check if the userID used to login to IM matches the userID used to generate the UserSig.
|
|
28
|
+
|
|
29
|
+
## Error Code 70014
|
|
30
|
+
**Cause:** The SDKAppID in the request does not match the SDKAppID used when generating the UserSig.
|
|
31
|
+
**Solution:** You can verify the UserSig using the IM Console > Development Tools > UserSig Generation & Verification tool: https://console.trtc.io/usersig.
|
|
32
|
+
|
|
33
|
+
## Error Code 20003
|
|
34
|
+
**Cause:** Invalid or non-existent userID for message sender or receiver.
|
|
35
|
+
**Solution:** Please confirm that the userID has been logged into IM under your SDKAppID.
|
|
36
|
+
|
|
37
|
+
## Error Code 20009
|
|
38
|
+
**Cause:** Sender and receiver are not friends, sending is prohibited.
|
|
39
|
+
**Solution:** The sender and receiver are not friends. Sending is prohibited when friend relationship verification is configured for one-to-one messages. To send messages to non-friends, you need to configure this in the console or add them as friends first.
|
|
40
|
+
|
|
41
|
+
## Error Code 20010
|
|
42
|
+
**Cause:** Sender is not in the receiver's friend list, sending is prohibited.
|
|
43
|
+
**Solution:** When sending one-to-one messages, the sender is not in the receiver's friend list (one-way relationship), sending is prohibited.
|
|
44
|
+
|
|
45
|
+
## Error Code 3122
|
|
46
|
+
**Cause:** Your current package does not support this feature.
|
|
47
|
+
**Solution:** You can upgrade to the Ultimate Edition package: https://console.trtc.io/subscription/buy/chat?packType=pro.
|
|
48
|
+
|
|
49
|
+
## Error Code 60020
|
|
50
|
+
**Cause:** Cloud search feature is not enabled for your current package.
|
|
51
|
+
**Solution:** You can enable Cloud Search: https://console.trtc.io/chat/plugin/TUICloudSearch.
|
|
52
|
+
|
|
53
|
+
## Error Code 60018
|
|
54
|
+
**Cause:** Cloud search request exceeded backend rate limit. Each user is allowed 2 search requests per second.
|
|
55
|
+
**Solution:** Please adjust the request frequency and try again later.
|
|
56
|
+
|
|
57
|
+
## Error Code 80004
|
|
58
|
+
**Cause:** Sensitive content detected in message or profile text.
|
|
59
|
+
**Solution:** Please check if the message or profile contains sensitive information.
|
|
60
|
+
|
|
61
|
+
## Error Code 10021
|
|
62
|
+
**Cause:** Group ID is already in use.
|
|
63
|
+
**Solution:** Please choose a different group ID.
|
|
64
|
+
|
|
65
|
+
## Error Code 10007
|
|
66
|
+
**Cause:** Common reasons include:
|
|
67
|
+
- The group type does not support this operation by default. Please check the current group type.
|
|
68
|
+
- The operation account lacks sufficient permissions (e.g., in mute operations, an admin can mute regular members but not the group owner).
|
|
69
|
+
- The account calling the REST API is not an admin account for the SDKAppID.
|
|
70
|
+
**Solution:** Please check the group type or group member role. If the error occurs when calling REST API, verify that the account is an admin account for the corresponding SDKAppID.
|
|
71
|
+
|
|
72
|
+
## Error Code 60010
|
|
73
|
+
**Cause:** Request requires App admin privileges.
|
|
74
|
+
**Solution:** Please verify that the requesting account is an admin for the SDKAppID.
|
|
@@ -0,0 +1,47 @@
|
|
|
1
|
+
---
|
|
2
|
+
product: 'Chat'
|
|
3
|
+
tech_stack: 'web_js_sdk'
|
|
4
|
+
framework: 'sdk'
|
|
5
|
+
title: 'Web JS SDK Error Code Reference'
|
|
6
|
+
keywords: ['error code', 'error', 'login failure']
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# Web JS SDK Error Code Reference
|
|
10
|
+
|
|
11
|
+
## Web JS SDK Error Codes (Topic: SDK Error Code)
|
|
12
|
+
|
|
13
|
+
## Error Code 2024
|
|
14
|
+
**Cause:** User not logged in.
|
|
15
|
+
**Solution:** Check if the login interface was called correctly.
|
|
16
|
+
|
|
17
|
+
## Error Code 2025
|
|
18
|
+
**Cause:** Duplicate login. Multiple login requests were triggered within 15 seconds, and the SDK blocked them.
|
|
19
|
+
**Solution:** Check the timing and trigger mechanism of the login interface calls.
|
|
20
|
+
|
|
21
|
+
## Error Code 2301
|
|
22
|
+
**Cause:** Audio file size exceeds the limit.
|
|
23
|
+
**Solution:** Maximum audio message size is 20MB.
|
|
24
|
+
|
|
25
|
+
## Error Code 2252
|
|
26
|
+
**Cause:** Image message sending failed due to invalid image format.
|
|
27
|
+
**Solution:** Supported image formats: 'jpg', 'jpeg', 'gif', 'png', 'bmp', 'image', 'webp'.
|
|
28
|
+
|
|
29
|
+
## Error Code 2253
|
|
30
|
+
**Cause:** Image size exceeds the limit.
|
|
31
|
+
**Solution:** Maximum image message size is 20MB.
|
|
32
|
+
|
|
33
|
+
## Error Code 2351
|
|
34
|
+
**Cause:** Video size exceeds the limit.
|
|
35
|
+
**Solution:** Maximum video message size is 100MB.
|
|
36
|
+
|
|
37
|
+
## Error Code 2352
|
|
38
|
+
**Cause:** Video message sending failed due to invalid video format.
|
|
39
|
+
**Solution:** Supported video formats: 'mp4', 'quicktime', 'mov'.
|
|
40
|
+
|
|
41
|
+
## Error Code 2401
|
|
42
|
+
**Cause:** File does not exist.
|
|
43
|
+
**Solution:** Please check if the file path is correct.
|
|
44
|
+
|
|
45
|
+
## Error Code 2402
|
|
46
|
+
**Cause:** File size exceeds the limit.
|
|
47
|
+
**Solution:** Maximum file message size is 100MB.
|
|
@@ -0,0 +1,105 @@
|
|
|
1
|
+
---
|
|
2
|
+
product: 'Chat'
|
|
3
|
+
tech_stack: 'web_js_sdk'
|
|
4
|
+
framework: 'sdk'
|
|
5
|
+
title: 'Web JS SDK Frequently Asked Questions'
|
|
6
|
+
keywords: ['sdk integration', 'login API', 'create group']
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# Web JS SDK FAQ
|
|
10
|
+
|
|
11
|
+
## Important Notice
|
|
12
|
+
**SDK Version Information:**
|
|
13
|
+
- v3: `@tencentcloud/chat`
|
|
14
|
+
When providing code examples, always use the latest version `@tencentcloud/chat` for demonstration.
|
|
15
|
+
|
|
16
|
+
## Web JS SDK Frequently Asked Questions (Topic: SDK FAQ)
|
|
17
|
+
|
|
18
|
+
### Q: How to receive streaming messages sent via Chat REST API (https://trtc.io/document/71131?product=chat&menulabel=core%20sdk&platform=javascript) through the SDK?
|
|
19
|
+
**A:** The SDK handles streaming messages through the message received event [TencentCloudChat.EVENT.MESSAGE_RECEIVED](https://trtc.io/document/47996?product=chat&menulabel=core%20sdk&platform=javascript) and message modified event [TencentCloudChat.EVENT.MESSAGE_MODIFIED](https://trtc.io/document/48005?product=chat&menulabel=core%20sdk&platform=javascript). When REST API sends the first fragment, the SDK notifies the application through the message received event. Subsequent fragments are notified through the message modified event.
|
|
20
|
+
|
|
21
|
+
### Q: Why does SDK login fail?
|
|
22
|
+
**A:** Please provide the error message or error code.
|
|
23
|
+
|
|
24
|
+
### Q: Why can I still receive SDK events after calling the off interface to unregister event listeners?
|
|
25
|
+
**A:** For the same event, such as [TencentCloudChat.EVENT.MESSAGE_RECEIVED](https://trtc.io/document/47996?product=chat&menulabel=core%20sdk&platform=javascript), when calling the [on](https://trtc.io/document/47967?platform=javascript&product=chat&menulabel=sdk#d39fb50f-f0f2-4b67-9b15-acd7e8608105) interface to listen for events and the [off](https://trtc.io/document/47967?platform=javascript&product=chat&menulabel=sdk#c4cb09c5-142a-4d8c-8c03-ea7f446aa844) interface to unregister event listeners, the handler parameter should point to the same function. Recommended approach:
|
|
26
|
+
|
|
27
|
+
```typescript
|
|
28
|
+
// Recommended approach
|
|
29
|
+
tim.on(TencentCloudChat.EVENT.MESSAGE_RECEIVED, onMessageReceived, this);
|
|
30
|
+
tim.off(TencentCloudChat.EVENT.MESSAGE_RECEIVED, onMessageReceived);
|
|
31
|
+
|
|
32
|
+
// Note: The following code has a bug and cannot unregister TencentCloudChat.EVENT.MESSAGE_RECEIVED because bind() returns a new function each time
|
|
33
|
+
tim.on(TencentCloudChat.EVENT.MESSAGE_RECEIVED, this.onMessageReceived.bind(this));
|
|
34
|
+
tim.off(TencentCloudChat.EVENT.MESSAGE_RECEIVED, this.onMessageReceived.bind(this));
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
### Q: Does the SDK automatically unregister events that were registered via the on interface when logout is called?
|
|
38
|
+
**A:** No. To unregister event listeners, you must actively call the [off](https://trtc.io/document/47967?platform=javascript&product=chat&menulabel=sdk#c4cb09c5-142a-4d8c-8c03-ea7f446aa844) interface.
|
|
39
|
+
|
|
40
|
+
### Q: After successful login, I cannot send messages and receive a prompt about improper API call timing?
|
|
41
|
+
**A:** SDK APIs can only be called after the SDK is ready. Listen for the [TencentCloudChat.EVENT.SDK_READY](https://trtc.io/document/47967?product=chat&menulabel=core%20sdk&platform=javascript#b7ca8a5b-e020-4c43-a442-71125e55da2d) event and only call authenticated interfaces like sending messages after the SDK is ready.
|
|
42
|
+
|
|
43
|
+
### Q: I want to implement like and flower-sending features in an audio-video chatroom. How do I do this?
|
|
44
|
+
**A:** Use the [createCustomMessage](https://trtc.io/document/47993?product=chat&menulabel=core%20sdk&platform=javascript#creating-a-custom-message) and [sendMessage](https://trtc.io/document/47993?product=chat&menulabel=core%20sdk&platform=javascript#sending-a-message) interfaces to implement this.
|
|
45
|
+
|
|
46
|
+
### Q: How does Web IM SDK v2.x/v3.x/v4.x handle combined messages sent via REST API or legacy IM?
|
|
47
|
+
**A:** The content of combined messages is stored in the _elements property of the Message instance. You need to parse it yourself. Refer to [Message Format](https://trtc.io/document/47990?product=chat&menulabel=core%20sdk&platform=javascript) for parsing.
|
|
48
|
+
For non-combined messages, use the recommended approach: use the type and payload properties of the [Message](https://trtc.io/document/47990?product=chat&menulabel=core%20sdk&platform=javascript) instance.
|
|
49
|
+
|
|
50
|
+
### Q: Why don't I receive the TencentCloudChat.EVENT.MESSAGE_RECEIVED event after successfully sending a message via Web IM SDK's sendMessage?
|
|
51
|
+
**A:** Messages sent by yourself are not notified to the application through `TencentCloudChat.EVENT.MESSAGE_RECEIVED`. The [sendMessage](https://trtc.io/document/47993?product=chat&menulabel=core%20sdk&platform=javascript#sending-a-message) interface returns a `Promise`. Handle success or failure business logic through `Promise.then` or `Promise.catch`.
|
|
52
|
+
|
|
53
|
+
### Q: After merging messages retrieved via getMessageList with messages received through TencentCloudChat.EVENT.MESSAGE_RECEIVED event listener, I sometimes notice messages are out of order. Why?
|
|
54
|
+
**A:** When maintaining the conversation message list, ensure messages are enqueued in the correct order. If the message list is sorted from oldest to newest, historical messages retrieved via [getMessageList](https://trtc.io/document/47999?product=chat&menulabel=core%20sdk&platform=javascript) should be added to the head of the list, while real-time messages received via [TencentCloudChat.EVENT.MESSAGE_RECEIVED](https://trtc.io/document/47996?product=chat&menulabel=core%20sdk&platform=javascript) should be added to the tail.
|
|
55
|
+
|
|
56
|
+
### Q: After creating a live streaming group via the createGroup interface, I cannot receive messages?
|
|
57
|
+
**A:** For live streaming groups, you need to actively join the group to start the long-polling message channel. After creating a live streaming group using the [createGroup](https://trtc.io/document/48465?product=chat&menulabel=core%20sdk&platform=javascript#creating-a-group) interface, you must call the [joinGroup](https://trtc.io/document/48465?product=chat&menulabel=core%20sdk&platform=javascript#joining-a-group) interface to join the group before you can send and receive messages.
|
|
58
|
+
```typescript
|
|
59
|
+
let promise = tim.joinGroup({ groupID: 'group1' });
|
|
60
|
+
promise.then(function(imResponse) {
|
|
61
|
+
switch (imResponse.data.status) {
|
|
62
|
+
case TencentCloudChat.TYPES.JOIN_STATUS_WAIT_APPROVAL:
|
|
63
|
+
break;
|
|
64
|
+
case TencentCloudChat.TYPES.JOIN_STATUS_SUCCESS:
|
|
65
|
+
console.log(imResponse.data.group); // Joined group profile
|
|
66
|
+
break;
|
|
67
|
+
case TencentCloudChat.TYPES.JOIN_STATUS_ALREADY_IN_GROUP:
|
|
68
|
+
break;
|
|
69
|
+
default:
|
|
70
|
+
break;
|
|
71
|
+
}
|
|
72
|
+
}).catch(function(imError){
|
|
73
|
+
console.warn('joinGroup error:', imError);
|
|
74
|
+
});
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
### Q: Why don't live streaming groups have unread message counts? Why can't I retrieve message history?
|
|
78
|
+
**A:** By design: live streaming groups do not support unread message counts, and new members cannot view message history before joining. See [Group System](https://trtc.io/document/33529?product=chat&menulabel=core%20sdk&platform=javascript) for details. Ultimate or Enterprise editions support new members viewing message history before joining live streaming groups (SDK v2.16.0 or higher required).
|
|
79
|
+
|
|
80
|
+
### Q: Can I join two or more live streaming groups simultaneously?
|
|
81
|
+
**A:** No, a user can only join one live streaming group at a time. Joining multiple live streaming groups simultaneously would start multiple long-polling message channels, which can significantly impact web/H5 or mini-program performance.
|
|
82
|
+
|
|
83
|
+
### Q: How does the SDK implement message reactions?
|
|
84
|
+
**A:** The SDK supports message reaction capability. You need to purchase the Ultimate or Enterprise edition package. For API implementation, refer to the official documentation: https://trtc.io/document/60749?product=chat&menulabel=core%20sdk&platform=javascript.
|
|
85
|
+
|
|
86
|
+
### Q: How to mark one-to-one messages as read?
|
|
87
|
+
**A:** To mark one-to-one messages as read and clear the conversation unread count, use [setMessageRead](https://trtc.io/document/48319?product=chat&menulabel=core%20sdk&platform=javascript#clearing-the-conversation-unread-count).
|
|
88
|
+
|
|
89
|
+
### Q: How to clear unread count for group messages?
|
|
90
|
+
**A:** To clear the unread count for group conversations, use [setMessageRead](https://trtc.io/document/48319?product=chat&menulabel=core%20sdk&platform=javascript#clearing-the-conversation-unread-count).
|
|
91
|
+
|
|
92
|
+
### Q: How to implement single message read status for one-to-one and group messages?
|
|
93
|
+
**A:** To implement single message read status, use the message read receipt feature. For details on how to enable read receipts, send read receipts, etc., refer to: https://trtc.io/document/48021?product=chat&menulabel=core%20sdk&platform=javascript.
|
|
94
|
+
|
|
95
|
+
### Q: How to send image messages with Web SDK?
|
|
96
|
+
**A:** Use [createImageMessage](https://trtc.io/document/47993?product=chat&menulabel=core%20sdk&platform=javascript#creating-an-image-message) to create an image message instance, then use [sendMessage](https://trtc.io/document/47993?product=chat&menulabel=core%20sdk&platform=javascript#sending-a-message) to send the image message.
|
|
97
|
+
|
|
98
|
+
### Q: How to send video messages with Web SDK?
|
|
99
|
+
**A:** Use [createVideoMessage](https://trtc.io/document/47993?product=chat&menulabel=core%20sdk&platform=javascript#creating-a-video-message) to create a video message instance, then use [sendMessage](https://trtc.io/document/47993?product=chat&menulabel=core%20sdk&platform=javascript#sending-a-message) to send the video message.
|
|
100
|
+
|
|
101
|
+
### Q: How to send audio messages with Web SDK?
|
|
102
|
+
**A:** Use [createAudioMessage](https://trtc.io/document/47993?product=chat&menulabel=core%20sdk&platform=javascript#creating-an-audio-message) to create an audio message instance, then use [sendMessage](https://trtc.io/document/47993?product=chat&menulabel=core%20sdk&platform=javascript#sending-a-message) to send the audio message.
|
|
103
|
+
|
|
104
|
+
### Q: How to send file messages with Web SDK?
|
|
105
|
+
**A:** Use [createFileMessage](https://trtc.io/document/47993?product=chat&menulabel=core%20sdk&platform=javascript#creating-a-file-message) to create a file message instance, then use [sendMessage](https://trtc.io/document/47993?product=chat&menulabel=core%20sdk&platform=javascript#sending-a-message) to send the file message.
|
|
@@ -0,0 +1,120 @@
|
|
|
1
|
+
### Does TUIKit source code support Androidx?
|
|
2
|
+
|
|
3
|
+
Yes.
|
|
4
|
+
|
|
5
|
+
### Why do I encounter a 6012 error or "TLSSDK exchange ticket fail" upon login?
|
|
6
|
+
- The initialization API and the login API must be called separately and cannot be called successively because there are asynchronous operations in the initialization method.
|
|
7
|
+
|
|
8
|
+
- If you are using Chat Free edition and upgrade to Chat Pro Edition, after the upgrade, you can configure your SDKAppID in the console to ensure proper login. For pricing details, see [Pricing](https://intl.cloud.tencent.com/document/product/1047/34350).
|
|
9
|
+
|
|
10
|
+
|
|
11
|
+
### Why do I encounter a 6013 "SDK Not Initialized" error?
|
|
12
|
+
|
|
13
|
+
If the 6013 "SDK Not Initialized" error occurs, try the following troubleshooting methods:
|
|
14
|
+
1. Check whether you performed other operations such as receiving and sending messages before logging in successfully.
|
|
15
|
+
|
|
16
|
+
2. Check whether you were forced offline when logging in by an account already logged in on another device. By default, the Chat SDK allows one account to log in on one device at a time. For more information, see [Multi-Device Login](https://intl.cloud.tencent.com/document/product/1047/33518).
|
|
17
|
+
|
|
18
|
+
3. For Android, verify that all library files have been loaded or repossessed by the system during use.
|
|
19
|
+
|
|
20
|
+
|
|
21
|
+
### Why do I encounter "code: 6205 desc: QALSERVICE not ready" error?
|
|
22
|
+
|
|
23
|
+
This error is caused by calling `stopQALService` after initialization. To fix it, refer to the [configuration method](https://blog.csdn.net/qq_16131393/article/details/54895733) shared by one of our customers.
|
|
24
|
+
|
|
25
|
+
### Why do not emojis appear or appear as gibberish in messages?
|
|
26
|
+
|
|
27
|
+
Chat does not provide emoji packs. You must align the actual parsing by yourself.
|
|
28
|
+
|
|
29
|
+
There are two ways to use emojis:
|
|
30
|
+
- Use index in TIMFaceElem to identify the index of the emojis. For example, an Android device and an iOS device have the same set of emojis and index 2 represents the smile emoji. When index=2, both devices send and receive the same indexed emoji.
|
|
31
|
+
|
|
32
|
+
- Use data in TIMFaceElem. For example, the names of emoji images are string-type. Use the word "smile" to represent the smile emoji, and store "smile" in data. Then, both iOS and Android devices use data as the key to retrieve and display the corresponding emoji.
|
|
33
|
+
|
|
34
|
+
|
|
35
|
+
You can also use the two fields at the same time. For example, use data to specify the emoji set and index to indicate the specific index in this emoji set. This way, you can implement many different emoji effects as in QQ. It is possible to store more complex data structures in data as long as the devices follow the same parsing rules.
|
|
36
|
+
|
|
37
|
+
|
|
38
|
+
### Why do I encounter error 10002 during operations?
|
|
39
|
+
|
|
40
|
+
This status code is returned when a network exception, timeout, or ticket switching failure occurs during server-side authentication. If you see this status code, wait a moment and try again.
|
|
41
|
+
|
|
42
|
+
### Why do I encounter error 6200 or 6201 when receiving or sending messages?
|
|
43
|
+
|
|
44
|
+
This status code is returned when the client is offline, times out, or is disconnected. Error 6200 is defined as no network connection during request sending, whereas error 6201 is defined as no network connection during response sending. When you encounter this status code, check the network condition or wait for the network to restore and try again.
|
|
45
|
+
|
|
46
|
+
### Why do I encounter error 20003 when receiving and sending messages?
|
|
47
|
+
|
|
48
|
+
This error code is returned when UserID is invalid or UserID has not been imported to Chat. To fix it, check whether UserID has been imported to Tencent Cloud.
|
|
49
|
+
|
|
50
|
+
### Why do I encounter error 6010 when playing audio messages?
|
|
51
|
+
|
|
52
|
+
This error code is returned when audio messages that are no longer retained by the roaming server are requested. To fix it, you can [increase the message roaming duration](https://intl.cloud.tencent.com/document/product/1047/34419) or download audio files to local storage and play them. However, expired files cannot be restored. Different SDK versions allow you to increase the retention duration for different message types. For more information, see [Message Storage](https://intl.cloud.tencent.com/document/product/1047/33524).
|
|
53
|
+
|
|
54
|
+
### Why do I encounter errors 70001, 70003, 70009, and 70013 during account authentication?
|
|
55
|
+
|
|
56
|
+
These errors occur because UserID and UserSig do not match. To fix it, check the validity of UserID and UserSig. Among them, error 70001 means UserSig has expired, error 70003 means a verification failure due to a truncated UserSig, error 70009 means UserSig verification failed (possibly due to mixing the keys or private keys of other SDKAppIDs when generating UserSig), and error 70013 means UserID does not match.
|
|
57
|
+
|
|
58
|
+
### Why do I encounter the error code -2 or -5 when the web client app is using the Chat SDK?
|
|
59
|
+
- -2: Indicates that a web app request to the server failed, usually due to network problems. Web apps send requests to the server by using the HTTP Long Polling method, and this status code is returned when a network problem occurs. To fix it, check your network or try again.
|
|
60
|
+
|
|
61
|
+
- -5: When the login attempt is not completed and the SDK has not received the a2key and tinyID returned by the server, directly calling other APIs returns the "tinyid or a2 is empty" error message and -5 error code.
|
|
62
|
+
|
|
63
|
+
|
|
64
|
+
### What should I do when the SDK on the armeabi platform reports "java.lang.UnsatisfiedLinkError: No implementation found for"?
|
|
65
|
+
|
|
66
|
+
Copy jni/armeabi-v7a/libImSDK.so in the Chat SDK’s aar file to the src/main/jniLibs/armeabi directory in your source code project and load it in build.gradle.
|
|
67
|
+
|
|
68
|
+
### How can I resolve x86_64 and i386 architecture errors when the app has been launched in App Store?
|
|
69
|
+
|
|
70
|
+
This error occurs because App Store does not support the x86_64 and i386 architecture. The solution is as follows:
|
|
71
|
+
1. Clear the project compilation cache:
|
|
72
|
+
Select **Product** > **clean**, press Alt until "clean build Folder..." appears and wait for the operation to complete.
|
|
73
|
+
|
|
74
|
+
2. Remove the x86_64 and i386 architecture not supported by App Store:
|
|
75
|
+
a. Select **TARGETS** > **Build Phases**.
|
|
76
|
+
b. Click the plus sign and select **New Run Script Phase**.
|
|
77
|
+
c. Add the following code:
|
|
78
|
+
|
|
79
|
+
``` bash
|
|
80
|
+
APP_PATH="${TARGET_BUILD_DIR}/${WRAPPER_NAME}"
|
|
81
|
+
|
|
82
|
+
# This script loops through the frameworks embedded in the application and
|
|
83
|
+
|
|
84
|
+
# removes unused architectures.
|
|
85
|
+
|
|
86
|
+
find "$APP_PATH" -name '*.framework' -type d | while read -r FRAMEWORK
|
|
87
|
+
do
|
|
88
|
+
FRAMEWORK_EXECUTABLE_NAME=$(defaults read "$FRAMEWORK/Info.plist" CFBundleExecutable)
|
|
89
|
+
FRAMEWORK_EXECUTABLE_PATH="$FRAMEWORK/$FRAMEWORK_EXECUTABLE_NAME"
|
|
90
|
+
echo "Executable is $FRAMEWORK_EXECUTABLE_PATH"
|
|
91
|
+
|
|
92
|
+
EXTRACTED_ARCHS=()
|
|
93
|
+
|
|
94
|
+
for ARCH in $ARCHS
|
|
95
|
+
do
|
|
96
|
+
echo "Extracting $ARCH from $FRAMEWORK_EXECUTABLE_NAME"
|
|
97
|
+
lipo -extract "$ARCH" "$FRAMEWORK_EXECUTABLE_PATH" -o "$FRAMEWORK_EXECUTABLE_PATH-$ARCH"
|
|
98
|
+
EXTRACTED_ARCHS+=("$FRAMEWORK_EXECUTABLE_PATH-$ARCH")
|
|
99
|
+
done
|
|
100
|
+
|
|
101
|
+
echo "Merging extracted architectures: ${ARCHS}"
|
|
102
|
+
lipo -o "$FRAMEWORK_EXECUTABLE_PATH-merged" -create "${EXTRACTED_ARCHS[@]}"
|
|
103
|
+
rm "${EXTRACTED_ARCHS[@]}"
|
|
104
|
+
|
|
105
|
+
echo "Replacing original executable with thinned version"
|
|
106
|
+
rm "$FRAMEWORK_EXECUTABLE_PATH"
|
|
107
|
+
mv "$FRAMEWORK_EXECUTABLE_PATH-merged" "$FRAMEWORK_EXECUTABLE_PATH"
|
|
108
|
+
|
|
109
|
+
done
|
|
110
|
+
```
|
|
111
|
+

|
|
112
|
+
|
|
113
|
+
3. Package the app and upload it again.
|
|
114
|
+
|
|
115
|
+
|
|
116
|
+
### Can developers directly utilize the emoticon packs demonstrated in the Chat various client demos/TUIKit projects?
|
|
117
|
+
|
|
118
|
+
To respect the copyright of emoji designs, the Chat Demo/TUIKit project does not include cutouts of large emoji elements. Please replace them with your own designs or other emoji packs for which you hold the copyright before officially launching for commercial use. **The default smiley face emoji pack shown below is copyrighted by Tencent RTC** and is available for licensed use for a fee. If you need to obtain a license, please [contact us](https://trtc.io/contact).
|
|
119
|
+
|
|
120
|
+

|
|
@@ -0,0 +1,120 @@
|
|
|
1
|
+
### Does TUIKit source code support Androidx?
|
|
2
|
+
|
|
3
|
+
Yes.
|
|
4
|
+
|
|
5
|
+
### Why do I encounter a 6012 error or "TLSSDK exchange ticket fail" upon login?
|
|
6
|
+
- The initialization API and the login API must be called separately and cannot be called successively because there are asynchronous operations in the initialization method.
|
|
7
|
+
|
|
8
|
+
- If you are using Chat Free edition and upgrade to Chat Pro Edition, after the upgrade, you can configure your SDKAppID in the console to ensure proper login. For pricing details, see [Pricing](https://intl.cloud.tencent.com/document/product/1047/34350).
|
|
9
|
+
|
|
10
|
+
|
|
11
|
+
### Why do I encounter a 6013 "SDK Not Initialized" error?
|
|
12
|
+
|
|
13
|
+
If the 6013 "SDK Not Initialized" error occurs, try the following troubleshooting methods:
|
|
14
|
+
1. Check whether you performed other operations such as receiving and sending messages before logging in successfully.
|
|
15
|
+
|
|
16
|
+
2. Check whether you were forced offline when logging in by an account already logged in on another device. By default, the Chat SDK allows one account to log in on one device at a time. For more information, see [Multi-Device Login](https://intl.cloud.tencent.com/document/product/1047/33518).
|
|
17
|
+
|
|
18
|
+
3. For Android, verify that all library files have been loaded or repossessed by the system during use.
|
|
19
|
+
|
|
20
|
+
|
|
21
|
+
### Why do I encounter "code: 6205 desc: QALSERVICE not ready" error?
|
|
22
|
+
|
|
23
|
+
This error is caused by calling `stopQALService` after initialization. To fix it, refer to the [configuration method](https://blog.csdn.net/qq_16131393/article/details/54895733) shared by one of our customers.
|
|
24
|
+
|
|
25
|
+
### Why do not emojis appear or appear as gibberish in messages?
|
|
26
|
+
|
|
27
|
+
Chat does not provide emoji packs. You must align the actual parsing by yourself.
|
|
28
|
+
|
|
29
|
+
There are two ways to use emojis:
|
|
30
|
+
- Use index in TIMFaceElem to identify the index of the emojis. For example, an Android device and an iOS device have the same set of emojis and index 2 represents the smile emoji. When index=2, both devices send and receive the same indexed emoji.
|
|
31
|
+
|
|
32
|
+
- Use data in TIMFaceElem. For example, the names of emoji images are string-type. Use the word "smile" to represent the smile emoji, and store "smile" in data. Then, both iOS and Android devices use data as the key to retrieve and display the corresponding emoji.
|
|
33
|
+
|
|
34
|
+
|
|
35
|
+
You can also use the two fields at the same time. For example, use data to specify the emoji set and index to indicate the specific index in this emoji set. This way, you can implement many different emoji effects as in QQ. It is possible to store more complex data structures in data as long as the devices follow the same parsing rules.
|
|
36
|
+
|
|
37
|
+
|
|
38
|
+
### Why do I encounter error 10002 during operations?
|
|
39
|
+
|
|
40
|
+
This status code is returned when a network exception, timeout, or ticket switching failure occurs during server-side authentication. If you see this status code, wait a moment and try again.
|
|
41
|
+
|
|
42
|
+
### Why do I encounter error 6200 or 6201 when receiving or sending messages?
|
|
43
|
+
|
|
44
|
+
This status code is returned when the client is offline, times out, or is disconnected. Error 6200 is defined as no network connection during request sending, whereas error 6201 is defined as no network connection during response sending. When you encounter this status code, check the network condition or wait for the network to restore and try again.
|
|
45
|
+
|
|
46
|
+
### Why do I encounter error 20003 when receiving and sending messages?
|
|
47
|
+
|
|
48
|
+
This error code is returned when UserID is invalid or UserID has not been imported to Chat. To fix it, check whether UserID has been imported to Tencent Cloud.
|
|
49
|
+
|
|
50
|
+
### Why do I encounter error 6010 when playing audio messages?
|
|
51
|
+
|
|
52
|
+
This error code is returned when audio messages that are no longer retained by the roaming server are requested. To fix it, you can [increase the message roaming duration](https://intl.cloud.tencent.com/document/product/1047/34419) or download audio files to local storage and play them. However, expired files cannot be restored. Different SDK versions allow you to increase the retention duration for different message types. For more information, see [Message Storage](https://intl.cloud.tencent.com/document/product/1047/33524).
|
|
53
|
+
|
|
54
|
+
### Why do I encounter errors 70001, 70003, 70009, and 70013 during account authentication?
|
|
55
|
+
|
|
56
|
+
These errors occur because UserID and UserSig do not match. To fix it, check the validity of UserID and UserSig. Among them, error 70001 means UserSig has expired, error 70003 means a verification failure due to a truncated UserSig, error 70009 means UserSig verification failed (possibly due to mixing the keys or private keys of other SDKAppIDs when generating UserSig), and error 70013 means UserID does not match.
|
|
57
|
+
|
|
58
|
+
### Why do I encounter the error code -2 or -5 when the web client app is using the Chat SDK?
|
|
59
|
+
- -2: Indicates that a web app request to the server failed, usually due to network problems. Web apps send requests to the server by using the HTTP Long Polling method, and this status code is returned when a network problem occurs. To fix it, check your network or try again.
|
|
60
|
+
|
|
61
|
+
- -5: When the login attempt is not completed and the SDK has not received the a2key and tinyID returned by the server, directly calling other APIs returns the "tinyid or a2 is empty" error message and -5 error code.
|
|
62
|
+
|
|
63
|
+
|
|
64
|
+
### What should I do when the SDK on the armeabi platform reports "java.lang.UnsatisfiedLinkError: No implementation found for"?
|
|
65
|
+
|
|
66
|
+
Copy jni/armeabi-v7a/libImSDK.so in the Chat SDK’s aar file to the src/main/jniLibs/armeabi directory in your source code project and load it in build.gradle.
|
|
67
|
+
|
|
68
|
+
### How can I resolve x86_64 and i386 architecture errors when the app has been launched in App Store?
|
|
69
|
+
|
|
70
|
+
This error occurs because App Store does not support the x86_64 and i386 architecture. The solution is as follows:
|
|
71
|
+
1. Clear the project compilation cache:
|
|
72
|
+
Select **Product** > **clean**, press Alt until "clean build Folder..." appears and wait for the operation to complete.
|
|
73
|
+
|
|
74
|
+
2. Remove the x86_64 and i386 architecture not supported by App Store:
|
|
75
|
+
a. Select **TARGETS** > **Build Phases**.
|
|
76
|
+
b. Click the plus sign and select **New Run Script Phase**.
|
|
77
|
+
c. Add the following code:
|
|
78
|
+
|
|
79
|
+
``` bash
|
|
80
|
+
APP_PATH="${TARGET_BUILD_DIR}/${WRAPPER_NAME}"
|
|
81
|
+
|
|
82
|
+
# This script loops through the frameworks embedded in the application and
|
|
83
|
+
|
|
84
|
+
# removes unused architectures.
|
|
85
|
+
|
|
86
|
+
find "$APP_PATH" -name '*.framework' -type d | while read -r FRAMEWORK
|
|
87
|
+
do
|
|
88
|
+
FRAMEWORK_EXECUTABLE_NAME=$(defaults read "$FRAMEWORK/Info.plist" CFBundleExecutable)
|
|
89
|
+
FRAMEWORK_EXECUTABLE_PATH="$FRAMEWORK/$FRAMEWORK_EXECUTABLE_NAME"
|
|
90
|
+
echo "Executable is $FRAMEWORK_EXECUTABLE_PATH"
|
|
91
|
+
|
|
92
|
+
EXTRACTED_ARCHS=()
|
|
93
|
+
|
|
94
|
+
for ARCH in $ARCHS
|
|
95
|
+
do
|
|
96
|
+
echo "Extracting $ARCH from $FRAMEWORK_EXECUTABLE_NAME"
|
|
97
|
+
lipo -extract "$ARCH" "$FRAMEWORK_EXECUTABLE_PATH" -o "$FRAMEWORK_EXECUTABLE_PATH-$ARCH"
|
|
98
|
+
EXTRACTED_ARCHS+=("$FRAMEWORK_EXECUTABLE_PATH-$ARCH")
|
|
99
|
+
done
|
|
100
|
+
|
|
101
|
+
echo "Merging extracted architectures: ${ARCHS}"
|
|
102
|
+
lipo -o "$FRAMEWORK_EXECUTABLE_PATH-merged" -create "${EXTRACTED_ARCHS[@]}"
|
|
103
|
+
rm "${EXTRACTED_ARCHS[@]}"
|
|
104
|
+
|
|
105
|
+
echo "Replacing original executable with thinned version"
|
|
106
|
+
rm "$FRAMEWORK_EXECUTABLE_PATH"
|
|
107
|
+
mv "$FRAMEWORK_EXECUTABLE_PATH-merged" "$FRAMEWORK_EXECUTABLE_PATH"
|
|
108
|
+
|
|
109
|
+
done
|
|
110
|
+
```
|
|
111
|
+

|
|
112
|
+
|
|
113
|
+
3. Package the app and upload it again.
|
|
114
|
+
|
|
115
|
+
|
|
116
|
+
### Can developers directly utilize the emoticon packs demonstrated in the Chat various client demos/TUIKit projects?
|
|
117
|
+
|
|
118
|
+
To respect the copyright of emoji designs, the Chat Demo/TUIKit project does not include cutouts of large emoji elements. Please replace them with your own designs or other emoji packs for which you hold the copyright before officially launching for commercial use. **The default smiley face emoji pack shown below is copyrighted by Tencent RTC** and is available for licensed use for a fee. If you need to obtain a license, please [contact us](https://trtc.io/contact).
|
|
119
|
+
|
|
120
|
+

|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
---
|
|
2
|
+
product: 'Chat'
|
|
3
|
+
tech_stack: 'web_js_sdk'
|
|
4
|
+
framework: 'react'
|
|
5
|
+
title: 'React UIKit Integration and Frequently Asked Questions'
|
|
6
|
+
keywords: ['react', 'initialization', 'components', 'integration', 'TUIKit']
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# React TUIKit Integration and FAQ
|
|
10
|
+
|
|
11
|
+
## Module 1: Environment Setup and Quick Initialization (Topic: Setup)
|
|
12
|
+
|
|
13
|
+
### Q: How do I install TUIKit in a React project?
|
|
14
|
+
|
|
15
|
+
**A:** TUIKit is built on top of the Web SDK. You need to install `@tencentcloud/chat-uikit-react`
|
|
16
|
+
|
|
17
|
+
```bash
|
|
18
|
+
# Install TUIKit React version
|
|
19
|
+
npm install @tencentcloud/chat-uikit-react@latest
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
## Module 2: Frequently Asked Questions (Topic: Question)
|
|
23
|
+
|
|
24
|
+
### Q: Does TUIKit support React 17/19 versions?
|
|
25
|
+
|
|
26
|
+
**A:** Currently, React versions 17.x and 19.x are not supported. Only React v18 is supported.
|
|
@@ -0,0 +1,36 @@
|
|
|
1
|
+
---
|
|
2
|
+
product: 'Chat'
|
|
3
|
+
tech_stack: 'web_js_sdk'
|
|
4
|
+
framework: 'vue'
|
|
5
|
+
title: 'Vue TUIKit Integration and FAQ Solutions'
|
|
6
|
+
keywords: ['vue', 'Initialization', 'Component', 'Integration', 'TUIKit']
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
Vue TUIKit Integration and Common Problem Solutions (FAQ)
|
|
10
|
+
|
|
11
|
+
Module 1: Environment Setup and Quick Initialization (Topic: Setup)
|
|
12
|
+
|
|
13
|
+
Q: How to install TUIKit in a Vue project?
|
|
14
|
+
|
|
15
|
+
A: TUIKit is developed based on the Web SDK. You need to install @tencentcloud/chat-uikit-vue3.
|
|
16
|
+
|
|
17
|
+
```bash
|
|
18
|
+
# Install TUIKit Vue version
|
|
19
|
+
npm install @tencentcloud/chat-uikit-vue3@latest
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
Module 2: Common Problem Solutions (Topic: Question)
|
|
23
|
+
|
|
24
|
+
Q: Can I use third-party component libraries, such as Element-Plus, within TUIKit?
|
|
25
|
+
|
|
26
|
+
A: Glue code between the core components can use other component libraries, which can be seen in the example code. For instance, you can encapsulate <ChatSetting /> into a full-screen drawer component. However, components already existing inside the core components are not supported for modification at this time.
|
|
27
|
+
```typescript
|
|
28
|
+
const isChatSettingShow = ref(false);
|
|
29
|
+
<el-drawer
|
|
30
|
+
v-model="isChatSettingShow"
|
|
31
|
+
title="Settings"
|
|
32
|
+
>
|
|
33
|
+
<ChatSetting />
|
|
34
|
+
</el-drawer>
|
|
35
|
+
|
|
36
|
+
```
|
|
@@ -0,0 +1,88 @@
|
|
|
1
|
+
---
|
|
2
|
+
product: 'Live'
|
|
3
|
+
tech_stack: 'liveKit'
|
|
4
|
+
framework: 'common'
|
|
5
|
+
title: 'LiveKit Error Code Reference'
|
|
6
|
+
keywords: ['error code', 'error', 'live', 'liveKit', 'live room error', 'pk error', 'co-hosting error']
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# LiveKit Error Code Reference
|
|
10
|
+
|
|
11
|
+
## LiveKit Error Codes (Topic: LiveKit Error Code)
|
|
12
|
+
|
|
13
|
+
## Error Code 100002
|
|
14
|
+
**Cause:** Possible reasons include:
|
|
15
|
+
- Your current package does not support live streaming, possibly due to package expiration or not being activated.
|
|
16
|
+
- Live room name cannot exceed 100 bytes. One Chinese character occupies 2 bytes.
|
|
17
|
+
- Live room ID cannot exceed 48 characters.
|
|
18
|
+
- Live room ID can only contain letters, numbers, and underscores.
|
|
19
|
+
- Only live-type rooms support this interface.
|
|
20
|
+
- Current layout template does not need to be changed.
|
|
21
|
+
- PK request duration exceeded the maximum limit (default is 5 minutes).
|
|
22
|
+
**Solution:**
|
|
23
|
+
- Check your package. For first-time use, you can [activate the trial version](https://trtc.io/document/60033?product=live&menulabel=uikit&platform=web) or visit the [Tencent Cloud Console](https://console.trtc.io/subscription/buy/live) to purchase or upgrade your package.
|
|
24
|
+
- Verify that the live room name and live room ID meet requirements, and confirm that the room type is live.
|
|
25
|
+
- Check the layout template parameters to confirm if layout changes are needed.
|
|
26
|
+
- Check the PK request duration and reduce the PK time.
|
|
27
|
+
|
|
28
|
+
## Error Code 70001
|
|
29
|
+
**Cause:** User signature has expired.
|
|
30
|
+
**Solution:** It is recommended to set the signature validity period to no less than 24 hours. Refer to [Generate UserSig (User Authentication)](https://trtc.io/document/35166?product=live&menulabel=uikit&platform=web).
|
|
31
|
+
|
|
32
|
+
## Error Code 70003
|
|
33
|
+
**Cause:** Invalid user signature.
|
|
34
|
+
**Solution:** Regenerate the signature. Refer to [Generate UserSig (User Authentication)](https://trtc.io/document/35166?product=live&menulabel=uikit&platform=web).
|
|
35
|
+
|
|
36
|
+
## Error Code 70013
|
|
37
|
+
**Cause:** User ID does not match the user signature.
|
|
38
|
+
**Solution:** Please verify that the user ID matches the user signature. You can verify the signature at the [Tencent Cloud Console](https://console.trtc.io/usersig).
|
|
39
|
+
|
|
40
|
+
## Error Code 100004
|
|
41
|
+
**Cause:** Room does not exist.
|
|
42
|
+
**Solution:** Please verify that the room ID being used is correct.
|
|
43
|
+
|
|
44
|
+
## Error Code 100006
|
|
45
|
+
**Cause:** No operation permission.
|
|
46
|
+
**Solution:** Please check if the current role has the required permission.
|
|
47
|
+
|
|
48
|
+
## Error Code 100007
|
|
49
|
+
**Cause:** Possible reasons include:
|
|
50
|
+
- No package purchased or account is in arrears.
|
|
51
|
+
- Cross-room co-hosting feature is not available between live rooms.
|
|
52
|
+
- PK feature is not available between live rooms.
|
|
53
|
+
**Solution:**
|
|
54
|
+
- For package issues, visit the [Tencent Cloud Console](https://console.trtc.io/subscription/buy/live) to purchase. For first-time use, you can [activate the trial version](https://trtc.io/document/60033?product=live&menulabel=uikit&platform=web).
|
|
55
|
+
- For cross-room co-hosting unavailability, visit the [Tencent Cloud Console](https://console.trtc.io/subscription/buy/live) to purchase or upgrade your package.
|
|
56
|
+
- For PK feature unavailability, visit the [Tencent Cloud Console](https://console.trtc.io/subscription/buy/live) to purchase or upgrade your package.
|
|
57
|
+
|
|
58
|
+
## Error Code 100012
|
|
59
|
+
**Cause:** Request too frequent.
|
|
60
|
+
**Solution:** Requests are too frequent, please try again later.
|
|
61
|
+
|
|
62
|
+
## Error Code 100203
|
|
63
|
+
**Cause:** You are already on the microphone seat.
|
|
64
|
+
**Solution:** Please check if the current user is already on the microphone seat.
|
|
65
|
+
|
|
66
|
+
## Error Code 100206
|
|
67
|
+
**Cause:** User is not on the microphone seat.
|
|
68
|
+
**Solution:** Please check if the user is on the microphone seat.
|
|
69
|
+
|
|
70
|
+
## Error Code 100400
|
|
71
|
+
**Cause:** Current room has not enabled live room co-hosting.
|
|
72
|
+
**Solution:** Please enable live room co-hosting before performing this operation.
|
|
73
|
+
|
|
74
|
+
## Error Code 100418
|
|
75
|
+
**Cause:** Current room has not started PK yet.
|
|
76
|
+
**Solution:** Please start PK in the current room before performing this operation.
|
|
77
|
+
|
|
78
|
+
## Error Code 100419
|
|
79
|
+
**Cause:** Current room is currently in PK.
|
|
80
|
+
**Solution:** The current room is in PK mode and cannot perform this operation. Please try again later.
|
|
81
|
+
|
|
82
|
+
## Error Code 100421
|
|
83
|
+
**Cause:** Current room PK has ended.
|
|
84
|
+
**Solution:** The current room PK has ended and cannot perform this operation. Please try again later.
|
|
85
|
+
|
|
86
|
+
## Error Code 101011
|
|
87
|
+
**Cause:** Current room has reached the package participant limit.
|
|
88
|
+
**Solution:** Visit the [Tencent Cloud Console](https://console.trtc.io/subscription/buy/live) to purchase or upgrade your package.
|
|
File without changes
|