Fixed
Status Update
No update yet.
Comments
ra...@google.com
Yigit, do you have time to fix it?
reemission of the same liveData is racy
reemission of the same liveData is racy
ra...@google.com
yea i'll take it.
ra...@google.com
Thanks for the detailed analysis. This may not be an issue anymore since we've started using Main.immediate there but I' not sure; I'll try to create a test case.
ap...@google.com
just emitting same live data reproduces the issue.
@Test
fun raceTest() {
val subLiveData = MutableLiveData(1)
val subject = liveData(testScope.coroutineContext) {
emitSource(subLiveData)
emitSource(subLiveData) //crashes
}
subject.addObserver().apply {
testScope.advanceUntilIdle()
}
}
@Test
fun raceTest() {
val subLiveData = MutableLiveData(1)
val subject = liveData(testScope.coroutineContext) {
emitSource(subLiveData)
emitSource(subLiveData) //crashes
}
subject.addObserver().apply {
testScope.advanceUntilIdle()
}
}
Description
Version used: 2.2.0+
Devices/Android versions reproduced on: All manufacturers/Android 6 and higher
Basically adding an empty List<OneTimeWorkRequest> to a chain will break the chain. Example:
workContinuation.beginWith(someJob).then(workList1).then(emptyWorkList).then(workList2)....enqeue
The chain completely stops executing work when it reaches the "emptyWorkList" part of the chain. There is NO error message. The chain sort of hangs in limbo after that. Expected behaviour should be that it ignores that part of the chain and proceeds to the next continuation, I think.