Search Issue Tracker
Fixed
Fixed in 1.3.13
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment