Fixed
Status Update
Comments
yb...@google.com <yb...@google.com> #2
I've experienced seen this issue, even on 26.0.0-beta1.
yb...@google.com <yb...@google.com>
fl...@google.com <fl...@google.com>
fl...@google.com <fl...@google.com>
yb...@google.com <yb...@google.com> #3
Thank you for reporting this issue. We have shared this with our engineering team and will update this issue with more information as it becomes available.
[Deleted User] <[Deleted User]> #4
I think I'm running into this issue again--but this time it's with deep-linking and synthesizing a fragment back stack. If I have postponeEnterTransition in the fragment I'm deep-linking to, I see the other (backstacked) fragments briefly show on screen.
In one project, I'm using the Navigation Component. The graph is just two fragments: A1 is the start destination with a deep-link to A2. I see A1 show momentarily if I use postponeEnterTransition in A2. And I see similar results in another project that does its own fragment transactions; in that case, I can use setReorderingAllowed(false) to prevent the issue.
In one project, I'm using the Navigation Component. The graph is just two fragments: A1 is the start destination with a deep-link to A2. I see A1 show momentarily if I use postponeEnterTransition in A2. And I see similar results in another project that does its own fragment transactions; in that case, I can use setReorderingAllowed(false) to prevent the issue.
ap...@google.com <ap...@google.com> #5
This has been fixed internally and will be avilable in Fragment 1.3.0-alpha08.
Note: this fix relies on using the
Description
it is not intended for public use.