Search Issue Tracker
Won't Fix
Votes
3
Found in
2017.1.0xf3
Issue ID
944085
Regression
No
[Linux Editor] Building Android in Linux Editor fails after the first time with IOException: Failed to Copy File / Directory
Prerequisites: A storage device with NTFS system, I used an 8GB flash drive.
Steps to reproduce:
1. Create a new project on an NTFS device
2. Change build target to Android
3. Set any correct bundle identifier
4. Build an .apk file
5. After building completes, build again
Expected results: second .apk file is successfully built.
Actual results: building fails with an error
IOException: Failed to Copy File / Directory from 'Temp/StagingArea/Data' to 'Temp/StagingArea/assets/bin/Data': destination path already exists.
Reproduced with:2017.1.1f1, 2017.2.0b11
Notes:
* Did not reproduce on ext4 or FAT formats.
* Killing UnityShaderCompiler processes makes it possible to build again one time.
Comments (2)
-
forestrf
Dec 09, 2020 22:52
In my case, I rarely use Linux, so I just want to have Unity open the project I have on my Windows HDD without having to copy paste files around or waiting for git to do it's stuff.
To fix this problem, I created a folder anywhere in my Linux HDD and drag and dropped to it (creating a link, by pressing CTRL-SHIFT while dragging) the folders "Assets", "Project Settings" and "Packages" from my actual project. Then Unity Hub recognised the project and created it's own library, Temp folder and others inside Linux, but it's still changing the correct files on the Windows hard drive.
This technique also works for having the same project open several times and more, but it may break something as it surely isn't intended. -
sjocelyn2011
Mar 28, 2018 20:34
I am experiencing a similar problem but it is on Windows 10.
The project is fine I am able to Build the Android game on another Computer. But on my Laptop with the latest Unity 3D 2017.4 It fails with IOException
I don't understand why it would fail, the path is the same on both machines... but it fails on the Laptop every time.
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note:
Hosting projects on NTFS from Linux is not something we are likely to consider in the near future