Closed KatieWoe closed 2 months ago
@marlitas and I looked at this together and found a possible fix. The animation in Snack.ts
was sometimes being started before the associated Property value was being set. In cases where the snack was already at the destination position, this could cause the handlers for the animation finishing to be invoked immediately, and the Property being set afterwards. This would cause a problematic state. We adjusted the order and re-red the fuzz testing locally and weren't seeing the problem. I've committed the change, and we will keep an eye on CT to see if the problem is really addressed.
I'm not seeing this error in CT anymore. Closing.