Fixed
Status Update
Comments
ma...@gmail.com <ma...@gmail.com> #2
confirmed. had to downgrade to gradle-4.5.1.
br...@novvia.com <br...@novvia.com> #3
upgrading to 4.7 also didn't work if that helps
uc...@google.com <uc...@google.com>
ma...@gmail.com <ma...@gmail.com> #4
apparently the android studio compiler setting overrides gradle properties.
after disabling configure on demand there, `gradle-4.7` works fine.
after disabling configure on demand there, `gradle-4.7` works fine.
br...@novvia.com <br...@novvia.com> #5
Where does one go about "disabling configure on demand there" ?
to...@googlemail.com <to...@googlemail.com> #6
The bug seems to be related to reading the settings from "gradle.properties" located in the project root.
1. Setting "org.gradle.configureondemand=false" in "~/.gradle/gradle.properties" works.
2. Running "./gradlew -Dorg.gradle.configureondemand=false wrapper" works.
3. Setting "org.gradle.configureondemand=false" in "gradle.properties" in the root of the project does not work.
1. Setting "org.gradle.configureondemand=false" in "~/.gradle/gradle.properties" works.
2. Running "./gradlew -Dorg.gradle.configureondemand=false wrapper" works.
3. Setting "org.gradle.configureondemand=false" in "gradle.properties" in the root of the project does not work.
br...@novvia.com <br...@novvia.com> #7
here is where I found my errant "configure on demand" in the gui. Just in case anyone is wondering. Unchecked this and worked like a charm
je...@google.com <je...@google.com>
cs...@supercharge.io <cs...@supercharge.io> #8
I think we should not disable configure on demand in the first place.
hu...@google.com <hu...@google.com> #9
Thanks for the fix in comment #7 ! (See Issue 76429932 and https://developer.android.com/studio/known-issues for more info on this issue.)
Note that this will be fixed in 3.2.0, you can re-enable configure on demand then.
I understand that the error message should have been clearer, but this will go away soon in 3.2.0 so it's probably not worth releasing 3.1.3 just to fix that. Thanks again for the report!
Note that this will be fixed in 3.2.0, you can re-enable configure on demand then.
I understand that the error message should have been clearer, but this will go away soon in 3.2.0 so it's probably not worth releasing 3.1.3 just to fix that. Thanks again for the report!
hu...@google.com <hu...@google.com> #10
CC-ing Todd in case you want to add a note to the known issues section (https://developer.android.com/studio/known-issues ) to say that if the user enabled configuration on demand in Android Studio settings (see comment #7 ), they will also need to disable it there.
ko...@google.com <ko...@google.com> #11
re-opening as a documentation issue for me
ko...@google.com <ko...@google.com>
[Deleted User] <[Deleted User]> #12
The documentation for this known issue says that Android Studio 3.2 will remove configure on demand, so we won't have to disable that setting again. It doesn't say whether we will have to keep "org.gradle.configureondemand=false" in the project's gradle.properties to support command line builds with AGP 3.2. Will we be able to remove that as well? Thanks!
hu...@google.com <hu...@google.com> #13
@#12: The documentation says "If you're using Android Gradle Plugin 3.0.1 or 3.1.0 with Gradle 4.6, you should disable configuration on demand to avoid some unpredictable build errors." You don't need to disable configuration on demand when using AGP 3.2.0 or higher---this is implied by the previous sentence, but maybe we should still add it to clarify that point.
Leaving to Todd to decide.
Leaving to Todd to decide.
ko...@google.com <ko...@google.com> #14
Thanks for the feedback. I've updated the document to clarify these points. The updated document with clarifications will be available very soon.
Description
A problem occurred evaluating project ':app'.
> Failed to apply plugin [id 'com.android.application']
> Configuration on demand is not supported by the current version of the Android Gradle plugin since you are using Gradle version 4.6 or above. Suggestion: disable configuration on demand by setting org.gradle.configureondemand=false in your gradle.properties file or use a Gradle version less than 4.6.
* 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.
* Get more help at
I added the "org.gradle.configureondemand=false" to my root gradle.properties file and it still errors out :-/
Build: 3.1.2, AI-173.4720617, 201804132127,
AI-173.4720617, JRE 1.8.0_152-release-1024-b01x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.13.4 unknown, screens 1280x800, 1920x1200, 1920x1200
Android Gradle Plugin: 3.1.2
Gradle: 4.7
NDK: from local.properties: (not specified); latest from SDK: (not found);
LLDB: LLDB 3.1 (revision: 3.1.4508709)
CMake: from local.properties: (not specified); latest from SDK: 3.6.0-rc2; from PATH: (not found);
IMPORTANT: Please read