Search Issue Tracker
Fixed
Fixed in 2022.3.11f1
Votes
2
Found in
2022.3.6f1
Issue ID
UUM-46745
Regression
No
[M1]Error building empty visionOS project with Simulator SDK selected instead of Device SDK
How to reproduce:
1. Create a new empty project in Unity 2022.3.6.
2. Switch the target platform to visionOS (experimental). (File → Build Settings)
3. Change SDK from Device SDK to Simulator SDK in the Player Settings.
4. Build the project.
Expected result: Project successfully builds
Actual result: The build fails
Reproducible with: 2022.3.6f1
Reproducible on: macOS M1 (User Reported)
Not reproducible on: No other environment tested
Notes:
- Not reproduced by CQA
- Unity will build successfully if the default value of Device SDK is selected in the Player Settings.
- Developer needs to use Simulator SDK since Apple Vision Pro is not yet available for purchase.
Comments (1)
-
Yugo_mydearest
Aug 30, 2023 09:45
I also have verified this issue using below:
・Intel processor
・version 2022.3.5f1
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
- [MacOS] Can't clear text from text field when using Japanese IME on macOS
- Freeze or crash on MemoryProfiler::UnregisterAllocation when opening a specific Scene
- [Android] Application freezes when changing between materials on Mali G52 devices
- UI Builder performing Redo action for creating a nested element throws nvalid UXML or USS: System.IndexOutOfRangeException and corrupts the opened document causing data loss
- Element blocks another element when it is set to PickingMode.Ignore
Resolution Note (fix version 2022.3.11f1):
Confirmed that starting with editor 2022.3.11f1, users now need to specify player target SDK under Project Settings -> Player -> visionOS tab (last tab which does not have an icon) -> Other Settings -> Target SDK. Users running against the visionOS simulator need to set this value to Simulator SDK, and users running on HMD need to set this value to Device SDK. Both options have been confirmed working starting with 0.4.1 release.