Hi guys, I have a weird one ``` fun <T> L...

# coroutines

[dan.the.man]

Hi guys, I have a weird one

fun <T> LifecycleOwner.stateFlow(stateFlow: StateFlow<T>, funCollect: (T) -> Unit) {
        lifecycleScope.launchWhenStarted {
            stateFlow.collect() {
                funCollect(it)
            }
        }
    }

Is how I subscribe to a Stateflow. I then subscribe to that in my fragment. However, very infrequently, my Stateflow doesn't emit.

Timber.d(//This log is hit)
            model.data.emit(result)

The log above is hit, in theory I would think it should have emit, but for some reason, my subscription is never hit in my fragment. The correct object is being pushed to/observed, not sure what's happening, any thoughts?

[ursus]

whats that lambda after collect? doesnt seem right

[dan.the.man]

It's just a log statement atm

[ursus]

does that code compile?

[dan.the.man]

Yes

[ursus]

oh yea the () is optional lol, nevermind ..

[ursus]

I'd venture the lifecyclescope can be busted, or, since emit is suspending its scope can ran out

[ursus]

and also, since its a mutable flow, it only passes through distinct values (it does a == check inside)

[dan.the.man]

Yup. The values are different that are being passed, the lifecyclescope being dead would explain it, but there's no reason it should be

[ursus]

try GlobalScope just to prove

[dan.the.man]

I did a CoroutineScope(DIspatchers.Main().launch and same issue, still sometimes not receiving updates

[ursus]

did you keep it as a field? if not it might get garbage collected

[dan.the.man]

The stateflow is a member variable, so I'd think the function would be kept there

[Ryan Rolnicki]

What is T? If you emit an object that 'equals' the previous value it won't actually do anything.,

[Ryan Rolnicki]

Here's an example:

https://pl.kotl.in/OXQVvI06w

[dan.the.man]

The objects aren't equal