Javier
01/21/2021, 10:01 PMfilterNotNull a MutableStateFlow and keep returning a StateFlow instead of a Flow? It is forcing me to add an stateIn to retransform the Flow into StateFlowGuillermo Alcantara
01/21/2021, 10:05 PMJavier
01/21/2021, 10:12 PMstateInIan Lake
01/21/2021, 10:12 PMStateFlow is that it has always has a value. If your upstream MutableStateFlow only emits null, then filterNotNull never emits anything. That's why you need to use stateIn() to either set an initialValue (so that your StateFlow actually has a value ) or use the suspend stateIn that suspends until the first value is emittedJavier
01/21/2021, 10:14 PMstateIn is what I was imagining