-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
3e72a94
commit 501c8e7
Showing
31 changed files
with
360 additions
and
61 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -62,4 +62,24 @@ Users that do not fall into the above two categories can use the Agora services | |
|
||
**Solution** | ||
|
||
You do not need ID authentication if your phone number or IP address is not from mainland China. If you need ID authenticationn for getting an invoice, ensure that your phone number or IP address is from mainland China. | ||
If your verified phone number or network IP address does not belong to mainland China, real-name authentication is not required. If you wish to submit real-name authentication information, please modify your phone number or network IP address in the console to one belonging to mainland China. | ||
|
||
## How to Switch from the International Console Account to the Domestic Console Account? | ||
|
||
**Issue description** | ||
|
||
Due to business requirements or operational errors, some users need to switch their console account from the [International version](https://console.agora.io) to the [Domestic version](https://console.shengwang.cn/), but cannot find the switch settings in the console. | ||
|
||
**Reason** | ||
|
||
To comply with data security and compliance requirements, Agora's international and domestic console versions have data isolation, so users cannot switch account regions on their own. | ||
|
||
**Solution** | ||
|
||
- If there is minimal project data in your account, Agora recommends registering a new domestic version account. See [Account Registration](/doc/console/general/quickstart#register-account) for details. | ||
- If there is significant project data in your account, contact sales at [[email protected]](mailto:[email protected]) for assistance with account switching and data migration. | ||
|
||
<Admonition type="danger" title="Warning"> | ||
- Agora only supports switching from an International console account to a Domestic console account; reverse operations are not supported. | ||
- Once you switch your International console account to a Domestic console account, this operation cannot be undone. Therefore, please proceed with caution. | ||
</Admonition> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
--- | ||
title: 'How to handle errors when running the `pod install` command?' | ||
sidebar_position: 1016 | ||
platforms: [] | ||
products: [] | ||
--- | ||
|
||
export const toc = [{}]; | ||
|
||
When running `pod install`, the following error occurs: | ||
|
||
```shell | ||
[!] Invalid Podfile file: /xxx/ios/Flutter/Generated.xcconfig must exist. If you’re running pod install manually, make sure flutter pub get is executed first. | ||
``` | ||
|
||
## Reason | ||
|
||
The error message indicates that the `Generated.xcconfig` file is missing. This file is necessary for building the Flutter app on iOS devices. If you do not run `flutter pub get` to generate this file before executing `pod install`, you will encounter this error. | ||
|
||
## Solution | ||
|
||
To resolve this issue, follow these steps: | ||
|
||
1. Open the terminal and navigate to the root directory of your Flutter project. | ||
1. Run the `flutter pub get` command to fetch and update the project's dependencies. This command will also generate the `Generated.xcconfig` file and other necessary configuration files. | ||
1. Re-run pod install. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
--- | ||
title: 'How to resolve Xcode project compilation failure due to missing development team configuration information?' | ||
sidebar_position: 952 | ||
platforms: [] | ||
products: [] | ||
--- | ||
|
||
export const toc = [{}]; | ||
|
||
When deploying the Xcode project to an iOS device for debugging, the following error occurs: | ||
|
||
```shell | ||
Error: Signing for "Runner" requires a development team. Select a development team in the Signing & Capabilities editor. (in target 'Runner' from project 'Runner') | ||
``` | ||
## Reason | ||
On the iOS platform, all apps require a developer signature certified by Apple to verify the source and security of the app. If Xcode fails to detect a valid development team or certificate, it will not be able to complete the compilation and deployment of the app. | ||
## Solution | ||
Refer to [Apple's official instructions](https://help.apple.com/xcode/mac/current/#/dev60b6fbbc7) to configure a valid development team and certificate. | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,78 @@ | ||
--- | ||
title: 'How do I handle issues when integrating the Signaling SDK and RTC SDK simultaneously?' | ||
sidebar_position: 664 | ||
platforms: [] | ||
products: [] | ||
--- | ||
|
||
export const toc = [{}]; | ||
|
||
When integrating Signaling SDK version 2.2.0 and above with RTC SDK version 4.3.0 and above, the following errors may appear in the IDE: | ||
|
||
- **Android:** | ||
```java | ||
com.android.builder.merge.DuplicateRelativeFileException: More than one file was found with OS independent path 'lib/x86/libaosl.so' | ||
``` | ||
|
||
- **IOS:** | ||
|
||
```objc | ||
Unexpected duplicate tasks | ||
Multiple commands produce <your_app_build_path>/Contents/Frameworks/aosl.framework/Versions/A' | ||
``` | ||
## Reason | ||
Both Signaling SDK versions 2.2.0 and above and RTC SDK versions 4.3.0 and above use the same library: | ||
- **Android SDK**: `lib/x86/libaosl.so` | ||
- **IOS SDK**: `libs/aosl.xcframework` | ||
As a result, the IDE detects multiple files with the same path during the build process, leading to errors. | ||
## Solution | ||
### Android SDK | ||
Depending on your integration method, follow the corresponding solution below: | ||
- **Using CDN** | ||
1. Manually delete the following files in the SDK package: | ||
- `lib/x86/libaosl.so` | ||
- `lib/x86_64/libaosl.so` | ||
- `lib/armeabi-v7a/libaosl.so` | ||
- `lib/arm64-v8a/libaosl.so` | ||
2. Rebuild the project. | ||
- **Using Maven** | ||
1. Add the `packagingOptions` node to the `android` node in the `build.gradle` file to specify that the first matching file is preferred during the build process: | ||
```groovy | ||
android { | ||
// ... | ||
packagingOptions { | ||
pickFirst 'lib/x86/libaosl.so' | ||
pickFirst 'lib/x86_64/libaosl.so' | ||
pickFirst 'lib/armeabi-v7a/libaosl.so' | ||
pickFirst 'lib/arm64-v8a/libaosl.so' | ||
} | ||
} | ||
``` | ||
2. After the Gradle file synchronization is complete, rebuild the project. | ||
### IOS SDK | ||
Depending on your integration method, follow the corresponding solution below: | ||
- **Using CDN** | ||
1. Manually delete the `libs/aosl.xcframework` file in the SDK package. | ||
2. Rebuild the project. | ||
- **Using CocoaPods** | ||
1. After successfully running the `pod install` command to install the SDK, manually delete the `aosl.xcframework` file in the project's `/Pods/AgoraRtm` path. | ||
2. Rebuild the project. | ||
|
||
|
||
|
||
|
||
|
||
|
Oops, something went wrong.