Search Issue Tracker
Fixed in 2020.2.X
Votes
4
Found in
2020.2.0a21
Issue ID
1270452
Regression
Yes
"Failed copying file" error message appears while dragging file from Explorer to the Editor
Steps:
1. Create a new project
2. Drag file (e.g. scene asset, 3d model, etc. ) from OS (Explorer in case of Windows) to the Editor
==>
Expected results: Asset is imported successfully
Actual results: "Failed copying file" error message appears Asset is not added to the Unity project
Reproducible with: 2020.2.0a21, 2020.2.0b1
Not reproducible with: 2018.4.27f1, 2019.4.9f1, 2020.1.4f1, 2020.2.0a20, 2020.2.0b4
Workaround: Copy the file into Assets folder manually using OS (Explorer in case of Windows)
Comments (1)
-
Tobydoo2
Sep 25, 2020 06:03
I've had this issue multiple times, but don't want to downgrade as it doesn't cause some errors. any possible ways to fix this or alternative ways?
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.2):
No longer reproduces with - 2020.2.0b4