Status Update
Comments
ja...@google.com <ja...@google.com> #2
To use
The issue is happening because, starting from LocalLifecycleOwner
has been moved from androidx.compose.ui
to lifecycle-runtime-compose
, as outlined in their respective release notes. For compatibility reasons, you must update both dependencies.
For context, note these changes were made to enable the utilization of its Compose-based helper APIs beyond Compose UI (such as in
If the issue persists even after updating your Compose UI, please let us know.
Edit: please see
tj...@gmail.com <tj...@gmail.com> #3
If this change has made both libraries version dependent, it seems that guide them to the release note so that users will not experience difficulties :)
ja...@google.com <ja...@google.com>
ap...@google.com <ap...@google.com> #4
lifecycle 2.8.0 is now stable but compose UI 1.7.0 is still in beta.
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.