It was an automatic update about 5h ago. I do love watching this thread and refreshing as the minutes of each post tick up, whilst waiting for my Xcode_13.2.xip to expand... A good 3h enjoyed thinking I had messed up my xcscheme, which I usually don't touch but had just before the update.

+1 for this and the rest of SwiftUI. There's some annoying edgecases that need solving such as EnvironmentalModifier/resolve(in:) which cannot satisfy Swift Concurrency because ViewModifier is @MainActor but resolve in is nonisolated so you cannot return modifiers.

This requires Sendable self which in my case is not possible.

Frustratingly I can't edit this comment but it regressed with the iOS 18.3 release (didn't catch this in simulators because there weren't any). But is present in iOS 18.4. Interestingly this is only an issue using Xcode 16 (so would be linked to the iOS 18 SDK), building with Xcode 15 doesn't introduce the issue.

Also to add that I did get a response back from the feedback assistant claiming it was expected behaviour because we're wrapping a UIImageView that has isUserInteractionEnabled default false. Setting it to true does fix it but that does not explain why .plain is broken compared to .borderless or why it was fixed after finding it in the Xcode 16.0 beta... Button styles should behave consistently.

Just a heads up this is not a good recommended answer and there is a serious bug in the iOS 18.4 simulator that still exists in the Xcode 16.3 RC1 build. WebViews do not work on second load of the same URL outside of a nonPersistent data store.

Thank you. I usually raise tickets but rarely see them move or get responses. The report number is: FB21939280