Fixed
Status Update
Comments
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #2
Yigit, do you have time to fix it?
reemission of the same liveData is racy
reemission of the same liveData is racy
ta...@gmail.com <ta...@gmail.com> #3
yea i'll take it.
il...@google.com <il...@google.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.
Description
Version used: 1.1.0-alpha05
FragmentFactory has the method
public Fragment instantiate(@NonNull ClassLoader classLoader, @NonNull String className, @Nullable Bundle args)
but that method doesn't call setArguments(). While the Javadoc specifically calls this out, it is still confusing. The stated use case of constructing a different Fragment based on the arguments doesn't make much sense since developers can all setArguments() at any point after the fact (so needing a separate class for different arguments breaks down).