IssueTracker

It's the copy of framework bug https://issuetracker.google.com/issues/37118689
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: https://github.com/andkulikov/TwoVisibilityTransitionExample 

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 - https://github.com/andkulikov/Transitions-Everywhere. You can take a look on my variant of this fix:
https://github.com/andkulikov/Transitions-Everywhere/commit/d2c6c2382ae9199dc2eea6b22a5dab49502ebc00