Fixed
Status Update
No update yet.
Comments
il...@google.com
This requirement for addObserver to be called on the main thread is part of the 2.3.0-alpha06 release notes
LifecycleRegistry now verifies that its methods are called on main thread. It was always a requirement for lifecycles of activities, fragments etc. An addition of observers from non-main threads resulted in hard to catch crashes in runtime.
It affects all APIs that use Lifecycle, including Navigation.
Description
When using fragment transitions with multiple fragments in a single transaction, only the last fragment in and the last fragment out transitions are actually run. All other transitions on intermediate fragments are ignored.
Adding two fragments with enter transitions, the first fragments transition will be ignored which will result in that fragment appearing in place immediately, while the second fragment properly does its transition.
If a fragment has a transition, we should run it.
In the attached sample, there are two fragments added at the same time. The first fragment added has a 5 second fade in transition and the second fragment added has a slide transition for buttons.
Expected behavior: The first fragment does its fade as the second fragment slides its buttons into place.
Actual behavior: The first fragment does no fade and the second fragment slides its buttons into place.