Its unbelievable to me that this hasn't been fixed or given more attention yet. I don't have a code example, but I can tell you that I found a workaround by rendering a mirrored version of the element as an overlay, starting the animation from that overlay as the matchedTransitionSource, then removing it from the view hierarchy once the close animation is done. In theory, this moves the bug onto the overlay which isn't visible after the animation completes, meaning the element behind it keeps its original behavior. That being said, this bug along with https://origin-devforums.apple.com/forums/thread/807208 makes using .navigationTransition with .matchedTransitionSource incredibly complex, requiring a specific workaround for both. I would not recommend using these APIs as they currently stand.

You will need to change the line var xoutput = Double(self.xaxis.text) ?? 0.0 to var xoutput = Double(self.xaxis.text ?? "0") ?? 0.0 The self.xaxis.text field is optional