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
f....@gmail.com <f....@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 :)
f....@gmail.com <f....@gmail.com> #4
lifecycle 2.8.0 is now stable but compose UI 1.7.0 is still in beta.
il...@google.com <il...@google.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 😬
ap...@google.com <ap...@google.com> #6
Something like that really shouldn't happen... 🤦🏻♂️
Description
Component: navigation-compose 1.0.0-alpha08
Hi there, I am trying to migrate to the Compose flavour of Navigation, and working with the
NamedNavArgument
class. I'd like to be able to retrieve the name that I passed in to thenavArgument()
function, but it's a bit hard because thename
field is private inNamedNavArgument
.Can you please make this field public? Since the class is basically an immutable data class, it seems natural to be able to access its fields publicly.