Status Update
No update yet.
Comments
il...@google.com
To use
The issue is happening because, starting from LocalLifecycleOwner has been moved from androidx.compose.ui to lifecycle-runtime-compose, as outlined in their respective release notes. For compatibility reasons, you must update both dependencies.
For context, note these changes were made to enable the utilization of its Compose-based helper APIs beyond Compose UI (such as in
If the issue persists even after updating your Compose UI, please let us know.
Edit: please see
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.