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)
-
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
- Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
- [Linux][OpenGL][Vulkan] Draw calls are not shown in the Event List when taking a capture of a frame with RenderDoc
- Inaccurate collision detections when Rigidbody Collision Detection is set to "Continuous" or "Continuous Dynamic"
- Crash on Object::IncrementPersistentDirtyIndex when upgrading project version
- [iOS] Multiple Xcode project instances created before opens up when performing Build and Run for iOS Platform
Resolution Note (fix version 2020.2):
No longer reproduces with - 2020.2.0b4