Fixed
Status Update
Comments
es...@gmail.com <es...@gmail.com> #2
Yigit, do you have time to fix it?
reemission of the same liveData is racy
reemission of the same liveData is racy
es...@gmail.com <es...@gmail.com> #3
yea i'll take it.
es...@gmail.com <es...@gmail.com> #4
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.
es...@gmail.com <es...@gmail.com> #5
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()
}
}
ap...@google.com <ap...@google.com> #6
With 2.2.0-alpha04 (that use Main.immediate), the issue seems to be still there (I tested it by calling emitSource() twice, like your test case)
cl...@google.com <cl...@google.com>
es...@gmail.com <es...@gmail.com> #7
yea sorry immediate does not fix it.
I actually have a WIP fix for it:
https://android-review.googlesource.com/c/platform/frameworks/support/+/1112186
if your case is the one i found (emitting same LiveData multiple times, as shown in #5) you can work around it by adding a dummy transformation.
val subLiveData = MutableLiveData(1)
val subject = liveData(testScope.coroutineContext) {
emitSource(subLiveData.map {it })
emitSource(subLiveData.map {it} )
}
I actually have a WIP fix for it:
if your case is the one i found (emitting same LiveData multiple times, as shown in #5) you can work around it by adding a dummy transformation.
val subLiveData = MutableLiveData(1)
val subject = liveData(testScope.coroutineContext) {
emitSource(subLiveData.map {it })
emitSource(subLiveData.map {it} )
}
ap...@google.com <ap...@google.com> #8
Project: platform/frameworks/support
Branch: androidx-master-dev
commit af12e75e6b4110f48e44ca121466943909de8f06
Author: Yigit Boyar <yboyar@google.com>
Date: Tue Sep 03 12:58:11 2019
Fix coroutine livedata race condition
This CL fixes a bug in liveData builder where emitting same
LiveData source twice would make it crash because the second
emission registry could possibly happen before first one is
removed as source.
We fix it by using a suspending dispose function. It does feel
a bit hacky but we cannot make DisposableHandle.dispose async
and we do not want to block there. This does not mean that there
is a problem if developer disposes it manually since our emit
functions take care of making sure it disposes (and there is
no other way to add source to the underlying MediatorLiveData)
Bug: 140249349
Test: BuildLiveDataTest#raceTest_*
Change-Id: I0b464c242a583da4669af195cf2504e2adc4de40
M lifecycle/lifecycle-livedata-ktx/api/2.2.0-alpha05.txt
M lifecycle/lifecycle-livedata-ktx/api/current.txt
M lifecycle/lifecycle-livedata-ktx/api/public_plus_experimental_2.2.0-alpha05.txt
M lifecycle/lifecycle-livedata-ktx/api/public_plus_experimental_current.txt
M lifecycle/lifecycle-livedata-ktx/api/restricted_2.2.0-alpha05.txt
M lifecycle/lifecycle-livedata-ktx/api/restricted_current.txt
M lifecycle/lifecycle-livedata-ktx/src/main/java/androidx/lifecycle/CoroutineLiveData.kt
M lifecycle/lifecycle-livedata-ktx/src/test/java/androidx/lifecycle/BuildLiveDataTest.kt
https://android-review.googlesource.com/1112186
https://goto.google.com/android-sha1/af12e75e6b4110f48e44ca121466943909de8f06
Branch: androidx-master-dev
commit af12e75e6b4110f48e44ca121466943909de8f06
Author: Yigit Boyar <yboyar@google.com>
Date: Tue Sep 03 12:58:11 2019
Fix coroutine livedata race condition
This CL fixes a bug in liveData builder where emitting same
LiveData source twice would make it crash because the second
emission registry could possibly happen before first one is
removed as source.
We fix it by using a suspending dispose function. It does feel
a bit hacky but we cannot make DisposableHandle.dispose async
and we do not want to block there. This does not mean that there
is a problem if developer disposes it manually since our emit
functions take care of making sure it disposes (and there is
no other way to add source to the underlying MediatorLiveData)
Bug: 140249349
Test: BuildLiveDataTest#raceTest_*
Change-Id: I0b464c242a583da4669af195cf2504e2adc4de40
M lifecycle/lifecycle-livedata-ktx/api/2.2.0-alpha05.txt
M lifecycle/lifecycle-livedata-ktx/api/current.txt
M lifecycle/lifecycle-livedata-ktx/api/public_plus_experimental_2.2.0-alpha05.txt
M lifecycle/lifecycle-livedata-ktx/api/public_plus_experimental_current.txt
M lifecycle/lifecycle-livedata-ktx/api/restricted_2.2.0-alpha05.txt
M lifecycle/lifecycle-livedata-ktx/api/restricted_current.txt
M lifecycle/lifecycle-livedata-ktx/src/main/java/androidx/lifecycle/CoroutineLiveData.kt
M lifecycle/lifecycle-livedata-ktx/src/test/java/androidx/lifecycle/BuildLiveDataTest.kt
cl...@google.com <cl...@google.com> #9
Fixed internally and available in navigation-2.9.0-alpha04
ap...@google.com <ap...@google.com> #10
Project: platform/frameworks/support
Branch: androidx-main
Author: Clara Fok <
Link:
Add non-reified NavGraphBuilder.dialog safe args api
Expand for full commit details
Add non-reified NavGraphBuilder.dialog safe args api
Test: ./gradlew navigation:navigation-compose:cC
Bug: 366291612
Relnote: "Added non-reified NavGraphBuilder.dialog API to create a composable dialog with KClass<T>"
Change-Id: Iba4ee26b906c09e7ec47b7e940cf689788c117e8
Files:
- M
navigation/navigation-compose/api/current.txt
- M
navigation/navigation-compose/api/restricted_current.txt
- M
navigation/navigation-compose/src/androidTest/java/androidx/navigation/compose/NavGraphBuilderTest.kt
- M
navigation/navigation-compose/src/main/java/androidx/navigation/compose/NavGraphBuilder.kt
Hash: f96150f5be412aa3d660efd83ba07d439e1da211
Date: Wed Dec 04 13:51:14 2024
ap...@google.com <ap...@google.com> #11
Project: platform/frameworks/support
Branch: androidx-main
Author: Clara Fok <
Link:
Update non-reified composable and navigation
Expand for full commit details
Update non-reified composable and navigation
Added <T : Any> type parameter to the API
Test: ./gradlew navigation:navigation-compose:cC
Bug: 366291612
Relnote: "Non-reified composable and navigation API expects route from KClass<T> instead of KClass<*>"
Change-Id: Icd47da4061103edd8462a729ae168e724d833d36
Files:
- M
navigation/navigation-compose/api/current.txt
- M
navigation/navigation-compose/api/restricted_current.txt
- M
navigation/navigation-compose/src/androidTest/java/androidx/navigation/compose/NavGraphBuilderTest.kt
- M
navigation/navigation-compose/src/main/java/androidx/navigation/compose/NavGraphBuilder.kt
Hash: 653f2ea988ff3744ecf3de08c3221c4ee8c64917
Date: Wed Dec 04 13:41:46 2024
pr...@google.com <pr...@google.com> #12
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.navigation:navigation-common:2.9.0-alpha04
androidx.navigation:navigation-compose:2.9.0-alpha04
Description
Component used: Navigation Version used: 2.8.0
I'm currently using Voyager but decided to try migrating to Compose Navigation as it already provides better type-safety. However, I find it difficult to migrate since the Api is lacking in some way while there are some that are available but is only limited to the Library Scope.
This is in conjunction with Issue 361863272
I would like to request non-reified
navigation
,composable
, andNavBackStackEntry.toRoute()
wherein you can enter the class's KClass as a parameter.Voyager provides
Screen
, andTab
interfaces which could easily be implemented and extended to another interface or abstract class wherein you could create a common Class with common implementations you can tailor according to your needs. Compose Navigation currently doesn't support this but it is much more scalable especially with deeplinks.Migration to Compose Navigation without any interface proves to be difficult unless the above requested are given. I have here an example implementation of interfaces. I don't know how much effective it will be but technically it could be applied to my project to some extent since there are a lot of caveats I don't know of. It would be much better if Compose Team can provide similar interfaces which could greatly boost migration to the library.