Skip to main content

How do I handle issues when integrating the Signaling SDK and Video SDK simultaneously?

When integrating Signaling SDK version 2.2.0 and above with Video SDK version 4.3.0 and above, the following errors may appear in the IDE:

  • Android:


    _1
    com.android.builder.merge.DuplicateRelativeFileException: More than one file was found with OS independent path 'lib/x86/libaosl.so'

  • iOS:


    _2
    Unexpected duplicate tasks
    _2
    Multiple commands produce <your_app_build_path>/Contents/Frameworks/aosl.framework/Versions/A'


    _1
    The 'XXX' target has frameworks with conflicting names: aosl.xcframework.

Why this happens

Both Signaling SDK versions 2.2.0 and above and Video SDK versions 4.5.0 and above use the same library:

  • Android: libaosl.so

  • iOS/macOS: aosl.xcframework

  • Windows: libaosl.dll

As a result, the IDE detects multiple files with the same path during the build process, leading to errors.

Solution

Follow these steps to resolve the issue:

Manually specify the aosl library version

Compare the aosl library versions included in both the Signaling and Video SDKs, and keep the version with the higher number.

You can find version information in the following release notes:

Remove older version files

After identifying the latest version:

  1. Delete the older version of the aosl library from your SDK package.
  2. Ensure the newer version is correctly linked in your build configuration.
  3. Rebuild the project.

Depending on your integration method, choose from the following solutions:

If the version of the aosl library included in the Video SDK package is lower than the version required by your project, delete the outdated library file based on the target platform:

  • Android: Delete the older-version libaosl.so file from the SDK package.
  • iOS/macOS: Delete the older-version aosl.xcframework file from the SDK package.
  • Windows: Delete the older-version libaosl.dll file from the SDK package.