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
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
- Mouse and Pointer Events are called incorrectly in ScrollView with XRUIInputModule
Add comment