ApsaraVideo Live:Download and integrate ARTC SDK

Step 1: Import SDK

dependencyResolutionManagement {
    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
    repositories {
        google()
        mavenCentral()
        // Add the Maven repository for the ARTC SDK
        maven { url 'https://maven.aliyun.com/repository/google' }
        maven { url 'https://maven.aliyun.com/repository/public' }
    }
}

allprojects {
    repositories {
        ...
        // Add the Maven repository for the ARTC SDK
        maven { url 'https://maven.aliyun.com/repository/google' }
        maven { url 'https://maven.aliyun.com/repository/public' }
    }
}

dependencies {
    // Add the dependencies for the ARTC SDK
    // Replace ${latest_version} with the specific version number.
    implementation 'com.aliyun.aio:AliVCSDK_ARTC:${latest_version}'
    // For versions 7.4.0 and below, add the keep dependency
    // implementation 'com.aliyun.aio.keep:keep:1.0.1'
}   

dependencyResolutionManagement {
    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
    repositories {
        google()
        mavenCentral()
        // Add the relative directory where the ARTC SDK is located
        flatDir {
            dir 'app/libs'
        }
    }
}

allprojects {
    repositories {
        ...
        // Add the relative directory where the ARTC SDK is located
        flatDir {
            dir 'app/libs'
        }
    }
}

// Replace x.y.z with the specific version number.
implementation(name:'AliVCSDK_ARTC', version: 'x.y.z', ext:'aar')

Step 2: Configure supported CPU architectures

Open the app/build.gradle file and specify the CPU architectures supported by your project in defaultConfig, as shown in the following example. Available architectures include armeabi-v7a, arm64-v8a, x86, and x86_64.

android {
    defaultConfig {
        // ...other default configurations
        // Support armeabi-v7a and arm64-v8a architectures
        ndk {
             abiFilters "armeabi-v7a", "arm64-v8a"
        }
    }
}	

Step 3: Configure permissions

Configure the permissions required by your application:

Go to the app/src/main directory, open the AndroidManifest.xml file, and add the required permissions.

<uses-feature android:name="android.hardware.camera" android:required="false" /> 
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.RECORD_AUDIO" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<!-- Request legacy Bluetooth permissions on older devices. -->
<uses-permission
  android:name="android.permission.BLUETOOTH"
  android:maxSdkVersion="30" />
<uses-permission
  android:name="android.permission.BLUETOOTH_ADMIN"
  android:maxSdkVersion="30" />

<!-- Needed only if your app communicates with already-paired Bluetooth devices. -->
<uses-permission android:name="android.permission.BLUETOOTH_CONNECT" />
<uses-permission android:name="android.permission.CHANGE_NETWORK_STATE" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.WRITE_SETTINGS"
  tools:ignore="ProtectedPermissions" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />

<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.BLUETOOTH" />
<uses-permission android:name="android.permission.BLUETOOTH_CONNECT" />
<uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />

<uses-permission android:name="android.permission.BLUETOOTH_CONNECT" tools:node="remove"/>

<!-- Declare the legacy Bluetooth permission -->
<uses-permission android:name="android.permission.BLUETOOTH" />
<!-- Override and remove the newer permission for API 31+ -->
<uses-permission android:name="android.permission.BLUETOOTH_CONNECT" tools:node="remove" />

<!-- Declare the legacy Bluetooth permission and set maxSdkVersion for older devices -->
<uses-permission android:name="android.permission.BLUETOOTH"/>
<!-- Declare the new Bluetooth permission for API 31+ -->
<uses-permission android:name="android.permission.BLUETOOTH_CONNECT"/>
<!-- Other Bluetooth permissions as needed -->

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.S) {
    String[] permissions = {
        android.Manifest.permission.BLUETOOTH_CONNECT
    };
    ActivityCompat.requestPermissions(activity, permissions, REQUEST_BLUETOOTH);
}

<!-- Override and remove Bluetooth permissions from the ARTC SDK -->
<uses-permission android:name="android.permission.BLUETOOTH" tools:node="remove" />
<uses-permission android:name="android.permission.BLUETOOTH_CONNECT" tools:node="remove" />

Step 4: Prevent code obfuscation (optional)

In the app/proguard-rules.pro file, configure rules for the SDK to prevent the interfaces provided by the SDK from being obfuscated, which leads to improper function calls.

-keep class com.aliyun.allinone.** {
*;
}

-keep class com.aliyun.rts.network.AliHttpTool {
*;
}

-keep class com.aliyun.common.AlivcBase {
*;
}

-keep class com.huawei.multimedia.alivc.** {
*;
}

-keep class com.alivc.rtc.** {
*;
}

-keep class com.alivc.component.** {
*;
}

-keep class org.webrtc.** {
*;
}

Does the ARTC SDK add extra permissions?

Yes. Importing the ARTC SDK will automatically add the following Android permissions to your app's manifest. The exact list may vary by SDK version. For the definitive list, refer to the AndroidManifest.xml file within the .aar library.

<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.BLUETOOTH" />
<uses-permission android:name="android.permission.BLUETOOTH_CONNECT" />
<uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />

These permissions are primarily used for features such as network state detection, Wi-Fi information access, Bluetooth connectivity, and audio routing.

How can I handle permission conflicts or compatibility issues?

Although the ARTC SDK includes internal logic to handle Android version compatibility (such as the runtime permission requirement for BLUETOOTH_CONNECT on Android 12+), issues can still arise in certain scenarios:

• Runtime issues: Your app may experience unexpected behavior, such as a manifest merge failure during the build process.

• Google Play review risks: If your app declares a permission for a feature it doesn't use (such as Bluetooth), it may violate the principle of least privilege and lead to your app being rejected from the Play Store.

To resolve these issues, we recommend the following steps:

1. Evaluate permission necessity
   First, assess whether your app needs all the permissions declared by the SDK. If a feature (such as Bluetooth) is not used, remove its permission declaration. For example, if your app's targetSdkVersion is 30 or lower, you do not need the BLUETOOTH_CONNECT permission.

2. Use Manifest merge rules to resolve conflicts
   If multiple library modules declare the same permission with conflicting attributes (such as a different maxSdkVersion), you can use the tools namespace in your app's main AndroidManifest.xml file to override the behavior.

   <manifest xmlns:android="http://schemas.android.com/apk/res/android"
       xmlns:tools="http://schemas.android.com/tools">
       
       <!-- Example: Remove a permission declared by the SDK but not needed by the app -->
       <uses-permission 
           android:name="android.permission.BLUETOOTH_CONNECT"
           tools:node="remove" />
           
       <!-- Example: Override a permission attribute -->
       <uses-permission
           android:name="android.permission.BLUETOOTH"
           android:maxSdkVersion="30"
           tools:replace="android:maxSdkVersion" />
   </manifest>
   

Step 1: Import SDK

sudo gem install cocoapods

pod init

target 'MyApp' do
  use_frameworks!
  # Replace ${latest version} with a specific version number.
  pod 'AliVCSDK_ARTC', '~> ${latest version}'
end

pod install

Step 2: Configure permissions

• You must add recording and camera permissions

Add camera and microphone permissions Privacy - Camera Usage Description and Privacy - Microphone Usage Description to the Info.plist file.

• Enable audio background mode (optional).

As shown in the figure, check Audio, AirPlay, and Picture in Picture.