A modern programming language that makes developers happier.

kotlinlang

Sometimes `remember` saved state is lost after screen is turned off and on. :thread:

```        var things by remember { mutableStateOf("") }
        TextField(
            value = things,
            onValueChange = { things = it }
        )```

as part of a screen that is registered in compose navigation.

when I turn screen off and on, sometimes the text field goes back to empty string, other times it doesnt.

I added a lifecycle observer to NavBackStackEntry and I found this:

```WHEN STATE IS LOST:
onStateChanged NavBackStackEntry@86ef65fd - ON_PAUSE
onStateChanged NavBackStackEntry@86ef65fd - ON_STOP &lt;-- Screen turn off
onStateChanged NavBackStackEntry@86ef65fd - ON_CREATE &lt;-- Screen turn on and text field state is lost
onStateChanged NavBackStackEntry@86ef65fd - ON_START
onStateChanged NavBackStackEntry@86ef65fd - ON_RESUME


WHEN STATE IS KEPT:
onStateChanged NavBackStackEntry@5be23c59 - ON_PAUSE
onStateChanged NavBackStackEntry@5be23c59 - ON_STOP &lt;-- Screen turn off
onStateChanged NavBackStackEntry@5be23c59 - ON_START &lt;-- Screen turn on and text field state is kept
onStateChanged NavBackStackEntry@5be23c59 - ON_RESUME```

If I call the composable directly, i.e without using navigation code, it doesn’t seem to happen. <@UJBPFB3SN> any idea?

If you want your state saved, you'd want to use `rememberSaveable`.

Got it yeah, I tried and that works indeed. I was just confirming that this was expected. It's kinda weird that it just happens when in a composable registered as a destination in NavHost

Anyway, thanks for quick reply. I will pass this feedback to the person that actually asked me

I am also curious about this use-case. Why would using navigation cause this unexpected behaviour change ?
<https://kotlinlang.slack.com/archives/CJLTWPH7S/p1651691517906359?thread_ts=1651691130.284029&amp;cid=CJLTWPH7S>
<https://kotlinlang.slack.com/archives/CJLTWPH7S/p1651692124686329?thread_ts=1651691130.284029&amp;cid=CJLTWPH7S>