sorry for cross-posting: those who need to work with iOS 17 Simulator and cannot use iOS 16 versions: I have posted my analysis and a workaround here: https://developer.apple.com/forums/thread/734573?answerId=771879022#771879022 in short: check for the „Poster“ processes and kill them. They are iOS 17 specific as we are now able to customise the front screen more In depth. (A very important feature if you work with a Simulator 😂)

I was able to fix the problem for my two Apple Watches (Series 3 and 4!). I didn't see my paired Apple Watches in Xcode 15.3. As I'm new to watchOS development, I don't know if the problem would already occur for earlier versions. To make Xcode show my watches in the "Devices and Simulator" I did the following steps: (I don't know if all of them are really necessary) disconnecting iPhone from the Mac (=no cable) unpair the iPhone from Xcode unpaired both watches from the iPhone (=basically erasing them) disabling "Developer Mode" (in "Privacy & Security" settings) on the iPhone execute "Clear trusted computers" from the iPhones "Developer" setting restart the iPhone and Mac pair the watch with the iPhone (this takes a while!) make sure Xcode is not running on the Mac connect the iPhone using a cable to the Mac choose "Trust" when asked by your iPhone to "Trust This Computer?" and confirm by entering your PIN go to the Finder, choose your iPhone in the sidebar and do the same thing: choose "Trust" to establish a connection start Xcode and open the "Devices and Simulator" window, where you will see your iPhone and its paired Apple Watch. again, you will have to establish "Trust" by confirming the connection on your iPhone and watch finally, to be able to fully connect to your phone & watch, you will have to re-enable "Developer Mode" (in "Privacy & Security" settings) for both, the iPhone and the watch, and restart the devices. now you should be able to fully access the devices in Xcode 15.3 even without a cable connected between your Mac and iPhone. PS: If you have a Apple Watch Series 3 and 4 (as I do), you might perhaps struggle if the Mac, iPhone and watch are not connected to the same 2GHz WLAN... Make sure they are all connected to the same network.

I can't remember having seen this dialog when starting Xcode 16 beta (or I might have been able to easily accept it?). But before I downloaded the latest beta from Apples website I have been logging into https://developer.apple.com and had to agree to the changed terms under the "Account" section.

I've seen the same lagging in my app while debugging. I checked the Console app and saw that the error messages were generated from a "com.apple.GenerativeModels" library (category "availability") whenever a single key was tapped. The error messages are generated even when the app is not started from Xcode.

I've seen this error message too when running a very simple SwiftUI app (built using Xcode 26.0 (17A324)) on my device (iPhone 16 running iOS 26.0 (23A341)): Start the app Wait 10 seconds Send the app to the background. No other user interaction is necessary. The LLDB statement you provided does catch the location of the error message. But the stack trace is not helpful, as non of my code is involved. But what I've seen is that the error message is written to the console when the app is sent for the first time to the background. It doesn't appear anymore afterwards. The call stack I've captured is: #0 0x00000001a74e1280 in os_log () #1 0x00000001914d4218 in ___lldb_unnamed_symbol7481 () #2 0x000000018b2855c0 in ___lldb_unnamed_symbol14749 () #3 0x00000001914dc944 in ___lldb_unnamed_symbol7669 () #4 0x00000001914dce24 in ___lldb_unnamed_symbol7677 () #5 0x00000001de688520 in partial apply forwarder for closure #1 (Swift.UnsafeMutablePointer<Swift.Optional<Observation.ObservationTracking._AccessList>>) -> τ_0_0 in Observation.generateAccessList<τ_0_0>(() -> τ_0_0) -> (τ_0_0, Swift.Optional<Observation.ObservationTracking._AccessList>) () #6 0x00000001de67fc18 in withUnsafeMutablePointer () #7 0x00000001de67fb40 in Observation.generateAccessList<τ_0_0>(() -> τ_0_0) -> (τ_0_0, Swift.Optional<Observation.ObservationTracking._AccessList>) () #8 0x00000001de67ff00 in withObservationTracking () #9 0x00000001914dad74 in ___lldb_unnamed_symbol7647 () #10 0x0000000181785ef0 in merged closure #1 (Builtin.RawUnsafeContinuation) -> () in Swift.withCheckedContinuation<τ_0_0>(isolation: isolated Swift.Optional<Swift.Actor>, function: Swift.String, _: (Swift.CheckedContinuation<τ_0_0, Swift.Never>) -> ()) async -> τ_0_0 () #11 0x000000018178605c in (1) suspend resume partial function for Swift.withCheckedThrowingContinuation<τ_0_0>(isolation: isolated Swift.Optional<Swift.Actor>, function: Swift.String, _: (Swift.CheckedContinuation<τ_0_0, Swift.Error>) -> ()) async throws -> τ_0_0 () #12 0x00000001914dcc30 in ___lldb_unnamed_symbol7676 () #13 0x00000001914aa7f8 in ___lldb_unnamed_symbol6613 () #14 0x00000001817afe60 in (2) await resume partial function for Swift.withTaskCancellationHandler<τ_0_0>(operation: () async throws -> τ_0_0, onCancel: @Sendable () -> (), isolation: isolated Swift.Optional<Swift.Actor>) async throws -> τ_0_0 () #15 0x00000001914da668 in ___lldb_unnamed_symbol7643 () #16 0x00000001914adb30 in ___lldb_unnamed_symbol6682 () The unnamed symbols are from AXCoreUtilities. The log with its meta data is: Potential Structural Swift Concurrency Issue: unsafeForcedSync called from Swift Concurrent context. Type: Fault | Timestamp: 2025-09-30 22:09:09.104033+02:00 | Process: TicTacToe | Library: AXCoreUtilities | Subsystem: com.apple.Accessibility | Category: AXCommon | TID: 0x621c23