Android app build failed after adding SDK

Hello, I have followed the guide to add the android meeting SDK into my native Android app.
I have confirmed that I added both the aar.file into my build.gradle.
implementation project(path: ‘:mobilertc’)
implementation project(path: ‘:commonlib’)

Below is the error I got when I try to build my app.
1: Task failed with an exception.

  • What went wrong:
    Execution failed for task ‘:app:checkDebugDuplicateClasses’.

Could not resolve all files for configuration ‘:app:debugRuntimeClasspath’.
Could not find com.google.android:flexbox:2.0.1.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/com/google/android/flexbox/2.0.1/flexbox-2.0.1.pom
- https://repo.maven.apache.org/maven2/com/google/android/flexbox/2.0.1/flexbox-2.0.1.pom
Required by:
project :app > project :mobilertc

  • Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.

  • What went wrong:
    Execution failed for task ‘:app:desugarDebugFileDependencies’.

Could not resolve all files for configuration ‘:app:debugRuntimeClasspath’.
Could not find com.google.android:flexbox:2.0.1.
Required by:
project :app > project :mobilertc

  • Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

3: Task failed with an exception.

  • What went wrong:
    Execution failed for task ‘:app:checkDebugAarMetadata’.

Could not resolve all files for configuration ‘:app:debugRuntimeClasspath’.
Could not find com.google.android:flexbox:2.0.1.
Required by:
project :app > project :mobilertc

  • Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

4: Task failed with an exception.

  • What went wrong:
    Execution failed for task ‘:app:mergeDebugResources’.

Could not resolve all files for configuration ‘:app:debugRuntimeClasspath’.
Could not find com.google.android:flexbox:2.0.1.
Required by:
project :app > project :mobilertc

  • Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

5: Task failed with an exception.

  • What went wrong:
    Execution failed for task ‘:app:processDebugMainManifest’.

Could not resolve all files for configuration ‘:app:debugRuntimeClasspath’.
Could not find com.google.android:flexbox:2.0.1.
Required by:
project :app > project :mobilertc

  • Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

6: Task failed with an exception.

  • What went wrong:
    Execution failed for task ‘:app:mergeDebugAssets’.

Could not resolve all files for configuration ‘:app:debugRuntimeClasspath’.
Could not find com.google.android:flexbox:2.0.1.
Required by:
project :app > project :mobilertc

  • Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

7: Task failed with an exception.

  • What went wrong:
    Execution failed for task ‘:app:mergeDebugJavaResource’.

Could not resolve all files for configuration ‘:app:debugRuntimeClasspath’.
Could not find com.google.android:flexbox:2.0.1.
Required by:
project :app > project :mobilertc

  • Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

8: Task failed with an exception.

  • What went wrong:
    Execution failed for task ‘:app:mergeDebugNativeLibs’.

Could not resolve all files for configuration ‘:app:debugRuntimeClasspath’.
Could not find com.google.android:flexbox:2.0.1.
Required by:
project :app > project :mobilertc

Can someone guide me how to solve this problem? Thank you in advance.

Below is the list of tasks that were executed.

Task :app:clean
Task :app:preBuild UP-TO-DATE
Task :app:preDebugBuild UP-TO-DATE
Task :app:mergeDebugNativeDebugMetadata NO-SOURCE
Task :app:generateDebugBuildConfig
Task :app:javaPreCompileDebug
Task :app:generateDebugResValues
Task :app:createDebugCompatibleScreenManifests
Task :app:extractDeepLinksDebug
Task :app:mergeDebugShaders
Task :app:compileDebugShaders NO-SOURCE
Task :app:generateDebugAssets UP-TO-DATE
Task :app:processDebugJavaRes NO-SOURCE
Task :app:checkDebugDuplicateClasses FAILED
Task :app:desugarDebugFileDependencies FAILED
Task :app:mergeDebugJniLibFolders
Task :app:validateSigningDebug
Task :app:writeDebugAppMetadata
Task :app:writeDebugSigningConfigVersions
Task :app:compileDebugAidl NO-SOURCE
Task :app:compileDebugRenderscript NO-SOURCE
Task :app:checkDebugAarMetadata FAILED
Task :app:generateDebugResources
Task :app:mergeDebugResources FAILED
Task :app:packageDebugResources
Task :app:mergeDebugAssets FAILED
Task :app:processDebugMainManifest FAILED
Task :app:mergeDebugJavaResource FAILED
Task :app:mergeDebugNativeLibs FAILED
Task :app:parseDebugLocalResources

The version of my Zoom SDK is v5.11.3.7251

I am having same…A lot of issues after adding SDK to my app. It built fine before adding SDK, does not build after adding SDK. Did you get any solution?

Solved issue.
-Upgraded build:gradle
-removed flexbox:flexbox from gradle.

@justintohtw ,

You are still having issues building the SDK? Have you tried upgrading build:gradle as suggested by @sreeharikr298?

No. It was a package duplication issue. @donte.zoom

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.