Status Update
Unfortunately the issue in Studio 2024.2.2 Canary 9 was destructive and removed information from the stored run configurations, even when just opening and closing the project.
We explored if this could be detected and automatically fixed, but unfortunately the end result is not unambiguously distinguishable from a manually edited run configuration and we didn't want to run the risk of any mitigation breaking things further or causing more confusion.
If you have a project with this issue, you can either
- delete the broken run configuration, and manually recreate it in the UI or
- delete it from the file system, which will trigger the automatic creation of the app run configurations that happen on first import.
- if you're using git with the default
.gitignore
closing the project, runninggit clean -fdx
- closing the project, removing all of the .idea folder
- if you're using git with the default
Comments
pu...@gmail.com <pu...@gmail.com> #2
Please re-assign to UX. It was a UX team request to make them appear this way.
They, however, are supposed to be black solid black in bound to a variable (I don't know why it is important).
to...@yahoo.com <to...@yahoo.com> #3
ze...@gmail.com <ze...@gmail.com> #4
Setting as P2 as it is a minor UX issue.
je...@google.com <je...@google.com>
st...@gmail.com <st...@gmail.com> #5
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Canary 1
- Android Gradle Plugin 8.8.0-alpha01
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
pa...@gmail.com <pa...@gmail.com> #6
Ran into the same issue and when I checked the Run Configuration it turned out Gradle-aware Make
was missing in "Before launch". Add it again or create a new Run Configuration and it should work
ka...@google.com <ka...@google.com> #7
Thank you for the report and for bringing this to our attention via various channels: indeed I can confirm after looking at
vm...@google.com <vm...@google.com>
r....@gmail.com <r....@gmail.com> #8
Additionally, any run configuration that is stored on the project, no longer shows up.
ka...@google.com <ka...@google.com> #9
If you want to try out a nightly version that includes the fix for this, then please try 2024.3.2 Nightly 2024-11-02
or above
otherwise, a fix will be included in the 2024.2.2 Beta 1
to be released soon
ni...@gmail.com <ni...@gmail.com> #10
Just tested with Android Studio Ladybug Feature Drop | 2024.3.2 Nightly 2024-11-02 and issue seems to be same. Open a project, make change to the code such as add or remove a function and run. It simply installs last build output instead of building and then installing
ka...@google.com <ka...@google.com> #11
If ths project was already opened in Canary9 then I am afraid the fix we have will not recover the previoous working state you had before upgrading to canary 9, but if your project wasn't opened with Cnary 9 then the transtion will be seamless.
ni...@gmail.com <ni...@gmail.com> #12
Thanks, it was opened in Canary 9. How does one recover it then?
ka...@google.com <ka...@google.com> #13
I am afraid we still haven't added a fix to automatically recover back to the state without requiring some efforts from you (it's currently WIP on our end), but for now you will have to basically do the same workaround suggested above by manually adding the Gradle-Aware-Make
to the beforeLaunch block of your RunConfig.
jo...@google.com <jo...@google.com>
ka...@google.com <ka...@google.com>
ka...@google.com <ka...@google.com> #14
The fix for this bug will be available in the 2024.2.2 Beta 1
release. Please note, that if you already opened your project using 2024.2.2 Canary 9
, you will unfortunately have to manually add the Gradle-aware Make
task to your Run Configuration (as shown below).
Apologies for this inconvenience, and thank you for bringing this to our attention.
an...@google.com <an...@google.com> #15
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Meerkat | 2024.3.1 Canary 1
- Android Gradle Plugin 8.9.0-alpha01
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
fl...@gmail.com <fl...@gmail.com> #16
Nope it is the same issue
fl...@gmail.com <fl...@gmail.com> #17
Pressing the play button doesn't even compile anymore... Like you can have non compilable code and see a deployment working successfully...
ka...@google.com <ka...@google.com> #18
Can you please elaborate on what do you mean by this is the same issueand confirm if this is happenin on a projec you previously opened with Canary 9 ?
fl...@gmail.com <fl...@gmail.com> #19
I tried with Android Studio Meerkat | 2024.3.1 Canary 1 and it also doesn't compile the project when you click on the play button. It only deploy to your device the previously compiled version, there is no written error but that's an error to me.
Like if you do a ./gradlew clean then click on the play button won't do anything as it won't be able to rebuild an apk to deploy.
ka...@google.com <ka...@google.com> #20
This is adifferent bug from what you are experiencing. Please file a bug and the team will take care of it. Thank you.
fl...@gmail.com <fl...@gmail.com> #21
ok I have created a new ticket there
en...@gmail.com <en...@gmail.com> #22
ka...@google.com <ka...@google.com> #23
Please refer to
cm...@google.com <cm...@google.com> #24
For context, unfortunately the issue in Studio 2024.2.2 Canary 9 was destructive and removed information from the stored run configurations, just from opening and closing the project.
We explored if this could be detected and automatically fixed, but unfortunately the end result is not unambiguously distinguishable from a manually edited run configuration and we didn't want to run the risk of any mitigation breaking things further or causing more confusion.
Other workarounds include
- deleting the broken run configuration, and manually recreating it in the UI
- if you're using git with the default
.gitignore
closing the project, runninggit clean -fdx
and reopening will remove all previous run configurations and trigger the automatic creation of the app run configurations that happen on first import. - closing the project, removing all of the .idea folder (that might contain some shared settings though) and reopen the project will trigger the automatic creation of the app run configurations
an...@google.com <an...@google.com> #25
The fixes for this issue are now also available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Beta 1
- Android Gradle Plugin 8.8.0-beta01
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
lb...@gmail.com <lb...@gmail.com> #26
@25 I have the next canary and it's still not fixed. How come?
Android Studio Meerkat | 2024.3.1 Canary 3
Build #AI-243.21565.193.2431.12691553, built on November 21, 2024
Runtime version: 21.0.5+-12651406-b631.16 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.awt.windows.WToolkit
Windows 11.0
Kotlin plugin: K2 mode
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 6144M
Cores: 16
Registry:
ide.instant.shutdown=false
ide.experimental.ui=true
i18n.locale=
ide.images.show.chessboard=true
Non-Bundled Plugins:
com.intellij.marketplace (243.21565.247)
cn.jxzhang.plugin.json-formatter (1.6)
Show As ... (1.0.3)
String Manipulation (9.14.1)
GenerateSerialVersionUID (3.0.3)
com.steve.plugins.autoscroll (1.1)
com.dethlex.numberconverter (2.1.1)
izhangzhihao.rainbow.brackets (2024.2.7-241)
com.developerphil.adbidea (1.6.19)
GenerateSerializationHelpers (1.0.6)
cn.yiiguxing.plugin.translate (3.6.7)
ko...@gmail.com <ko...@gmail.com> #27
If you've already opened a project with Ladybug Canary 9, you have to manually fix the problem. There's the solution and explanation in #14 and #24.
lb...@gmail.com <lb...@gmail.com> #28
@27 OK thanks.
cr...@gmail.com <cr...@gmail.com> #29
From
on 1/11/2024: issue 376707224
Probably duplicate of
an...@google.com <an...@google.com> #30
The fixes for this issue are now also available in:
- Android Studio Meerkat Feature Drop | 2024.3.2 Canary 3
- Android Gradle Plugin 8.10.0-alpha03
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
an...@google.com <an...@google.com> #31
Further fixes for this issue are now available in:
- Android Studio Meerkat | 2024.3.1 RC 1
- Android Gradle Plugin 8.9.0-rc01
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
an...@google.com <an...@google.com> #32
Further fixes for this issue are now available in:
- Android Studio Meerkat Feature Drop | 2024.3.2 Canary 4
- Android Gradle Plugin 8.10.0-alpha04
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
an...@google.com <an...@google.com> #33
Further fixes for this issue are now available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Patch 1
- Android Gradle Plugin 8.8.1
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Description
After upgrading from Ladybug Canary 8 to Canary 9, running my app (Shift+F10) does not automatically builds it anymore (if needed) first, which results in this error:
To be able to run it, I have to manually build it first (CTRL+F9). And this, each time I make a modification to the code.
Studio Build: Build #AI-242.23339.11.2422.12584204, built on October 31, 2024 Version of Gradle Plugin: 8.8.0-alpha09 Version of Gradle: 8.10.2 Version of Java: OS: Linux