Can't Repro
Status Update
No update yet.
Comments
uc...@google.com
Thank you for this feedback. The team may reach out for more information on triaging or reproducing this issue.
[Deleted User] <[Deleted User]>
Looks like the issue is present on Android Studio 2.3.1 on MacOS as well. Full rebuild every time is really painful for large project !
my workaround: run gradlew from command line, ie: ./gradlew :moduleName:assembleDebug
my workaround: run gradlew from command line, ie: ./gradlew :moduleName:assembleDebug
uc...@google.com
Thanks for the feedback. We are sorry it took so long for us to get to this report. We would really appreciate it if you could confirm that this is still an issue for you and if so we will route it to the right team.
For information of what’s needed in the report please don’t forget to read this guide athttps://developer.android.com/studio/report-bugs
For information of what’s needed in the report please don’t forget to read this guide at
an...@google.com
Our team had requested additional information for this issue which was not provided within 30 days. Unfortunately there is not enough information for us to proceed and this issue is now closed.
In the future, if you encounter this or any other issue, please readhttps://developer.android.com/studio/report-bugs.html and file a new bug report with all the required information. This will help ensure the team can correctly triage, reproduce, and resolve your issue.
Thank you!
In the future, if you encounter this or any other issue, please read
Thank you!
Description
Let the project open up fully and open up the Gradle projects panel (see "Fnord Gradle projects"). Navigate to the :app->help->dependencies task and double-click on it. Make sure you toggle the text mode in the Run window.
Note that it will run dependencies on the Root project, displaying "No configurations". See "Fnord task run 1".
Without closing this project, open up a new project in a new window; this is project Foobar.
Go back to Fnord and re-run dependencies.
It should show the dependencies for Fnord app:dependencies (see "Fnord task run 2").
Close Fnord and switch to Foobar: no module tasks can be run; it appears to be running the task in the Root project context. Re-Open Fnord and Foobar module tasks run correctly again.
Running Gradle or Gradle Wrapper from the Terminal window or a separate shell window, passing "app:dependencies" works as expected. It is only when running the task through Android Studio that this is a problem.
Also note that running Fnord:app [dependencies] from the configuration drop-down in the Android Studio menu behaves the same.
Note that if you run any other submodule tasks, it is as if you are running them on the Root project, not the module. So, for larger projects with lots of dependencies you may end up building the entire project when you just want to build one module and its dependencies.
The workaround is to always have at least two Android Studio windows open.
Android Studio:
Version 2.2.3 AMD64 on Windows 10 using whatever JRE it wants to use, which appears to be a bundled OpenJSDK 1.8.0_76. See AboutBox.png.
Gradle:
PS C:\rd\experiments\trunk\Fnord> .\gradlew.bat --version
------------------------------------------------------------
Gradle 2.14.1
------------------------------------------------------------
Build time: 2016-07-18 06:38:37 UTC
Revision: d9e2113d9fb05a5caabba61798bdb8dfdca83719
Groovy: 2.4.4
Ant: Apache Ant(TM) version 1.9.6 compiled on June 29 2015
JVM: 1.8.0_101 (Oracle Corporation 25.101-b13)
OS: Windows 10 10.0 amd64
(Though I can reproduce with any version of the Gradle Wrapper.)