Search Issue Tracker
Won't Fix
Won't Fix in 5.6.X, 2017.1.X
Votes
1
Found in
5.6.1p3
Issue ID
942412
Regression
Yes
Infinite Guid Changes because of Symlinks
Reproduction steps:
1. Open project attached (Symlinks.zip).
2. Setup Symlink.
Instructions:
- Open cmd with administrator rights.
- Go to "Project"\Assets\ComScore-iOS-SDK-master\comScore\ComScore.framework
- run this code line: "mklink /D Test Versions"
3. Go to Editor and check the console.
4. If the console is clear, go to "Assets" and use "Reimport All".
Expected result: There will be no warnings due to symlink.
Actual result: Warning appear like "The GUID for ... is already in use by...".
Notes: if you use a symlink to a file directly, everything goes ok, but if you use a symlink to a folder, it shows these warnings (and recreate the guid, etc.). It only happens on 5.6+
Reproduced on: 5.6.0a2, 5.6.3p2, 2017.1.0p5, 2017.2.0b9, 2017.3.0a6
Comments (3)
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
bencoPB
May 16, 2019 14:55
Unity needs to be able to handle iOS Frameworks, we need to reopen this issue.
brokenbeta
Jun 04, 2018 15:14
Does whoever marked this as Won't Fix understand the bug? The GUID for these assets changes *every time you give the Editor focus*. It makes clean commits almost impossible.
CapitalGames
Apr 02, 2018 22:49
Additional information: This occurs with iOS Frameworks which typically use these sorts of symlinks to reference "Current" from a set of contained libraries etc. As such it's going to occur for a lot of the plugins that support iOS and contain the prescribed Apple frameworks.