Status Update
Comments
jo...@google.com <jo...@google.com>
tn...@google.com <tn...@google.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
rv...@mozilla.com <rv...@mozilla.com> #4
I have the same issue and to see any changes I need to run twice the app
rv...@mozilla.com <rv...@mozilla.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
tn...@google.com <tn...@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
an...@google.com <an...@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
rv...@mozilla.com <rv...@mozilla.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.
Description
With the AGP 8.8.0 alpha builds, we're seeing new ObsoleteSdkInt warnings that seem spurious. Our project is built with minSdkVersion = 21, targetSdkVersion = 34, and compileSdkVersion = 35.
I'm not sure if it's the TargetApi annotation that's tripping things up, but my understanding is there's nothing preventing this code from running on older API levels and the code is valid as-written.