@DTS Engineer Hi Albert, yes, this looks to be resolved in Xcode 26.1 beta 2 (17B5035f).

Still an issue as of Feb 2025 with Xcode 16.2.

I can reproduce this in a bare bones 10 line SwiftUI Mac Catalyst app. import SwiftUI @main struct TextFieldApp: App { @State private var text: String = "" var body: some Scene { WindowGroup { TextField("Text", text: $text) } } } Run the app (don't even need to give the TextField focus) Give focus to another app Give focus to the app again and the message is logged to the console. Apple M3 Pro Sonoma 14.7.1 Xcode Version 16.0 (16A242d)

We've found a viable temporary workaround through an @unchecked Sendable container and coordination via an OSAllocatedUnfairLock

Thank you very much! This appears to be fixed as of iOS 17.0 (21A5317a Beta 7).

Removed

Hi @nathanfusselman I'm also running Xcode 15 Beta 7 and structured logging doesn't seem to be working for me either. I'm using an iOS 17 simulator and I remember structured logging working just fine in the previous beta versions.

The question is answered in this post. The correct solution is to use capture lists.

Am also having the same issue mentioned twice above (the 19.737993 magic number).

Hi @baugestalt, no I haven't. I'm hoping that it's fixed for the iOS 17 release build.

Apologies, this would be more appropriately titled, iOS 17 Breaks Usage Of TextField.focused()

For what it's worth, I'm no longer seeing the error when running on a 16.1 simulator.

Duplicate

As of iOS 15 the correct path is Settings > General > VPN & Device Management