If i have to use a state inside a lambda , do i always need to wrap it inside rememberUpdatedState? ...

# compose

[Prateek Kumar]

If i have to use a state inside a lambda , do i always need to wrap it inside rememberUpdatedState? Seems like too much but it dosen’t work properly without it and it is a hit and miss.
Am i missing something?
Ex:-

val image = rememberUpdatedState(mcqData.imageUrl)
GlideImage(imageModel = { image.value })

Or

val screenModeUpdated by rememberUpdatedState(screenMode)
LaunchedEffect(key1) {
    if (screenModeUpdated == ScreenMode.SELECTION_MODEL)
        viewModel.initMcqs(
}

[myanmarking]

is GlideImage a wrapper of yours ?

[Prateek Kumar]

No , it is part of this library

com.github.skydoves:landscapist-glide:2.1.9

[myanmarking]

i’m not familiar with that library. But since imageModel is a lambda and not a variable, it must certainly can be recomposed with a new value. What happens if you just use mcqData.imageUrl in the lambda ?

[Prateek Kumar]

if i use mcqData.imageUrl in the lambda , it sometime loads and sometimes it dosen’t . I feel the reason being mcqData.imageUrl is in my VM and that takes some tome to populate data, and the lambda tries to load image using the old url and not the updated one.

[myanmarking]

not likely. Are you sure the urls are valid? If there is some problem and the image cannot be loaded. It might be your problem there

[myanmarking]

if you use rememberUpdatedState it works as intended right ?

[Prateek Kumar]

I have checked them and they are valid , i even used Coil or Glide Compose(in alpha), and they work flawlessly

[Prateek Kumar]

Yes with rememberUpdatedState it works

[myanmarking]

even if the url is not state, the lambda should recompose. Maybe the library is doing something weird. Leave the rememberUpdatedState then. And maybe report a bug

[myanmarking]

well, it may be the case if only the url changes, compose will skip everything and not detect the change since the value is captured in the lambda. just use rememberUpdatedState and you will be fine

[Prateek Kumar]

But what is looks like every time we use a State inside a lambda ,We should always wrap it inside rememberUpdatedState or else it can pick the old value.

[Stylianos Gakis]

for image.value, how is that value written at the place where it’s created.
Is it val value by mutableStateOf()?

[Prateek Kumar]

It is inside my a data class in my VM as StateFlow , and in compose am using it using collectAsStateWithLifecycle().