Fixed
Status Update
No update yet.
Comments
mg...@google.com
ap...@google.com
Update: I was able to downgrade to 32.1.10 and I can confirm it's smooth again. The issue is indeed in emulator version 33.1.1
na...@google.com
It's happening to me too and I also confirm that reverting to 32.1.10 fixes the issue.
We should have an easier way of reverting versions. AS should allow picking the version similarly to how we already do for the other tools in SDK manager.
We should have an easier way of reverting versions. AS should allow picking the version similarly to how we already do for the other tools in SDK manager.
pr...@google.com
Hi,
would you try to turn on hardware GPU rendering (instead of auto GPU) and see if it fixes this issue?
would you try to turn on hardware GPU rendering (instead of auto GPU) and see if it fixes this issue?
Description
Currently
lifecycle-viewmodel-composeare depending oncompose-uiincommonMain. The dependency is only used inandroidMain.This dependency brings alot of code for projects aiming to use Compose Runtime only, for example Redwood. At Voyager the Core and Navigator modules only depend on Compose Runtime, by adding the support for ViewModel to KMP projects with Voyager would bring the hole
compose-ui.The solution here is just move the
compose-uidependency toandroidMain.