Fixed
Status Update
Comments
il...@google.com <il...@google.com> #2
Trying to find a temporary work-a-round I found that `MediatorLiveData` also doesn't work, as it internally also calls observeForever/removeObserver.
The only work-a-round I found is very hacky and only works on this specific scenario is to `post` to a Handler to `removeObserver` later.
It works only on this case because the background processing only happens when the network call is successful (a.k.a. the LiveData won't values anymore).
The only work-a-round I found is very hacky and only works on this specific scenario is to `post` to a Handler to `removeObserver` later.
It works only on this case because the background processing only happens when the network call is successful (a.k.a. the LiveData won't values anymore).
il...@google.com <il...@google.com> #3
Thank you for a report!
Yeah, your work around is fine for now. This is going to be fixed in alpha-9.
Yeah, your work around is fine for now. This is going to be fixed in alpha-9.
Description
Component used: Fragment
Version used: 1.2.4
Devices/Android versions reproduced on: N/A
If both the platform and AndroidX transitions are both used in a fragment transition you get this error:
It's not very helpful or tell you how to fix it.
It would be very useful if it listed the following:
It's very easy to accidentally import the wrong transition by accident