Fixed
Status Update
No update yet.
Comments
al...@google.com
Yigit, do you have time to fix it?
reemission of the same liveData is racy
reemission of the same liveData is racy
jb...@google.com
ap...@google.com
yea i'll take it.
jb...@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.
Description
ViewModelProviderKtexists in bothlifecycle-viewmodel-ktx:2.3.1, which gets pulled in transitively byappcompat, andlifecycle-viewmodelat head. If I updateappcompattolifecycle-viewmodelit's going to cause a classpath conflict for a lot of external clients.Dependency constraints should be used here, but Gradle has several bugs in dependency constraint resolution that prevent us from using it (seehttps://github.com/gradle/gradle/issues/19882 ).
Please use a different
JvmNamefor the class inlifecycle-viewmodelso that we can avoid the conflict without needing to blocklifecycle-viewmodelorappcompat's release on Gradle fixing their bugs.