Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.3.4f1
Issue ID
809590
Regression
No
Asset Database only handles one of multiple colliding GUIDs
Materials in the project have colliding GUIDs. Simplest repro:
1. From Finder/Explorer, duplicate an asset twice (together with .meta)
2. Go back to Unity and notice that
- one of the new duplicate assets has been detected as a duplicate GUID and re-assigned
- the other one is left with a colliding GUID. this will eventually result in broken references, e.g. when exporting as a package (user case).
Reproducible: 5.2.4.f1, 5.3.4f1, 5.3.5p5, 5.4.0b24
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment