Open robbiet480 opened 7 months ago
Oh and I thought at first it was a OS bug but other apps successfully requested local network access.
Hey I finally got it to pop after a reboot + opening the app from the launcher instead of Xcode. However, the Windows side still can't find it.
I'm wondering if the app requires the multicast entitlement to function on device which is required for sending or receiving any kind of non-unicast UDP traffic...
Brought up the requirement for a mDNS discovery protocol to avoid the entitlement on the ALVR Discord at here
@robbiet480 Check if PR https://github.com/zhuowei/VisionOSALVRClient/pull/6 helps you connect; I at least get a connection to Windows from the updated ALVRClientCore.xcframework with Vision Pro hardware when adding it manually. The stream itself needs a lot of work for me but it connects and shows VR Home when I combine the new xcframework with PR https://github.com/zhuowei/VisionOSALVRClient/pull/3
Yeah I'm able to get connected now but its not pretty as the headset only sends out discovery packets for a few seconds and if the Windows client isn't searching at the same moment they don't link.
Having some really weird behavior when trying to run on device. Logs look like this:
Over and over again. Manually adding the device by name and IP from the Windows side does nothing, it never connects. I've confirmed with nmap that the port is open randomly, it seems to only stay open when discovery is happening which is for a few milliseconds. I'm sometimes able to connect like this:
I've tried everything to get the local network prompt to pop on device, so far no dice. I even attempted to run a simple HTTP request to a totally unrelated service on the same box running ALVR but it worked fine. The Settings app doesn't show local network access granted. I do get the popup on iOS but only after the app crashes out from a black screen.