Search Issue Tracker
Third Party Issue
Votes
0
Found in
2022.3.60f1
6000.0.45f1
6000.1.0b13
6000.2.0a8
Issue ID
UUM-101777
Regression
No
Xcode VisionOS builds fail with a "Circular dependency..." error when the used project is named "Metal"
How to reproduce:
1. Create and open a new project named “Metal”
2. Switch the Build Target to VisionOS
3. Build and Run the project on Xcode
4. Observe Xcode
Expected result: The Build is successful and the App is running
Actual result: The Build fails with “Circular dependency…” error
Reproducible with: 2022.3.60f1, 6000.0.45f1, 6000.1.0b13, 6000.2.0a8
Reproducible on: macOS Sequoia 15.3.2 (M3 Pro), macOS M2 Pro (user’s)
Not reproducible on: Windows 11
Notes:
- Related Unity Discussions thread: https://discussions.unity.com/t/circular-dependency-between-modules-metal-and-realityfoundation/1616884
- Not Reproducible on Windows 11 when using Vulkan Graphics API and naming the project Vulkan
- Not Reproducible with iOS and Standalone Build Targets
- Xcode full build fail error: /Users/[USERNAME]/Metal/TestVisionOS/Libraries/com.unity.xr.visionos/Runtime/Plugins/visionos/UnityMetalMainApp.swift Circular dependency between modules 'Metal' and 'RealityFoundation'
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
We've investigated this issue and found that it comes from Apple somewhere specifically related to VisionOS.
During testing it was noted that it does not reproduce on Windows and does not affect Standalone or iOS builds using the same project and same conditions.