Hmm yes, I see this too, and suspect it is probably one of the things causing the issue I posted about earlier whereby I cannot use Xcode to install/run any apps on Apple Watch Ultra... 🤔 (Unfortunately I'm a n00b in terms of developing for the watch devices, so don't have anything helpful to add beyond corroborating the problem...)

Hmm, that is weird, because we finally got it working (just now, at 23:30 Japan time) by... upgrading our Mac to the latest macOS 13 Ventura beta, Xcode to the latest Version 14.1 beta, our development iPhone to the latest iOS 16.1 beta, and installing the latest watchOS 9.1 beta on the Apple Watch Ultra we are trying to install onto. 😓 I thought that meant it doesn't work with the release versions of Xcode/macOS/iOS/watchOS, but it works with the betas. But it looks like Dpayne5532 is also using the latest betas, and still encountering the issue. 🤔 Very annoying issue, I might add — we wasted the best part of a day on it.

Thanks for the reply; it's anyway nice to know we're not the only ones suffering this issue. 😅 BTW, as I mentioned in another thread about it: we finally got it working (just now, at 23:30 Japan time) by... upgrading our Mac to the latest macOS 13 Ventura beta, Xcode to the latest Version 14.1 beta, our development iPhone to the latest iOS 16.1 beta, and installing the latest watchOS 9.1 beta on the Apple Watch Ultra we are trying to install onto. 😓 However, in that thread, somebody else posted a screenshot of the same error, but the screenshot showed they were using the latest betas, and were still getting the error. So, YMMV, I guess.... 😞 Oh wait, that person in the other thread is you! Well yeah, sorry I don't have much to add other than that since I just installed the Ventura OS tonight, I had to re-setup Xcode from scratch and Xcode automatically re-downloaded my account status, re-generated the automatic signing certificates, etc. I doubt it is related but... I mean maybe since it seems to be a download permission error? 🤷‍♀️ It might be worth creating a brand new user account on the Mac and setting up Xcode from scratch. (OTOH it might just end up being something Apple fixes on the backend tomorrow...)