But I filed a radar and that came back with "Potential fix identified - For a future OS update", so I'm guessing they fixed it in 18.2
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags: