Run attached project in paused "step by step" mode, and look at the console.

MatchTarget is "scheduled" between 0.1 and 0.4 in normalized time (clip has a length of 1 s, so normalized = regular time).

We call a MatchTarget when t > 0.4 (so "matching window" for first loop iteration is passed) and expect cube to be moving towards target between t = 1.1 and t = 1.4.

Note in the debug traces that at t = 1.26, target has already been reached in y, and animator.isMatchingTarget is already false, when we do not expect the match to be complete before t = 1.4.

I'm also puzzled as to why the x position would be -1.