You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use ios-deploy to connect to a Vision Pro but it's unable to see it on the network. It does see my iphone and ipad but can't see the Vision Pro. I have the same issue in go-ios, wasn't sure if this is just something that doesn't work yet due to the newness of the device or if I have something not setup correctly on my side. I am able to see the Vision Pro wirelessly connected in Xcode and do installs there. If there is anything I can run to debug let me know.
The text was updated successfully, but these errors were encountered:
I don't think ios-deploy can support visionOS (in its current form at least). It's a tool built on Apple's MobileDevice framework which AFAIK does not support visionOS. Starting with Xcode 15, Apple has swapped to a new CoreDevice framework to interact with devices. visionOS is only supported with the newer CoreDevice framework (as is iOS 17 which you may have noticed that some ios-deploy features no longer work on).
Apple does ship a command line tool similar to ios-deploy with Xcode 15 called devicectl that provides many of the same features (see xcrun devicectl --help). One notable missing feature from devicectl is the ability to connect a debugger to the device. The CoreDevice framework is capable of doing so but Apple's command line tool does not provide that feature.
I'm trying to use ios-deploy to connect to a Vision Pro but it's unable to see it on the network. It does see my iphone and ipad but can't see the Vision Pro. I have the same issue in go-ios, wasn't sure if this is just something that doesn't work yet due to the newness of the device or if I have something not setup correctly on my side. I am able to see the Vision Pro wirelessly connected in Xcode and do installs there. If there is anything I can run to debug let me know.
The text was updated successfully, but these errors were encountered: