Hi all, I have a very strange problem with my `LazyColumn`. I am updating the menuList `State` in th...

# compose

[Mike Speed]

Hi all, I have a very strange problem with my LazyColumn. I am updating the menuList State in the ViewModel, the view recomposes but the debugger gets to LazyColumn and then stops, which means the children aren’t redrawn with the new data. Any ideas why? Thanks!

MyView:

val menuList = viewModel.menuData.observeAsState()

LazyColumn() {
                items(menuList.value.size) { i->
                    MenuItem(menuList.value[i])
                }
}

MyViewModel:

private var menu: MenuUiState? = null
val menuData: SingleLiveEvent<MenuUiState> by lazy { SingleLiveEvent() }

// ...
menu?.sections?.forEach {
    //update menu properties here
}
menuData.value = menu?.copy()

[Lokik Soni]

check your menuList size in log

[Mike Speed]

the data is definitely there. the debugger doesn’t even get to the items(){} line to check the size

[Colton Idle]

I've had a ton of issues with compose + debugger. It's anecdotal at this point but I have been recluded to using logs instead of debugger in my compose apps.

[Mike Speed]

I also tried that.. nothing after LazyColumn() { is printed

[Adrijan Rogan]

You can try using items(menuList.value) or itemsIndexed(menuList.value) if you really need indices.

[Adrijan Rogan]

The state has changed, but if the size does not change, I believe your items block will not be executed.