Add Compose-observable State<Lifecycle.State> for current Lifecycle state [209684871]

Fixed

Feature Request

Status Update

No update yet.

Description

va...@google.com

created issue #1

Dec 7, 2021 11:27PM

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 current Lifecycle.State automatically observable to Compose.

Comments

il...@google.com <il...@google.com> #2Dec 7, 2021 11:42PM

To use Lifecycle 2.8.0-alpha03, ensure you are using at least Compose UI 1.7.0-alpha05.

The issue is happening because, starting from Lifecycle 2.8.0-alpha03 and Compose UI 1.7.0-alpha05, 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 Molecule). Further information can be found at b/328263448.

If the issue persists even after updating your Compose UI, please let us know.

Edit: please see https://issuetracker.google.com/336842920#comment8 for a workaround.

va...@google.com <va...@google.com> #3Dec 8, 2021 12:34AM

Thanks for your answer.
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> #4Dec 9, 2021 12:15AM

lifecycle 2.8.0 is now stable but compose UI 1.7.0 is still in beta.

ra...@gmail.com <ra...@gmail.com> #5Dec 24, 2021 04:23AM

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> Sep 12, 2022 11:53PM

Assigned to sa...@google.com.

sa...@google.com <sa...@google.com> Mar 14, 2023 08:18PM

Accepted by sa...@google.com.

ap...@google.com <ap...@google.com> #6Mar 15, 2023 11:08PM

Marked as fixed.

Something like that really shouldn't happen... 🤦🏻‍♂️

na...@google.com <na...@google.com> #7Jul 26, 2023 05:21PM

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.