Status Update
No update yet.
Comments
il...@google.com
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
ha...@googlemail.com
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
lifecycle 2.8.0 is now stable but compose UI 1.7.0 is still in beta.
bo...@gmail.com
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
Something like that really shouldn't happen... 🤦🏻♂️
lb...@gmail.com
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
Library version: 1.0.0-alpha03
When setting a new NavGraph to NavController, the back stack is not resetted.
From the documentation, "Any current navigation graph data will be replaced."
If a NavGraph is already setted then the back stack containts the default destination. In calling NavGraph.setGraph(NavGraph) and in the new graph, the destination is different, then the new destination is not displayed because back stack is not resetted.
Is it expected feature or not?