I'm also seeing this exact issue, and haven't yet found an acceptable fix or workaround. Has anyone been able to work around it without breaking anything else?
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags: