Also, the only workaround I found was to create a legacy UIKit app instead of using SwiftUI.

To my knowledge this still hasn't been fixed. I receive questions regularly from people still experiencing this issue.