Status Update
Comments
cl...@google.com <cl...@google.com>
ni...@google.com <ni...@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
jl...@google.com <jl...@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 :)
ni...@google.com <ni...@google.com> #4
lifecycle 2.8.0 is now stable but compose UI 1.7.0 is still in beta.
ni...@google.com <ni...@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 😬
[Deleted User] <[Deleted User]> #6
Something like that really shouldn't happen... 🤦🏻♂️
Description
compose-ui
triggers a security alert as it imports inspector.jar which containsprotobuf-javalite:3.19.4
. Please upgrade the version ofprotobuf-javalite
to at least 3.19.6.Jetpack Compose version: 1.3.0
Jetpack Compose component(s) used: compose-ui
Steps to Reproduce or Code Sample to Reproduce:
Stack trace (if applicable):