Assigned
Status Update
No update yet.
Comments
li...@gmail.com
Hey, sorry for coming back to this so late. We've never seen this. Without any repro steps it's going to be hard to do anything about it.
We've some cases where the Gradle daemon gets started but Studio cannot connect to it and the Studio side Gradle code handling connection to the daemon will keep spawning new ones if the connection does not get established. In this instance though the fact that the build window shows all these daemon running means that this is a different problem.
ca...@gmail.com
Hello, I had the issue reproduce on first project open after upgrading Android Studio from JetBrains Toolbox. Note that the project has a buildSrc.
I think you can reproduce it with the same steps if nothing changed since Arctic Fox alpha 08.
Description
When integrating Compose into an application using one-fragment per screen (our current recommendation), a natural coding pattern is to host the ViewModel in the Fragment and pass it through the composition tree.
This follows our guide to app architecture approach to managing screens and also allows for common DI patterns.
However, there are often animations in the top of the tree for enter/exit, and the lack of @Stable treatment for ViewModel causes excessive recomposition.
It would be preferred consider ViewModel as stable.
Related: