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

Since this is happening in Tink, rather than in the AndroidX library, it would be best to open an issue with that project, as there isn't an easy way for us to fix this.

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

@2 I don't know what "Tink" is, but here, created:

https://github.com/google/tink/issues/534

Would this mean that this bug report should be written there as well:

https://issuetracker.google.com/issues/176215143
?

il...@google.com <il...@google.com> #4Dec 9, 2021 12:15AM

Tink is the library that does the heavy lifting in Jetpack Security.

And yes, potentially raising that issue with the Tink team directly could help.

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

@4 Well why didn't Google offer it there? Crashes are far more important than warning logs...
Here, created it there too:

https://github.com/google/tink/issues/535

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.

Anyone here solved the issue? I have implemented the jetpack security and got the same crashes.

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

same warning