Hey, any idea why would a

.collect {}

call of a

MutableStateFlow

not work after the initial value? Basically, I create a

MutableStateFlow

in one place and call

emit

(multiple times) there, and at the same time call

.collect {}

in another place, and the callback of

collect

is not executed, except for the initial value. I can clearly see the state of the

Flow

is changing, but

collect

is just not working. I'm also absolutely sure the

collect

call is not getting canceled, as I have tried catching

CancellationException

. The context is a Jetpack Compose app, maybe it's some bug there? SOLVED: the problem was emitting the same list to the StateFlow. Even though the list is changing, its reference has not, and coroutines treat it as the same value, and concludes no new value needs to be emitted. Hence

collect

callback is not called after the initial value.

Is there any reason not to use

mutableStateFlow.value = newValue

instead of

emit()

?

Maybe your dispatcher is busy. Hard to guess without any code. Is there any runBlocking involved?

I want to listen to changes in the StateFlow to update UI accordingly. .collectAsState() doesn't work because.collect{} doesn't work

emit()

is a suspend function and it needs dispatching so there may be some timing issues. That's why I asked you why you are using the suspend function to update the value.

Ok, i'm gonna try

.value =

True.

Is there a way to change this behavior to use a different equality?

Using

MutableList

as state is suspicious and error-prone. You should always use immutable

List

as state.

yes i understand that now