I ran into the same issue with an internal component and resolved by downgrading Gradle to 3.4.2. This issue still persists in Gradle 3.5.2.

Hi there, any solution found for this problem?

this problem still occurred in Gradle 3.5.3

this problem still occurred in Gradle 3.5.3

That's correct. If you want to "fix" it by downgrading, try using 3.4.3.

I couldn't downgrade the Gradle version, I fixed it by uploading the aar's to internal artifactory

I couldn't downgrade the Gradle version, I fixed it by uploading the aar's to internal artifactory

Interesting.. Can you share some details which files you uploaded?

@mzennis could you please describe how you did this:

I fixed it by uploading the aar's to internal artifactory

OK, here is a little update from my side on this issue. I'm using React native and latest versions of RN 0.63 uses gradle plugin 3.5.3 by default.

I tried to update to gradle plugin 3.6.4 and it seems to work, solving by the way this issue with aar files.

Hope this will help someone.

I fixed it by add this code in module bulid.gradle

packagingOptions {
        merge "classes.jar"
        merge "AndroidManifest.xml"
        merge "proguard.txt"
}

I couldn't downgrade the Gradle version, I fixed it by uploading the aar's to internal artifactory

Interesting.. Can you share some details which files you uploaded?

I uploaded the aar library file that was previously local to the internal repository.

before:
implementation files('libs/mylibrary.aar')

now:
implementation 'com.xxx.xxx:mylibrary:1.0@aar'

Thank you for your interest in Gradle!

This is an issue with the Android Gradle Plugin which is developed by Google and cannot be addressed in the core of the Gradle Build Tool.

Please open such Android-related issues on the Android Issue Tracker at https://source.android.com/source/report-bugs