Status Update
Comments
ch...@jetbrains.com <ch...@jetbrains.com> #2
Note that the "Error loading build artifacts" error only happens if the project was cleaned or never built before. The general issue is that running the project never builds it first and you have to build it manually (as a workaround).
tn...@google.com <tn...@google.com> #3
joining this club as well....
I don't get the error described, but any source code changes are not reflected when I hit "Debug". I have to manually build first.
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: Windows 11
tn...@google.com <tn...@google.com> #4
I have the same issue and to see any changes I need to run twice the app
tn...@google.com <tn...@google.com> #5
I just filed
tn...@google.com <tn...@google.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
an...@google.com <an...@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
rv...@mozilla.com <rv...@mozilla.com> #8
Additionally, any run configuration that is stored on the project, no longer shows up.
tn...@google.com <tn...@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
js...@google.com <js...@google.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
js...@google.com <js...@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.
js...@google.com <js...@google.com> #12
Thanks, it was opened in Canary 9. How does one recover it then?
js...@google.com <js...@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.
an...@google.com <an...@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.
Description
Steps to reproduce
o -> o != null
.Expected result (correct result):
The inspection should not show, or invoking it should not use
Objects::nonNull
Actual result (faulty result):
Invoking the inspection replaces the lambda with
Objects::nonNull
, which raises an error because the method reference requires API level 24 or higher.Environment