Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.4f1
Issue ID
1141686
Regression
No
"System.IO.DirectoryInfo.CheckPath" doesn't recognize .NET's long path prefix, results in error "ArgumentException: path"
Reproduction steps:
1. Download "long path.zip"
2. Run "case_1141686-long_path" -> "CreateTestFiles" -> "CreateTestFiles"
3. Enable Long Paths in Windows (https://blogs.msdn.microsoft.com/jeremykuhne/2016/07/30/net-4-6-2-and-long-paths-on-windows-10/)
4. Open "case_1141686-long_path" project
5. "Window " -> "File Copy"
6. "Copy Texture from long path"
7. Notice Error "ArgumentException: path"
Expected Result: No errors when using long paths
Actual Result: "ArgumentException: path" when using long paths
Reproduced with: 2019.2.0a10, 2019.1.0b10, 2018.3.11f1, 2017.4.24f1
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
After internal discussion we are classifying this issue as a feature request. Unity does not support the Windows long path prefix historically. We intend to support this at some point, but it will involve a larger effort than a bug fix. We'll need to ensure all file related APIs and code paths can handle this (and are tested).