Seeing the same issue with Xcode 15 Beta 7 even though it says watchOS connectivity has been resolved. see "Waiting to reconnect to Apple Watch Series 5" and then a "Connecting to Apple Watch Series 5" message and it keeps switching between the two

Xcode 15 beta 7 here (still not working). The terminal this time however claims it's paired: Apple Watch Series 5 XXX XXXXXX-EA2A-4FB3-XXXXX-XXXXXXX available (paired) Watch5,2 iPhone 14 Pro Max XXX XXXXXXX-0012-XXXXXXX connected (no DDI) iPhone 14 Pro Max (iPhone15,3) And: devicectl device info ddiServices --device XXXXXX-EA2A-4FB3-XXXXX-XXXXXXX --verbose Using verbose logging. ERROR: The operation couldn’t be completed. Operation timed out (NSPOSIXErrorDomain error 60.)

@pk_ I've gone through every crash report and indeed they're all on build 24A5298h, which is beta 4! Coincidentally I'm also not seeing an explosion of crashes (which I was dreading) so it's likely a few dozen users on the same older build in our case. The same on iOS 18 - Crashlytics doesn't give us the build number of the OS so it wasn't obvious that they may all have been on older betas. We can probably safely assume this isn't happening on later versions of macOS 15. What threw me off is a few users crashing on macOS 11 and 14 but these are now most likely because of something else.

This is now breaking custom shortcuts for numerous third party apps and other than users complaining about our apps, it's hilarious to require users to learn about this "special knowledge" unless apps begin to say "you must also use CMD key if you want to use Shift or Option" - which makes no sense. This is a regression back to 1999 when there weren't that many apps and there weren't that many shortcuts to remember.

With this change you're protecting passwords that contain Ø but what about all the other passwords that use plain English and do not use Shift+Option? What about the emails and documents the user has composed in Mail / Outlook / Pages? Those can be logged? Sequoia might as well disable all keys on the keyboard to protect the user from ever leaking their passwords to key-loggers that their jealous boyfriends managed to install while on vacation. This is frankly ridiculous.

I'm seeing these too, for our main window (not menu-bar app). It's an AppKit app that has started to log hundreds of these at launch.