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
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
- Default Custom Components in project have Library counterparts
- [iOS]"The destination host has an erroneous SSL certificate" error is thrown when using UnityWebRequest to connect to the server with a self-signed certificate
- Freeze/crash on DynamicHeapAllocator::Allocate when opening a specific project
- Text Settings Inspector sections names have no padding
- UI elements shrinking, misaligned buttons, swapped icons, or incorrect styles when rapidly cycling through Scenes in the Player
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.