Closed jingibus closed 11 months ago
My colleague @gamepro65 ran into this issue in prod; coroutineContext.job.invokeOnCompletion has no well-defined dispatcher affinity, which means it can run anywhere. Doing this teardown within a coroutine should ensure consistent behavior.
coroutineContext.job.invokeOnCompletion
My colleague @gamepro65 ran into this issue in prod;
coroutineContext.job.invokeOnCompletion
has no well-defined dispatcher affinity, which means it can run anywhere. Doing this teardown within a coroutine should ensure consistent behavior.