Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.30f1
Issue ID
UUM-72213
Regression
Yes
There is an ability to switch to VisionOS module even though the installation of the module has failed
How to reproduce:
1. Install the VisionOS module in the Unity Hub (It will fail due to another issue, UUM-69573 )
2. Create a new Project
3. Open the Build Settings Window (File -> Build Settings)
4. Click on VisionOS
5. Click switch platform
Expected result: The ability to switch the platform is unavailable because the module is not installed
Actual result: There is an ability to switch to VisionOS even though the module is not installed
Reproducible with: 2022.3.30f1
Not reproducible with: 2022.3.29f1
Reproduced on: Windows 11
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
- Mouse and Pointer Events are called incorrectly in ScrollView with XRUIInputModule
- Memory leak occurs when repeatedly minimizing and maximizing the UI Builder window
Resolution Note:
This isn't itself a fixable bug; if the installation fails there's no way to know with 100% if accuracy that it failed.
However, the underlying issue (the visionOS bad installation) *has* been fixed.