IssueTracker

As a workaround I created this function utilizing produceState():

@Composable
fun currentLifecycleState(): State<Lifecycle.State> {
    val lifecycleOwner = LocalLifecycleOwner.current

    return produceState(
        initialValue = Lifecycle.State.INITIALIZED,
    ) {
        val observer = object : DefaultLifecycleObserver {

            override fun onCreate(owner: LifecycleOwner) {
                value = owner.lifecycle.currentState
            }

            override fun onStart(owner: LifecycleOwner) {
                value = owner.lifecycle.currentState
            }

            override fun onResume(owner: LifecycleOwner) {
                value = owner.lifecycle.currentState
            }

            override fun onPause(owner: LifecycleOwner) {
                value = owner.lifecycle.currentState
            }

            override fun onStop(owner: LifecycleOwner) {
                value = owner.lifecycle.currentState
            }

            override fun onDestroy(owner: LifecycleOwner) {
                value = owner.lifecycle.currentState
            }
        }

        lifecycleOwner.lifecycle.addObserver(observer)
        awaitDispose { lifecycleOwner.lifecycle.removeObserver(observer) }
    }
}

Is there a target API version where this may be released?

This is still in progress for inclusion in Lifecycle 2.7.0-alpha01.

When will this be released?

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.lifecycle:lifecycle-runtime-compose:2.7.0-alpha01

Just want to say that Lifecycle 2.7.0 stable has been finally released. Thank you very much 🙏🏼

Yes, those are the Lifecycle.States that reflect those particular Lifecycle.Events. Please take a look at the Lifecycle guidance for more details.

Receiving a state from the flow would be the signal that a change has occurred and the new state is that particular change. There are cases where you don't care how you get to a state, just that you are there. We also offer LifecycleEffects to assist with use cases for Lifecycle.Events.

If you look at the release notes, you'll find two separate sections - one on Lifecycle Events (where you can use Lifecycle.asFlow() to get a Flow of Lifecycle.Event) and one for Lifecycle State (where you can use Lifecycle.currentStateFlow to get the current Lifecycle.State).

Make sure you are using the right API.

Lifecycle.asFlow() works outside of Compose too and gives you Lifecycle.Event instances as they occur. That's why that API exists separately from currentStateFlow.