Fixed
Status Update
No update yet.
Comments
uc...@google.com
vs...@google.com
ra...@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
li...@bytedance.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
po...@gmail.com
FYI theese are the AS related applications running during theese hours...
[Deleted User] <[Deleted User]>
Saving project and restarting AS solved the problem so far...
tn...@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
[Deleted User] <[Deleted User]>
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
tn...@google.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
[Deleted User] <[Deleted User]>
Sorry typo above, it was AS 3.2 Canary 3, not AS 3.1 Canary 9...
RG
RG
[Deleted User] <[Deleted User]>
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
[Deleted User] <[Deleted User]>
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
tn...@google.com
Reproducible steps from
[Deleted User] <[Deleted User]>
Does this error also happen against any of the 3.1 Beta builds?
[Deleted User] <[Deleted User]>
Can reproduce on 3.1 beta 4
tn...@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).
to...@gmail.com
This bug still exists on Build: 3.2 Canary 4, AI-173.4615518, 201802220212.
RG
RG
al...@gmail.com
Yes, the fix was not included on 3.2 Canary 4 nor 3.1 beta 4. Next release will include it.
p....@radio.net
Yes, the fix will be available in Studio 3.1 RC1.
ko...@gmail.com
I suppose (as mentioned above) that AS 3.2 Canary 5+ will get it, not only the AS 3.1 path ?
ji...@gmail.com
Error still occures in AS Build: 3.2 Canary 5.
Additional IDE error occured:
===
No message
com.intellij.openapi.externalSystem.model.ExternalSystemException:
at org.jetbrains.plugins.gradle.service.execution.GradleExecutionHelper.execute(GradleExecutionHelper.java:217)
at com.android.tools.idea.gradle.project.build.invoker.GradleTasksExecutorImpl.invokeGradleTasks(GradleTasksExecutorImpl.java:394)
at com.android.tools.idea.gradle.project.build.invoker.GradleTasksExecutorImpl.run(GradleTasksExecutorImpl.java:163)
at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:713)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$1(CoreProgressManager.java:157)
at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:543)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:488)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:94)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:144)
at com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:165)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:315)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
===
was automatic reported.
RG
Additional IDE error occured:
===
No message
com.intellij.openapi.externalSystem.model.ExternalSystemException:
at org.jetbrains.plugins.gradle.service.execution.GradleExecutionHelper.execute(GradleExecutionHelper.java:217)
at com.android.tools.idea.gradle.project.build.invoker.GradleTasksExecutorImpl.invokeGradleTasks(GradleTasksExecutorImpl.java:394)
at com.android.tools.idea.gradle.project.build.invoker.GradleTasksExecutorImpl.run(GradleTasksExecutorImpl.java:163)
at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:713)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$1(CoreProgressManager.java:157)
at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:543)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:488)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:94)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:144)
at com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:165)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:315)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
===
was automatic reported.
RG
ke...@gmail.com
Thanks RG for letting us know!
I just checked the builds and unfortunately 3.2 canary 5 (build 173.4630681) does not include this fix yet. 3.2 Canary 6 will include it.
I just checked the builds and unfortunately 3.2 canary 5 (build 173.4630681) does not include this fix yet. 3.2 Canary 6 will include it.
[Deleted User] <[Deleted User]>
Confirming that fix is in Build: 3.2 Canary 6, and seems to work well !!
Thank you ! :D
RG
Thank you ! :D
RG
km...@gmail.com
Same here with onNewIntent, apparently since upgrading appcompat from 1.6.0 to 1.6.1
Using Kotlin 1.8.0
Android Studio Electric Eel | 2022.1.1 Patch 1
Build #AI-221.6008.13.2211.9514443, built on January 20, 2023
Runtime version: 11.0.15+0-b2043.56-8887301 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 6.1.12-x64v3-xanmod1
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 20
Registry:
external.system.auto.import.disabled=true
ide.text.editor.with.preview.show.floating.toolbar=false
Current Desktop: ubuntu:GNOME
pa...@outlook.com
Can confirm that this 6yo bug has resurfaced.
I am also using AS Electric Eel Patch 1, this version has been the most unstable and bug ridden "stable" version of Android Studio so far, it is insane.
rb...@gmail.com
Facing the same issue while using onNewIntent
Android Studio Electric Eel | 2022.1.1 Patch 2 Build #AI-221.6008.13.2211.9619390, built on February 17, 2023 Runtime version: 11.0.15+0-b2043.56-8887301 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. Linux 5.19.0-35-generic GC: G1 Young Generation, G1 Old Generation Memory: 2048M Cores: 8 Registry: external.system.auto.import.disabled=true ide.text.editor.with.preview.show.floating.toolbar=false
Non-Bundled Plugins: wu.seal.tool.jsontokotlin (3.7.4) com.intellij.marketplace (221.6008.18) zielu.gittoolbox (500.0.4+213) izhangzhihao.rainbow.brackets (2023.2.6-ij) com.suusan2go.kotlin-fill-class (1.0.17)
Current Desktop: ubuntu:GNOME
ac...@gmail.com
Also facing the same issue on:
Android Studio Dolphin | 2021.3.1
Build #AI-213.7172.25.2113.9014738, built on August 31, 2022
Runtime version: 11.0.13+0-b1751.21-8125866 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Android Studio Dolphin | 2021.3.1
Build #AI-213.7172.25.2113.9014738, built on August 31, 2022
Runtime version: 11.0.13+0-b1751.21-8125866 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
zh...@gmail.com
Comment has been deleted.
le...@gmail.com
Editor showing error on super call for onNewIntent in Electric EEL 2022.1.1 Patch 2. Have upgraded to Build #AI-222.4459.24.2221.10121639, built on May 12, 2023 and still showing error.
co...@gmail.com
I'm still seeing this in Giraffe:
Android Studio Giraffe | 2022.3.1 Patch 2 Build #AI-223.8836.35.2231.10811636, built on September 14, 2023 Runtime version: 17.0.6+0-17.0.6b829.9-10027231 x86_64
do...@gmail.com
Still the same with onNewIntent.
Android Studio Giraffe | 2022.3.1 Patch 2 Build #AI-223.8836.35.2231.10811636, built on September 15, 2023 Runtime version: 17.0.6+0-b2043.56-10027231 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. Windows 10 10.0 GC: G1 Young Generation, G1 Old Generation Memory: 1280M Cores: 12 Registry: external.system.auto.import.disabled=true ide.text.editor.with.preview.show.floating.toolbar=false
Non-Bundled Plugins: com.intellij.ideolog (222.1.0.0) com.knziha.vectorpathtweaker (1.9.1) Statistic (4.2.7) com.thoughtworks.gauge (223.7571.182) com.moxun.plugin.s2v (1.9.2)
do...@gmail.com
The bug here is wider. Lint is wrongfully integrating dependencies from all gradle build scripts from the modules. This is the same bug as in my question and answer
sw...@gmail.com
Same here with Android Studio Hedgehog | 2023.1.1
Build #AI-231.9392.1.2311.11076708, built on November 10, 2023
Runtime version: 17.0.7+0-17.0.7b1000.6-10550314 aarch64
Build #AI-231.9392.1.2311.11076708, built on November 10, 2023
Runtime version: 17.0.7+0-17.0.7b1000.6-10550314 aarch64
gi...@gmail.com
Still happens on
Android Studio Hedgehog | 2023.1.1
Build #AI-231.9392.1.2311.11076708, built on November 9, 2023
Runtime version: 17.0.7+0-17.0.7b1000.6-10550314 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
This warning is shown on onNewIntent override method
Android Studio Hedgehog | 2023.1.1
Build #AI-231.9392.1.2311.11076708, built on November 9, 2023
Runtime version: 17.0.7+0-17.0.7b1000.6-10550314 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
This warning is shown on onNewIntent override method
gm...@googlemail.com
Still happens on
Android Studio Iguana | 2023.2.1 Patch 1
Build #AI-232.10300.40.2321.11567975, built on March 13, 2024
Runtime version: 17.0.9+0-17.0.9b1087.7-11185874 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Shown on onNewIntent method
Android Studio Iguana | 2023.2.1 Patch 1
Build #AI-232.10300.40.2321.11567975, built on March 13, 2024
Runtime version: 17.0.9+0-17.0.9b1087.7-11185874 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Shown on onNewIntent method
Description
AI-171.4333198, JRE 1.8.0_152-release-915-b01x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.12.4 unknown, screens 1440x900, 1920x1080; Retina
Kotlin plugin: 1.1.50
Code:
open class TestActivity : KotlinBaseActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
}
}
KotlinBaseActivity in AAR(maven)
Alway tips "Overriding method should call super.onCreate".