Fixed
Status Update
No update yet.
Comments
ar...@google.com
is...@google.com
al...@google.com
Found the issue, ugh
Noticed that when I do the following:
transaction.addToBackStack(null)
When adding a Fragment with ViewPager2, the above issue occurs, although, idk if it's becaugh of gcFragments() anymore.
As soon as I un-comment that line, the issue disappears.
Noticed that when I do the following:
transaction.addToBackStack(null)
When adding a Fragment with ViewPager2, the above issue occurs, although, idk if it's becaugh of gcFragments() anymore.
As soon as I un-comment that line, the issue disappears.
al...@google.com
Is the Sample application, to reproduce, move back really fast between page 2 -> 1 and vice versa (they are bottom buttons) a couple times.
Wait a couple seconds and page 1 (the black page) should turn white meaning the Fragment has been removed.
As soon as you comment line 40 on MainActivity, and attempt again, the error does not persist
am...@google.com
an...@google.com
Woops, sorry, If you guys had the previous ViewPagerCrash test app, I forgot to push (was exhasuted after debugging) I pushed one more time for the latest reproducible code
Description
In support transitions we also have such bug.
Library com.android.support:transition:26.0.0-beta2
In some cases if you apply more than one animators that animate visibility changes it will show two instances of view.
Example project:
Screencast is attached.
Works fine with the code:
TransitionManager.beginDelayedTransition(container,
new TransitionSet()
.addTransition(new Fade())
.addTransition(new Slide(Gravity.RIGHT)));
icon.setVisibility(View.GONE);
But have two "instances" of animated view in that case:
TransitionManager.beginDelayedTransition(container,
new TransitionSet()
.addTransition(new Fade())
.addTransition(new Slide(Gravity.RIGHT)));
container.removeView(icon);
The reason of it that every Visibility transition add the "screenshot" of view to the overlay separately. I think first Visibility transition should add view to the overlay and the second Visibility transition should reuse the same view from overlay and apply animation to it.
I've already fixed the issue in my backport of transitions framework -