Search Issue Tracker
Fixed
Fixed in 1.3.13, 2.4.X
Votes
0
Found in [Package]
1.3.13
2.2.4
Issue ID
XRVOSB-87
Regression
No
GUID conflict errors are thrown when using PolySpatial and XR Hands packages
How to reproduce:
1. Open the attached “IN-101361.zip”Project
2. Observe the Console Window
Expected result: No errors
Actual result: “GUID [ID] for asset “com.unity.xr.hands file” conflicts with: “com.unity.polyspatial file” error is thrown
Reproducible with: 1.3.13 (2022.3.63f1), 2.2.4 (6000.1.6f1), 2.3.1 (6000.0.51f1, 6000.1.6f1, 6000.2.0b5)
Reproducible on: macOS 15.5 (M3 Pro), Windows 11 (user’s)
Not reproducible on: No other environment tested
Notes:
- Couldn’t reproduce on a new project
- Deleting Library and downgrading/re-installing packages did not fix the issue
- Full example error message:
GUID [2aeecf660b8290a45a8e652def3864bf] for asset 'Packages/com.unity.xr.hands/Editor/Analytics/XRHandsPlaymodeUsageEvent.cs.meta' conflicts with:
'Packages/com.unity.polyspatial/Editor/Analytics/PolySpatialPlaymodeUsageEvent.cs.meta'
We can't assign a new GUID because the asset is in an immutable folder. The asset will be ignored.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment