[visionOS] Fix PlayToDevice Connection Failure and Version Incompatibility
Solution
Unity 2022.3.x - Unity 6.3.x
Published 29 days ago
Connection issues with PlayToDevice are encountered following package updates or downgrades. Initially, an update to version 2.3.1 prompts an incompatibility warning with PolySpatial. Subsequently, downgrading to versions such as 2.2.4 or 2.1.2 results in a complete connection failure upon entering Unity Play Mode.
Connectivity is restored by using republished PlayToDevice builds available through TestFlight to match the project package version.
The reported connectivity failures between the Unity Editor and visionOS devices are addressed by ensuring that the package versions are synchronized with the republished companion application. Protocol discrepancies often occur when the PlayToDevice application metadata does not align with the installed PolySpatial package version.
- Open the TestFlight application on your visionOS hardware.
- Locate the PlayToDevice application and access the version history.
- Select and install the republished build (such as 2.4.3, 2.3.1, 2.2.4, or 2.1.2) that exactly matches the version of
PolySpatialused in your project. - Verify that the PlayToDevice application is active on the device before initiating Play Mode.
Additional Tips
- Ensure that your visionOS device and the host workstation are residing on the same local network subnet to allow the PlayToDevice discovery protocol to resolve the connection.
- If connectivity persists in failing after a version downgrade, the PlayToDevice app should be fully uninstalled from the device and reinstalled fresh from TestFlight to clear cached configuration data.
Related Posts Haven't quite found a solution to your problem? We think these posts might help you.
Content inspired by a Unity discussion post.