Summary
This issue is from here. The “Minimum Target visionOS Version” setting in Player Settings is currently being ignored during build. This is caused by an unconditional override in the visionOS build post-processor, which forces the minimum version to 2.0 regardless of user configuration.
This results in user confusion and prevents correct usage of supported minimum version (1.0) when applicable (e.g., Windowed mode).
Root Cause
In the visionOS build post-processor, the minimum target version is unconditionally set to 2.0 to satisfy requirements for Metal / RK / Hybrid modes. However, this logic does not respect user-defined Player Settings.
Git blame indicates this was introduced to enforce required features for 2.0+, but it currently overrides all user input, even when not necessary.
Expected Behavior
- Player Settings “Minimum Target visionOS Version” should be respected.
- Version should only be enforced/upgraded when required by specific build modes/features.
Actual Behavior
- The post-processor unconditionally sets minimum target visionOS version to 2.0.
- Any value set in Player Settings (e.g. 1.0) is ignored.
Impact
- User confusion due to ignored settings
- Incorrect build configuration visibility
- Prevents correct usage of visionOS 1.0 minimum target when applicable (e.g. Windowed mode)
- Workaround required by users to manually re-adjust or override behavior