Status Update
Comments
il...@google.com <il...@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
va...@google.com <va...@google.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 :)
il...@google.com <il...@google.com> #4
lifecycle 2.8.0 is now stable but compose UI 1.7.0 is still in beta.
ra...@gmail.com <ra...@gmail.com> #5
Same problem here. Lifecycle 2.8.0
is now stable but Compose UI 1.7.0
is still beta. Of course our Dependabot didn't know about this relationship between dependencies 😬
il...@google.com <il...@google.com>
sa...@google.com <sa...@google.com>
ap...@google.com <ap...@google.com> #6
Something like that really shouldn't happen... 🤦🏻♂️
na...@google.com <na...@google.com> #7
Thats really really bad. I would always expect the latest stable versions to be compatible. Please add this requirement to the changelog or better add a warning at compile time if used with incompatible combinations.
Description
We can observe Lifecycle changes in a few different ways, but with Compose the most natural way would be via a
State<Lifecycle.State>
, which would make the currentLifecycle.State
automatically observable to Compose.