Posts

Post not yet marked as solved
32 Replies
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
Post not yet marked as solved
6 Replies
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
Post not yet marked as solved
6 Replies
Essentially during all the Xcode 15 betas - watchOS has been crippled. Cannot test deployment at all on device and even OS 9.6 device won't connect.
Post not yet marked as solved
3 Replies
Also applies to watchOS 9.6 trying to connect it to Xcode 15 beta 6.
Post not yet marked as solved
2 Replies
Nothing works for me on Xcode 15 beta 6, tried multiple watches: FB12925643
Post not yet marked as solved
9 Replies
I've tried Xcode 15 beta 6 with a watchOS series 5 on OS 9.6 and a series 8 on OS 10.0 beta, none work. I get "Waiting of connection" on OS 10 and "Unsupported wire protocol version: This host does not support the wire protocol version implemented by the device." on OS 9.6 Unpaired, repaired, reset - did everything. Nothing works. FB12925643
Post not yet marked as solved
32 Replies
Submitted report: FB12925643
Post not yet marked as solved
32 Replies
I've tried everything as well - not connecting with Apple Watch Series 5, watchOS 10 (21R5295g) and Xcode 15 beta 6. Either says "Connecting ..." or "Waiting..." and keeps switching between the two. Unable to test the app.
Post not yet marked as solved
32 Replies
Getting: /Applications/Xcode-beta.app/Contents/Developer/usr/bin/devicectl device info ddiServices --device UUID_HERE --verbose Using verbose logging. ERROR: The operation couldn’t be completed. Operation timed out (NSPOSIXErrorDomain error 60.)
Post not yet marked as solved
32 Replies
It's not working for me either - exact same message in Xcode 15 Beta 6. I see this: xcrun devicectl list devices xcrun: error: sh -c '/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -find devicectl 2> /dev/null' failed with exit code 17664: (null) (errno=Invalid argument) xcrun: error: unable to find utility "devicectl", not a developer tool or in PATH
Post not yet marked as solved
6 Replies
Another on Ventura: FB11762161
Post marked as solved
3 Replies
Did you find a workaround?
Post not yet marked as solved
3 Replies
Note that NSFetchRequest will always read from disk, which explains why it's working for you. NSFetchedResultsController uses a cache where possible (as the documentation explains). You can purge the cache if you wish: https://developer.apple.com/documentation/coredata/nsfetchedresultscontroller?language=objc
Post not yet marked as solved
2 Replies
🤦‍♂️ Release notes say bit code is no longer supported. Got it.