Search Issue Tracker

Won't Fix

Votes

0

Found in

2019.4

2020.3

2020.3.14f1

2021.1

2021.2

2022.1

Issue ID

1362954

Regression

No

Console errors appear when reimporting UnityEngine.UI when the Library folder is symlinked

Asset - Database

-

Reproduction steps:
1. Download the attached "linktest.zip" project
2. Move the "Library" folder to a different disk
3. Create a symlink copy of the "Library" folder in the project folder
4. Open the project
5. In the Project window, select the "UnityEngine.UI" assembly definition file
6. Right-click and press reimport

Expected result: No errors appear in the console window
Actual result: "Copying assembly from 'Temp/UnityEngine.UI.dll' to 'Library/ScriptAssemblies/UnityEngine.UI.dll' failed. Detailed error: Win32 IO returned 1176" error appears in the console

Reproducible with: 2019.4.32f1, 2020.3.23f1, 2021.1.28f1, 2021.2.3f1, 2022.1.0a15

  1. Resolution Note:

    The use of symlinks is not fully supported in Unity. Simpler use cases should work, and symlinks should not cause Unity to crash. However, we don't support all the complexities that they can introduce, such as multiple references to the same asset, recursive symlinks or sharing assets between projects using different versions of Unity - or sharing across volumes, as in this case.

    When symlinks are discovered in a project, we emit the following warning:

    "Using symlinks in Unity projects may cause your project to become corrupted if you create multiple references to the same asset, use recursive symlinks or use symlinks to share assets between projects used with different versions of Unity. Make sure you know what you are doing."

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.