Known Issues - Android

This page lists known issues in Android SDK 3.x and how to work around them.

Issue : 1

x86 / x86_64 emulator images are not supported.

Solution

The SDK supports only arm64-v8a and armeabi-v7a. Test on an ARM phone, or on an emulator with an arm64-v8a system image.

If your app ships native libraries for other ABIs, limit the app to arm64-v8a and armeabi-v7a, so it is not installed on devices where the SDK cannot load:

app/build.gradle.kts

android {
    defaultConfig {
        ndk {
            abiFilters += listOf("arm64-v8a", "armeabi-v7a")
        }
    }
}

Issue : 2

A minified (R8 / ProGuard) release build needs keep rules for the videosdk.org classes.

Solution

The SDK ships keep rules for its own API in live.videosdk.rtc.android. They do not cover the SDK's videosdk.org classes. Add these rules to proguard-rules.pro:

proguard-rules.pro

-keep class videosdk.org.** { *; }
-dontwarn videosdk.org.**

Keep the -dontwarn line, because the keep rule alone fails the R8 step with a missing-class error. Rules you wrote for org.webrtc.** no longer match anything, so replace them with these.

Issue : 3

The virtual background library, live.videosdk:videosdk-media-effects, does not work with 3.x.

Solution

Remove the videosdk-media-effects dependency. It does not work with 3.x, and 3.x has no built-in virtual background.