It seems a bit more broken than this. Selecting a previous field which has suggestions then selecting the new password field keeps the autofill bar for the previous field and messes with the keyboard change notifications... Very fun. This reminds me of the mess that is GameplayKit which is mostly dysfunctional and riddled with crashes.

I'm wondering if it's possible to login an Xcode AppleID account on the CI machine using an app-specific password, then rely on xcodebuild to use that account behind the scenes? Has anyone tried this?

I think this issue is affecting the GitHub Actions runners as well. The iOS 17 simulators are unusable now; it's a huge pain as it likely means downgrading our validation pipelines back to Xcode 14.

Same boat. This change breaks our SDK and just seems odd. Now that Xcode 16.2 has released, using a Task for this seems inappropriate so I'd +1 the MainActor.assumeIsolated but honestly what nonsense and it's frustrating to not know if this change is purposeful. Why are no devs commenting on this; incredibly frustrating. I like Swift Concurrency but I reckon the devs might be at the point of 'can we make SwiftUI truly concurrent for performance gains' and finding that realistically the answer is no so they need to @MainActor it all. I'm at the same pain point and the biggest and obvious issue is nonisolated contexts that need to access isolated contexts need to be made async so really I need to either @MainActor or async it all.

This has regressed in iOS 18.4 and is now a serious issue for our clients. It's crazy that a bug like this can come back but image buttons with plain style no longer work.

This is still broken in Xcode 16.3 RC1 which is worrying. WebViews do not load the same URL the second time round. They do load if the datastore is set to nonPersistent but this is not a workaround.

This definitely feels more like a bug than something they've done intentionally. On iOS 18 the toolbar sits above the tab bar. On iOS 26 the UI is broken.