John Hoford

Could you post the ? If the duration is very short using "< Transition ..... motion:motionInterpolator="linear" />" might help.

That might be a bug centerVertically (A , B) should connect A top to B top and A bottom to B bottom. Those are very ambiguous API's. I Recommend more...

document the recommended (working) pattern.

A few issues KeyFrames are for modifying the behavior between states. You seem to be trying to change the end constraintSet by using KeyFrames. That will lead to bugs. Generally...

Your code looks almost exactly like the example. The only thing I see odd is you set android:layout_height="wrap_content" Not match parent android:layout_height="match_parent" Try that?

MATCH_PARENT is there because the underlying definition of layout_width/height has it. MATCH_PARENTs behavior can be confusing because how it should behave in many situations is not obvious and has no...

No time to check now but.. You set MotionLayout to android:layout_width="match_parent" android:layout_height="match_parent" not wrap_content Is that intentional?

Do not know what is causing it but as a work around binding.rootMotionLayout.post( binding.rootMotionLayout.requestLayout( ) ) You may also need to do a post requestLayout() in an onTransitionListener( .. onTransitionCompleated()...

Unfortunately that would intern force every one suing this project to upgrade there studio. Some how we need to be able to say build with what ever Gradle you have.

We will look at this next week. MotionLayout does not do anything special for Flow. So I suspect Flow manages the visibility of its views. Related: https://github.com/androidx/constraintlayout/issues/64#issue-772102623