@tencent-rtc/mcp 1.4.7 → 1.6.0-beta.1

package/resource/knowledge/callkit/faq/android.md

@@ -0,0 +1,92 @@
+### The error message "The package you purchased does not support this ability"?
+
+If you encounter the above error message, it is because the audio and video call capability package of your current application has expired or has not been activated. You can refer to the service activation guide to claim or activate the audio and video call capability, and then continue to use the TUICallKit component.
+
+### When the application is offline, Will it can pop up the call view?
+
+During a one-to-one call, if you come online within the timeout period, an incoming call view will be triggered;  For group calls, if you come online within the timeout period, the last 20 unprocessed group messages will be pulled up, and if a call invitation exists, it will trigger an incoming call. The display strategy for incoming calls see: Incoming call display policy for the callee.
+
+### When the application is in the background, Will it can pop up the call view?
+1. TUICallKit has two different display policy for the callee, see below: Incoming call display policy for the callee.
+
+2. Before version 2.3 of TUICallKit, to automatically bring the application from the background to the foreground, it was necessary to check whether the app had enabled the "Background self-start" or "Floating window" permission.
+
+   Different manufacturers, or even the same manufacturer with different Android versions, offer varying permissions and permission names for applications. For instance, Xiaomi 6 requires only the "Background pop-ups" permissions , while Redmi needs both the "Background pop-ups"  and "Display over other applications" permissions.
+
+   How to enable permissions, see below: Relevant permissions enabled.
+
+3. If you encounter the following scenarios where the call interface cannot be pulled up, the reason is that changes in the application's launch stack caused the CallKitActivity interface to be obscured or removed.
+
+   Scenario One: After accept call, if app goes to the background and then click the desktop icon to enter foreground, the CallKitActivity disappears.
+
+   Scenario Two: If the app is in the background and when you receive a IncomingNotificationView then click the desktop icon to enter the app, the CallKitActivity didn't show and the IncomingNotificationView disappears.
+
+   Scenario Three: When the app is in the background and an offline push notification is received, not clicking the push notification but entering the app via the desktop icon will either fail to bring up the CallKitActivity or cause the CallKitActivityto flash momentarily.
+
+   In the above scenarios, you need to add the following code to the default Activity of your app. Each app's default Activity may differ. Refer to the AndroidManifest.xml configuration for more details. Taking the launch page SplashActivity for most applications as an example:
+
+【Code】
+``` java
+if (!isTaskRoot() && getIntent() != null && getIntent().hasCategory(Intent.CATEGORY_LAUNCHER)
+        && Intent.ACTION_MAIN.equals(getIntent().getAction())) {
+    finish();
+    return;
+}
+```
+
+【Location】
+
+### Incoming call display policy for the callee
+
+To make TUICallKit adaptable to different business needs, add product features, and improve user experience, TUICallKit **version 2.3 and above** (Release Log) optimized the call page display pop-up strategy after receiving a call, as detailed below:
+
+|Full screen display of incoming call|Banner display of incoming call|
+|---------|---------|
+|||
+
+1. If you want the callee to pull up the full-screen call view when receiving a call, you can integrate the [tuicallkit-kt](https://github.com/Tencent-RTC/TUICallKit/tree/main/Android/tuicallkit-kt) code. By default, the incoming call display strategy for the callee is as follows:
+
+2. If you prefer to show a banner when receiving a call and then pull up the full-screen  as needed, you can enable this feature by calling the following interface.
+
+   ``` java
+     TUICallKit.createInstance(context).enableIncomingBanner(true);
+   ```
+
+   Once enabled, the callee's incoming call strategy is as shown below, as long as the **floating window permission** is enabled, the call banner will be displayed as much as possible.
+
+   > **Note:**
+   >
+
+   > For information on how to enable related permissions, see below: Relevant permissions enabled.
+   >
+
+   > If the incoming call interface doesn't display according to the above strategy, please filter the `onCallReceived` log to check if a call invitation was received.
+   >
+
+### **Relevant permissions enabled**
+
+To ensure a good calling experience, it is recommended to enable "notification" permissions, "Display over other apps(Floating window)" and "Background pop-ups" permissions in your application. The specific methods are as follows:
+
+【Manually Enabled】
+
+After the application is installed, you can long-press the application Icon, select "Application Information", then enable "notification" permission, "Display over other applications" and "Background pop-ups" permissions. Alternatively, you can go to `Mobile Phone > System Settings > Application Management > Application` to manually enable these permissions.
+
+|Pixel 4a|VIVO|
+|---------|---------|
+|||
+
+【Code guidance】
+- **Notification permissions**: For showcasing push notifications: please refer to [Notification runtime permissions](https://developer.android.com/develop/ui/views/notifications/notification-permission) and [Request runtime permissions](https://developer.android.com/training/permissions/requesting#request-permission) and implement according to business needs.
+
+- **Floating window permission**: Used for displaying custom incoming call notifications and call floating windows.
+
+- **Background pop-ups:** Used to pop up the interface when the application is in the background (for example: on a VIVO phone).
+
+``` java
+fun requestPermission(context: Context?) {
+    //In TUICallKit,Please open both OverlayWindows and Background pop-ups permission.
+    PermissionRequester.newInstance(
+         PermissionRequester.FLOAT_PERMISSION, PermissionRequester.BG_START_PERMISSION)
+        .request()
+}
+```

package/resource/{doc/callkit/faq/android-faq.md → knowledge/callkit/faq/common.md}

@@ -1,24 +1,24 @@
-### 1. Error message `[-100035]The package you purchased does not support this ability. Please purchase the package` appears during voice or video call？
+### Error message `[-100035]The package you purchased does not support this ability. Please purchase the package` appears during voice or video call？
 
 To make voice or video calls, you need to subscribe to our Call Monthly Package. You can try it for free for 7 days. For more information on how to activate the service, please refer to: [Activate Service (TUICallKit)](https://www.tencentcloud.com/document/product/647/59832).
 
-### 2. Invalid or non-existent UserID of message sender or receiver？
+### Invalid or non-existent UserID of message sender or receiver？
 
 If the user you are calling has not logged in, the call will fail. Please try calling a user who has successfully logged in.
 
-### 3. Error: inviteID is invalid or the invitation has been processed？
+### Error: inviteID is invalid or the invitation has been processed？
 
 The inviteID may be invalid if it has been cancelled by the caller or if the invitation has already been accepted. In some cases, network bandwidth may also affect signaling, causing inviteID invalid errors.
 
-### **4. How to get the call room number RoomId?**
+### **How to get the call room number RoomId?**
 
 After the call is connected, you can obtain the call room number (RoomId) through the [onCallBegin](https://www.tencentcloud.com/document/product/647/51007#onCallBegin) return roomid field.
 
-### 5. Can TUICallKit be used without importing the Chat SDK?
+### Encounter error code "-3301" with the message "Services are not available in your region" after entering the room
 
-**No**, all components of TUIKit use Tencent Cloud Chat SDK as the communication base service, including call signaling, busy line signaling, and other core logic. If you have already purchased another Chat product, you can also refer to the TUICallKit logic for adaptation.
+If you receive this error code, [contact us](https://trtc.io/contact) for support.
 
-### 6. in the TUIChat + TUICallKit Integrated Scenarios, after Upgrading the TUICallKit Version, New Version Calls Old Version and Old Version Is Unable to Receive Call Issues
+### In the TUIChat + TUICallKit Integrated Scenarios, after Upgrading the TUICallKit Version, New Version Calls Old Version and Old Version Is Unable to Receive Call Issues
 
 Starting from TUICallKit version 3.1, in the TUIChat + TUICallKit integrated scenarios, initiating a call through the call button in TUIChat by default uses the new calls API. Therefore, if your business has already gone live, you can use the advanced API to switch the call interface to call or groupCall to maintain interconnectivity with users of the online edition.
 
@@ -104,12 +104,11 @@ TUICallKitServer.getTUICallEngineInstance().callExperimentalAPI(JSON.stringfy(js
 
 ###
 
-### 7.How to get the log files of each platform?
+### How to get the log files of each platform?
 
 The current log file paths of each platform are as follows:
+- iOS or Mac:  Documents/log
 
-- iOS or Mac: In the sandbox Documents/log folder.
+- Android: /sdcard/Android/data/[your application package name]/files/log/liteav/
 
-- Android: In the /sdcard/Android/data/[your application package name]/files/log/liteav/ folder.
-
-- Windows: In the C:/Users/[system username]/AppData/Roaming/liteav/log, i.e. %APPDATA%/liteav/log folder.
+- Windows: C:/Users/[system username]/AppData/Roaming/liteav/log, i.e. %APPDATA%/liteav/log

package/resource/knowledge/callkit/faq/error-code.md

@@ -0,0 +1,67 @@
+Notify users of warnings and errors that occur during audio and video calls.
+
+## TUICallDefine Error Code
+| Definition | Value | Description |
+| --- | --- | --- |
+| ERROR_PACKAGE_NOT_PURCHASED | -1001 | You do not have TUICallKit package, please <a href="https://console.trtc.io/call">open the free experience</a> in the console or <a href="https://console.trtc.io/subscription/buy/call">purchase the official package</a>. |
+| ERROR_PACKAGE_NOT_SUPPORTED | -1002 | The package you purchased does not support this ability. You can refer to<br>console to purchase <a href="https://console.trtc.io/subscription/buy/call">Upgrade package</a>. |
+| ERROR_TIM_VERSION_OUTDATED | -1003 | The Chat SDK version is too low, please upgrade the Chat SDK version to ≥ 6.6; Find and modify in the build.gradle file.："com.tencent.imsdk:imsdk-plus:7.1.3925" |
+| ERROR_PERMISSION_DENIED | -1101 | Failed to obtain permission. The audio/video permission is not authorized. Check if the device permission is enabled. |
+| ERROR_GET_DEVICE_LIST_FAIL | -1102 | Failed to get the device list (only supported on web platform). |
+| ERROR_INIT_FAIL | -1201 | The init method has not been called for initialization. The TUICallEngine API should be used after initialization. |
+| ERROR_PARAM_INVALID | -1202 | Param is invalid. |
+| ERROR_REQUEST_REFUSED | -1203 | The current status can't use this function. |
+| ERROR_REQUEST_REPEATED | -1204 | The current status is waiting/accept, please do not call it repeatedly. |
+| ERROR_SCENE_NOT_SUPPORTED | -1205 | The current calling scene does not support this feature. |
+| ERROR_SIGNALING_SEND_FAIL | -1406 | Failed to send signaling. You can check the specific error message in the callback of the method. |
+
+## Chat Error Code
+
+Video and audio calls use Tencent Cloud's Chat SDK as the basic service for communication, such as the core logic of call signaling and busy signaling. Common error codes are as follows:
+
+|Error Code|Description|
+|---------|---------|
+|6014|You have not logged in to the Chat SDK or have been forcibly logged out. Log in to the Chat SDK first and try again after a successful callback. To check whether you are online, use TIMManager getLoginUser.|
+|6017|Invalid parameter. Check the error information to locate the invalid parameter.|
+|6206|UserSig has expired. Get a new valid UserSig and log in again. For more information about how to get a UserSig, see [Generating UserSig](https://www.tencentcloud.com/document/product/1047/34385).|
+|7013|The current package does not support this API. Please upgrade to the Flagship Edition package.|
+|8010|The signaling request ID is invalid or has been processed.|
+
+> **Note：**
+>
+
+> More Chat SDK error codes are available at：[Chat Error Code](https://www.tencentcloud.com/document/product/1047/34348)
+>
+
+## TRTC Error Code
+
+Video and audio calls use Tencent Cloud's Chat SDK as the basic service for calling, such as the core logic of switching camera and microphone on or off. Common error codes are as follows:
+
+|Enum|Value|Description|
+|---------|---------|---------|
+|ERR_CAMERA_START_FAIL|-1301|Failed to turn the camera on. This may occur when there is a problem with the camera configuration program (driver) on Windows or macOS. Disable and reenable the camera, restart the camera, or update the configuration program.|
+|ERR_CAMERA_NOT_AUTHORIZED|-1314|No permission to access to the camera. This usually occurs on mobile devices and may be because the user denied access.|
+|ERR_CAMERA_SET_PARAM_FAIL|-1315|Incorrect camera parameter settings (unsupported values or others).|
+|ERR_CAMERA_OCCUPY|-1316|The camera is being used. Try another camera.|
+|ERR_MIC_START_FAIL|-1302|Failed to turn the mic on. This may occur when there is a problem with the mic configuration program (driver) on Windows or macOS. Disable and reenable the mic, restart the mic, or update the configuration program.|
+|ERR_MIC_NOT_AUTHORIZED|-1317|No permission to access to the mic. This usually occurs on mobile devices and may be because the user denied access.|
+|ERR_MIC_SET_PARAM_FAIL|-1318|Failed to set mic parameters.|
+|ERR_MIC_OCCUPY|-1319|The mic is being used. The mic cannot be turned on when, for example, the user is having a call on the mobile device.|
+|ERR_TRTC_ENTER_ROOM_FAILED|-3301|Failed to enter the room. For the reason, refer to the error message for -3301.|
+
+> **Note：**
+>
+
+> More TRTC SDK error codes are available at：[TRTC Error Code](https://www.tencentcloud.com/document/product/647/35130)
+>
+
+## CallKit Server Error Code
+
+New version of CallKit REST API error codes, for example, when retrieving call status and call records. Common error codes are as follows:
+
+|Error Code|Description|
+|---------|---------|
+|101001|Internal server error, please try again.|
+|101002|Invalid parameter, check if parameters meet requirements. Refer to error message for specific invalid field.|
+|101004|Call does not exist or has already ended.|
+|101050|Call record does not exist.|

package/resource/knowledge/callkit/faq/flutter.md

@@ -0,0 +1,52 @@
+## 1. Integrate `tencent_calls_uikit` and `tencent_trtc_cloud` at the same time, or integrate `tencent_calls_uikit` and `live_flutter_plugin` at the same time, and the symbol conflict will occur, how to solve it?
+
+Detials: When introducing flutter ''tencent_calls_uikit'' into our existing project, Android builds APK with the following error:
+``` plaintext
+Duplicate class com.tencent.liteav.LiveSettingJni found in modules jetified-LiteAVSDK_Professional-10.7.0.13053-runtime
+(com.tencent.liteav:LiteAVSDK_Professional:10.7.0.13053) and jetified-LiteAVSDK_TRTC-10.3.0.11225-runtime
+(com.tencent.liteav:LiteAVSDK_TRTC:10.3.0.11225)
+```
+
+The following error occurs when `pod install` is executed on iOS:
+``` plaintext
+[!] The 'Pods-Runner' target has frameworks with conflicting names: txsoundtouch.xcframework and txffmpeg.xcframework.
+```
+
+The issue arises because you are using  tencent_calls_uikit  and  tencent_trtc_cloud  which depend on the Pro and Lite versions of  TRTC Android SDK , respectively. We have resolved this issue in the latest version. You just need to upgrade  [tencent_calls_uikit](https://pub.dev/packages/tencent_calls_uikit)  and  [tencent_trtc_cloud](https://pub.dev/packages/tencent_trtc_cloud) to the latest version.
+
+## 2. Flutter Android does not add confusion Settings, how to set?
+
+If you need to compile and run on the Android platform, because we use the reflection feature of Java inside the SDK, we need to add some classes in the SDK to the list of non-obviation, so you need to add the following code in the proguard-rules.pro file:
+``` plaintext
+-keep class com.tencent.** { *; }
+```
+
+## 3. How can I fix a compilation error or page failure caused by an upgrade from a version earlier than 1.8.0 to 1.8.0 or later?
+
+If you are upgrading from 1.8.0 or below to 1.8.0 or above, you need to check that the following steps are normal:
+1. Add `navigatorObservers `to `MateriaApp`. The purpose is to navigate to the TUICallKit page when you receive a call invitation. Example code is as follows:
+
+   ``` plaintext
+   import 'package:tencent_calls_uikit/tuicall_kit.dart';
+
+   MaterialApp（
+        navigatorObservers：[TUICallKit.navigatorObserver]，
+        ...
+   ）
+   ```
+2. `tencent_calls_engine `Import files in plug-ins are uniformly replaced with new ones.
+
+   ``` plaintext
+   import 'package:tencent_calls_engine/tuicall_engine.dart';
+   import 'package:tencent_calls_engine/tuicall_observer.dart';
+   import 'package:tencent_calls_engine/tuicall_define.dart';
+   ```
+
+   The above code block content is replaced with the following:
+
+   ``` plaintext
+   import 'package:tencent_calls_engine/tencent_calls_engine.dart';
+   ```
+3. The login API adjustment is more standardized and no parameters need to be specified.
+
+4. Optimization of offline push parameter construction.

package/resource/knowledge/callkit/faq/ios.md

@@ -0,0 +1,104 @@
+### The error message "The package you purchased does not support this ability"?
+
+If you encounter the above error message, it is because the audio and video call capability package of your current application has expired or has not been activated. You can refer to the service activation guide to claim or activate the audio and video call capability, and then continue to use the TUICallKit component.
+
+### How to modify TUICallKit source code?
+
+To import the component using `CocoaPods`, follow these steps:
+1. Create a **TUICallKit** folder in the same directory as your project's **Podfile**.
+
+2. Click to enter [**Github/TUICallKit**](https://github.com/tencentyun/TUICalling) , select Clone/Download code, and then copy the [TUICallKit_Swift](https://github.com/Tencent-RTC/TUICallKit/tree/main/iOS/TUICallKit_Swift) folder and [TUICallKit_Swift.podspec](https://github.com/Tencent-RTC/TUICallKit/blob/main/iOS/TUICallKit_Swift.podspec) file in the [**iOS**](https://github.com/tencentyun/TUICalling/tree/main/iOS) directory to the **TUICallKit** folder you created in Step 1.
+
+3. Add the following dependencies to your `Podfile`.
+
+   ``` bash
+   # :path => "Directed TUICallKit-Swift.podspec's phase path"
+   pod 'TUICallKit_Swift', :path => "TUICallKit/TUICallKit_Swift.podspec"
+   ```
+4. Execute the **pod install** command to complete the import.
+
+   > **Note:**
+   >
+
+   > The `TUICallKit_Swift`folder and `TUICallKit_Swift.podspec` file must be in the same directory.
+   >
+
+   **After integrating the **`TUICallKit_Swift`** component, the effect is as follows:**
+
+   > **Note：**
+   >
+
+   > After integrating the TUICallKit_Swift component, it supports hierarchical folder display, making it easier for you to read and modify the source code.
+   >
+
+### Xcode 15 compiler error?
+
+#### 1、**Sandbox: rsync **is displayed.
+
+You can set **User Script Sandboxing** to **NO** in **Build Settings:**
+
+#### 2、If **SDK does not contain**, compile error screenshot.
+
+Add the following code to the Podfile:
+``` bash
+# target 'xxxx' do
+#  ...
+#  pod 'TUICallKit_Swift'
+# end
+
+post_install do |installer|
+  installer.pods_project.targets.each do |target|
+    target.build_configurations.each do |config|
+      config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0'
+    end
+  end
+end
+```
+
+#### 3、If you run the simulator on an M-series computer, **Linker command failed with exit code 1 (use-v to see invocation) **may appear.
+
+Add the following code to the Podfile:
+``` bash
+# target 'xxxx' do
+#  ...
+#  pod 'TUICallKit_Swift'
+# end
+
+post_install do |installer|
+  installer.pods_project.targets.each do |target|
+    target.build_configurations.each do |config|
+      config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = "arm64"
+    end
+  end
+end
+```
+
+### Is there a conflict between TUICallKit and the integrated audio and video library?
+
+Tencent Cloud's audio and video libraries cannot be integrated at the same time, and there may be symbol conflicts. You can handle it according to the following scenarios.
+1. If you are using the `TXLiteAVSDK_TRTC` library, there will be no symbol conflicts. You can directly add dependencies in the Podfile file.
+
+   ``` bash
+   pod 'TUICallKit_Swift'
+   ```
+2. If you are using the `TXLiteAVSDK_Professional` library, there will be symbol conflicts. You can add dependencies in the `Podfile` file.
+
+   ``` bash
+   pod 'TUICallKit_Swift/Professional'
+   ```
+3. If you are using the `TXLiteAVSDK_Enterprise` library, there will be symbol conflicts. It is recommended to upgrade to `TXLiteAVSDK_Professional` and then use`TUICallKit_Swift/Professional`。
+
+### Does TUICallKit support background operation?
+
+Yes, if you need to continue running related functions in the background, you can select the current project, and in the Background Modes section under Capabilities, check **Audio, AirPlay, and Picture in Picture**, as shown in the following image:
+
+### How to view TRTC logs?
+
+TRTC logs are compressed and encrypted by default, with the extension .xlog. Whether the log is encrypted can be controlled by setLogCompressEnabled. The file name containing C(compressed) is encrypted and compressed, and the file name containing R(raw) is plaintext.
+
+iOS：Sandbox's `Documents/log`
+
+> **Note:**
+>
+> - To view the .xlog file, you need to download the [decryption tool](https://dldir1.qq.com/hudongzhibo/log_tool/decode_mars_log_file.py) and run it directly in the Python 2.7 environment with the xlog file in the same directory using python decode_mars_log_file.py.
+> - To view the .clog file (new log format after version 9.6), you need to download the [decryption tool](http://dldir1.qq.com/hudongzhibo/log_tool/decompress_clog.py) and run it directly in the Python 2.7 environment with the clog file in the same directory using python decompress_clog.py.

package/resource/knowledge/callkit/faq/web.md

@@ -0,0 +1,74 @@
+### What should I do if I receive the error message "The package you purchased does not support this ability"?
+
+If you encounter the error message above, it's because the Audio and Video Calling Capability Package of your current application has either expired or not been activated. Please refer to [Activate Service](https://trtc.io/document/59832) to claim or activate the audio and video calling capability, and continue to use the TUICallKit Component.
+
+### How do I purchase a package?
+
+Please follow the link [Purchase Official Version](https://trtc.io/document/59832).
+
+### How can I generate a UserSig?
+
+UserSig is a type of security signature designed by Tencent Cloud for its cloud services. It serves as a login credential, derived from the encrypted combination of information such as SDKAppID and SecretKey.
+- **Method 1:** Accessing from the control panel, refer to [ How to Obtain a Temporary UserSig](https://console.trtc.io/usersig).
+
+- **Method 2:** Deploying a temporary generation script.
+
+   > **Warning:**
+   >
+
+   > This approach involves configuring the SecretKey within the front-end code. Regrettably, in this method, the SecretKey can be easily decrypted through reverse engineering. In the event of your key being exposed, attackers can usurp your Tencent Cloud traffic. Therefore, ** this method is only suitable for local functional debugging**. For a production environment, please refer to Method 3.
+   >
+
+   For easier initial debugging, `GenerateTestUserSig-es.js` in the `genTestUserSig(params)` function can be used temporarily to calculate userSig, for instance:
+
+   ``` javascript
+   import { genTestUserSig } from "./debug/GenerateTestUserSig-es.js";
+   const { userSig } = genTestUserSig({ userID: "Alice", SDKAppID: 0, SecretKey: "YOUT_SECRETKEY" });
+   ```
+- **Method 3:**Use in official environment.
+
+   The correct method of issuing UserSig is to integrate the calculation code of UserSig into your server-side, providing project-specific interfaces. When UserSig is needed, your project can launch requests to the business server to obtain dynamic UserSig. For detailed information, please see [Generating UserSig on Server-side](https://trtc.io/document/35166).
+
+### How is the groupID generated in a group call?
+
+The generation of groupID requires integration of the [@tencentcloud/chat](https://www.npmjs.com/package/@tencentcloud/chat) package. For specifics, refer to the [createGroup API](https://trtc.io/document/48465); below is an example of the code to generate groupID.
+``` javascript
+import Chat from "@tencentcloud/chat";   // npm i @tencentcloud/chat
+
+const userIDList: string[] = ['user1', 'user2'];
+async function createGroupID() {
+  const chat = Chat.create({ SDKAppID });
+  const memberList: any[] = userIDList.map(userId => ({ userID: userId }));
+  const res = await chat.createGroup({
+    type: Chat.TYPES.GRP_PUBLIC,
+    name: 'WebSDK',
+    memberList
+  });
+  return res.data.group.groupID;
+}
+```
+
+### How do I create a userID?
+
+**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.
+- Signing in once with userID and userSig will automatically create the user.
+
+- Create and get through the [Tencent RTC Console](https://console.trtc.io/chat/account-management).
+
+## Error <call>: failed Invalid sender or receiver identifier？
+
+This error occurs because the userID you called does not exist; ensure the userID has signed in at least once. See [How do I create a userID](https://trtc.io/document/51024) for more details.
+
+## Error [CallService]API<init>: sdkAppID is required？
+
+- This error occurs because you did not fill in the SDKAppID information during [TUICallKitServer.init](https://trtc.io/document/51015#init)/ `GenerateTestUserSig.genTestUserSig`
+
+- Please obtain and fill in from the [Tencent RTC Console](https://trtc.io/document/59832).
+
+## npm install -g create-react-app error: errno -13？
+
+If this error occurs, it is because the current user does not have permission to globally install scaffolding. Please use`sudo npm install -g create-react-app`**.**
+
+## **npm install -g @vue/cli package error: errno -13？**
+
+If this error occurs, it is because the current user does not have permission to globally install scaffolding. Please use `sudo npm install -g @vue/cli`**.**