Status Update
Comments
xa...@google.com <xa...@google.com> #2
Fixed by Change I26379e894.
ga...@google.com <ga...@google.com> #3
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 6
- Android Gradle Plugin 8.8.0-alpha06
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!
so...@google.com <so...@google.com> #4
We can start with supporting it as a Build selected app
/Build selected test
when the run configuration is either a one pointing referring to an app or we recognise it as a Gradle run configuration invoking a test. (i.e. with a dynamic title to avoid confusion).
If a different run configuration is selected, we don't know what build means and the user has an option to just run it.
so...@google.com <so...@google.com> #5
pa...@gmail.com <pa...@gmail.com> #6
I would like for that to happen on all transitive modules that are pulled into the given application target, but I can also understand why that might be scary for larger projects
xa...@google.com <xa...@google.com> #7
Yes we heard clear feedback that we shouldn't call assemble on all projects :)
We're planning to have more build options to provide better control. I think we may end up with such an action and you could always assign a shortcut to it if that's what you want.
ga...@google.com <ga...@google.com> #8
In Giraffe we changed the default action to be "Build selected module" (i.e the one you are currently editing or you have selected in the project view). You can still revert to "Build project" by changing the default action (as it is a split button).
ka...@google.com <ka...@google.com>
ka...@google.com <ka...@google.com> #9
this is now available in Android Studio Ladybug Feature Drop | 2024.2.2 Canary 4
an...@google.com <an...@google.com> #10
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 5
- Android Gradle Plugin 8.8.0-alpha05
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!
ub...@gmail.com <ub...@gmail.com> #11
The "new" AS/IJ UI does not have the "Make" button physically close to the Run/Debug buttons by default, I think. That makes its new behavior less intuitive.
ka...@google.com <ka...@google.com> #12
it's on the same toolbar, just after the first group of (run/debug/modify) options.
Description
To improve the build experience for Android developers let's add a new build option to "Build Run configuration". This will perform the same build actions as the "Run" button, except that it will not deploy the app.
Let's also make this the default build behavior by mapping it to the hammer/build icon in the top toolbar. Given how close the hammer/build button is to the "Run" button, most developers expect it to build what they are about to deploy, not the whole project. Developers who want to build the whole project will still be able to do that through the "Make Project" option in the build menu.