Fixed
Status Update
Comments
ja...@google.com <ja...@google.com> #2
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
tj...@gmail.com <tj...@gmail.com> #3
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.
ja...@google.com <ja...@google.com>
ap...@google.com <ap...@google.com> #4
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
The Transition Kotlin extensions target the Framework Transition class which is a bit confusing, as most framework classes are being deprecated in favor of their AndroidX counterparts, Fragments for example.
As it stands, the KTX libraries for Transitions cannot be used with androidx.transition.AutoTransition. Does this mean android.transition.Transition should be used over androidx.transition.AutoTransition?
Thanks.