Cause: com.novoda.gradle.release.AndroidLibrary$LibraryUsage.getDependencyConstraints()Ljava/util/Set;
See original GitHub issueThis is happened after i update to AndroidStudio 3.2
Cause: com.novoda.gradle.release.AndroidLibrary$LibraryUsage.getDependencyConstraints()Ljava/util/Set;
The solution is to use gradle 4.4
but ofcourse, we can not use it since minimum supported gradle version for Android studio 3.2 is 4.6. So, can’t make it 4.4. Here is the error if i change back to 4.4:
Gradle sync failed: Minimum supported Gradle version is 4.6. Current version is 4.4. If using the gradle wrapper, try editing the distributionUrl in E:\mobile\ionic\jasatukang\android\gradle\wrapper\gradle-wrapper.properties to gradle-4.6-all.zip
For more information, please look at this issue
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Issues - GitHub
Cause : com.novoda.gradle.release.AndroidLibrary$LibraryUsage.getDependencyConstraints()Ljava/util/Set; What can I do.
Read more >Gradle error when Update to Android studio 3.2 - Stack Overflow
I updated my Android Studio version to 3.2. Now I am facing following error for my project - com.novoda.gradle.release.
Read more >问题 - CSDN博客
ERROR: Cause: com.novoda.gradle.release.AndroidLibrary$LibraryUsage.getDependencyConstraints()Ljava/util/Set; ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just a temp fix, since I was facing the same issue.
Open your project in Android Studio -> File -> Project Structure -> Project (sidebar) and set
Gradle version
: 4.4Android Plugin Version
: 3.1.1This is related to
com.novoda.bintray-release
.As that is only used for publishing capacitor-android, a better workaround would be to just remove all
com.novoda.bintray-release
related entries from capacitor-android’s build.gradle as you won’t be publishing.So remove
classpath 'com.novoda:bintray-release:0.8.0'
andapply plugin: 'com.novoda.bintray-release'
and the whole publish blockSeems like novoda has already fixed it, but not released, so we will have to wait until they release.
Another option would be to get rid of novoda plugin and use bintray plugin as proposed on this PR