When I try to build my project with gradle wrapper I get this error: The same project builds OK in Android Studio. I’ve already checked this and this but I’m using gradle wrapper version 4.1, have added google() repository and even tried setting android.enableAapt2=false. Any other tips? Thanks. My root build.gradle file: My gradle-wrapper.properties file: … Read more
Android Studio (1.2 RC0) keeps telling me Error running android: Gradle project sync failed. Please fix your project and try again. How can I find out what the problem is? Unfortunately the solutions from this SO thread did not help.
It should be exclude module: ‘net.milkbowl:vault:1.2.27′(add module:) as explained in documentation for DependencyHandler linked from here because ModuleDependency.exclude(java.util.Map) method is used.
Try to upgrade your buildToolsVersion to “23.0.1”, like this: If you didn’t install the buildTools for this version, please download it with SDKManager as hint.
Found this: The google-services.json file is generally placed in the app/ directory, but as of version 2.0.0-alpha3 of the plugin support was added for build types, which would make the following directory structure valid: Source Source 2
Your gradle wrapper is missing, broken or corrupted. What is gradle wrapper:gradlew is the gradle wrapper executable – batch script on windows and shell script elsewhere. The wrapper script when invoked, downloads the defined gradle version and executes it. By distributing the wrapper with your project, anyone can work with it without needing to install Gradle … Read more
never mind, i changed the name in settings.gradle and synced and then changed it back and synced again and it inexplicably worked this time.
Found it. System property ‘java.home’ is not JAVA_HOME environment variable. JAVA_HOME points to the JDK, while java.home points to the JRE. See that page for more info. Soo… My problem was that my startpoint was the jre folder (C:\jdk1.6.0_26\jre) and not the jdk folder (C:\jdk1.6.0_26) as I thought(tools.jar is on the C:\jdk1.6.0_26\lib folder ). The compile line in dependencies.gradle … Read more
To answer my own question, you need to add the following to your project-level build.gradle file:
Generally, you can refresh dependencies in your cache with the command line option –refresh-dependencies. You can also delete the cached files under ~/.gradle/caches. With the next build Gradle would attempt to download them again. What is your specific use case? Do you use dynamic dependency versions or SNAPSHOT versions? On Unix systems, you can delete all the … Read more