Fixed
Status Update
No update yet.
Comments
uc...@google.com
Found suddenly that this process has run for 3 hours !!
Shouldn't AS tell me that another builds was going on ?
By the way, it has never run for 3 hours before...
RG
Shouldn't AS tell me that another builds was going on ?
By the way, it has never run for 3 hours before...
RG
rp...@google.com
Thinking back for three hours, I may have tried to stop the build process by clicking on the gray x behind "Gradle bulding..." message on the AS status bar. All seemed OK then...
RG
RG
je...@google.com
ga...@google.com
FYI theese are the AS related applications running during theese hours...
jf...@3rdeyecam.com
Saving project and restarting AS solved the problem so far...
ga...@google.com
Breaktrhrough !!
If you try to stop the build process when app:transformDexWithInstantRunSlicesApkForDebug is executing, the build will "hang" in "Execute transform". The AS statusbar might show "Gradle build finished in xxs yyyms.
To remedy this situation and do a recompile, you need to restart AS.
See picture of situation.
RG
If you try to stop the build process when app:transformDexWithInstantRunSlicesApkForDebug is executing, the build will "hang" in "Execute transform". The AS statusbar might show "Gradle build finished in xxs yyyms.
To remedy this situation and do a recompile, you need to restart AS.
See picture of situation.
RG
ga...@google.com
How to reproduce:
1. Start building your project ("F10" or "Play button on action bar" or "Run -> Run App")
2. "You discovered an error in your code, and want to stop the build process".
3. Open your Build window, and show the processes ( not the log ).
3. Let the build process reach at least ":app:transformDexWithInstantRunSlicesApkForDebug"
4. Stop the build process by clicking the gray "cancel" button on far right of the status bar (x) (showing the build progress). See picture "notstopped_01"
5. The status bar shows "Stopping - Gradle Build Running". See picture "notstopped_02"
6. After a while the status bar shows nothing in the status bar in the middle, to the right the progressbar is disappeared and to the left following message is shown "Gradle build finished". See picture "notstopped_03"
7. The "task list" still shows that the process is running ":app:transformDexWithInstantRunSlicesApkForDebug".
8. If you try to Run the app again with "Run -> Run App " it will not build or start.
Build log also attached.
RG
1. Start building your project ("F10" or "Play button on action bar" or "Run -> Run App")
2. "You discovered an error in your code, and want to stop the build process".
3. Open your Build window, and show the processes ( not the log ).
3. Let the build process reach at least ":app:transformDexWithInstantRunSlicesApkForDebug"
4. Stop the build process by clicking the gray "cancel" button on far right of the status bar (x) (showing the build progress). See picture "notstopped_01"
5. The status bar shows "Stopping - Gradle Build Running". See picture "notstopped_02"
6. After a while the status bar shows nothing in the status bar in the middle, to the right the progressbar is disappeared and to the left following message is shown "Gradle build finished". See picture "notstopped_03"
7. The "task list" still shows that the process is running ":app:transformDexWithInstantRunSlicesApkForDebug".
8. If you try to Run the app again with "Run -> Run App " it will not build or start.
Build log also attached.
RG
jf...@3rdeyecam.com
In AS 3.1 Canary 9:
Starting Build First time. Stopping Build First time, same result as above (except pt 8.).
Starting Build Second time. New process is made, launching a process window showing both the "running" process (which is really stopped) and the new one.
Let the Second Build run out, and seems that this one is launched, but the first is still "running".
See picture.
RG
Starting Build First time. Stopping Build First time, same result as above (except pt 8.).
Starting Build Second time. New process is made, launching a process window showing both the "running" process (which is really stopped) and the new one.
Let the Second Build run out, and seems that this one is launched, but the first is still "running".
See picture.
RG
ga...@google.com
Sorry typo above, it was AS 3.2 Canary 3, not AS 3.1 Canary 9...
RG
RG
ga...@google.com
Checking further down the line:
It is not necessary to stop the process at pt 3. int the reproduce description above. You could try to stop the process in any step, and process window shows "running" process still.
If you start and stops subsequently, more "processes are made", and I cannot say they will influence each other.
Restarting AS still seems to remedy the situation though.
RG
It is not necessary to stop the process at pt 3. int the reproduce description above. You could try to stop the process in any step, and process window shows "running" process still.
If you start and stops subsequently, more "processes are made", and I cannot say they will influence each other.
Restarting AS still seems to remedy the situation though.
RG
jf...@3rdeyecam.com
ga...@google.com
Reproduced in
Android Studio 3.2 Canary 2
Build #AI-173.4591728, built on February 7, 2018
JRE: 1.8.0_152-release-1024-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.9.0-5-amd64
Android Studio 3.2 Canary 2
Build #AI-173.4591728, built on February 7, 2018
JRE: 1.8.0_152-release-1024-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.9.0-5-amd64
jf...@3rdeyecam.com
Reproducible steps from
ga...@google.com
Does this error also happen against any of the 3.1 Beta builds?
jf...@3rdeyecam.com
Can reproduce on 3.1 beta 4
ga...@google.com
Thanks for finding this issue! The problem is that the build view does not get a finish event when the build is cancelled, causing any running task to appear as it is still running, even if it is not.
The fix for this issue will show any pending task as skipped when the build is cancelled (see attached image).
The fix for this issue will show any pending task as skipped when the build is cancelled (see attached image).
jf...@3rdeyecam.com
This bug still exists on Build: 3.2 Canary 4, AI-173.4615518, 201802220212.
RG
RG
ga...@google.com
Yes, the fix was not included on 3.2 Canary 4 nor 3.1 beta 4. Next release will include it.
ga...@google.com
Yes, the fix will be available in Studio 3.1 RC1.
jf...@3rdeyecam.com
I suppose (as mentioned above) that AS 3.2 Canary 5+ will get it, not only the AS 3.1 path ?
Description
Android Plugin Version: 3.2.0-alpha02
Module Compile Sdk Version: 27
Module Build Tools Version: 27.0.3
Android SDK Tools version: 26.1..1
The CI installation of the Android SDK works with the 3.1.0-alpha04 plugin, but does not with the 3.2.0-alpha02. I haven't tested the intermediate plugin versions to see where it breaks.
I downloaded the standalone tools and then ran the following:
./sdkmanager "add-ons;addon-google_apis-google-21" "add-ons;addon-google_apis-google-22" "add-ons;addon-google_apis-google-23" "add-ons;addon-google_apis-google-24" "build-tools;27.0.3" "extras;android;m2repository" "extras;google;google_play_services" "extras;google;m2repository" "extras;m2repository;com;android;support;constraint;constraint-layout-solver;1.0.2" "extras;m2repository;com;android;support;constraint;constraint-layout;1.0.2" "platforms;android-21" "platforms;android-22" "platforms;android-23" "platforms;android-24" "platforms;android-25" "platforms;android-26" "system-images;android-21;google_apis;x86" "system-images;android-22;google_apis;x86" "system-images;android-23;google_apis;x86" "system-images;android-24;google_apis;x86" "system-images;android-25;google_apis;x86" "system-images;android-26;google_apis;x86" "platforms;android-27" "system-images;android-27;google_apis;x86"
Using an SDK that was installed using Android Studio works just fine.
The error is:
:app:compileReleaseJavaWithJavacFatal Error: Unable to find package java.lang in classpath or bootclasspath
FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:compileReleaseJavaWithJavac'.
> Compilation failed; see the compiler error output for details.