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?

whats that lambda after collect? doesnt seem right

It's just a log statement atm

does that code compile?

Yes

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

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

try GlobalScope just to prove

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

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

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

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

The objects aren't equal