Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.0f3
Issue ID
959984
Regression
No
[WSA] System.IO.DirectoryNotFoundException when exporting to WSA player (UWP/.NET Backend) with long project folder
Steps to reproduce:
1. Create a new project
2. Switch platform to Windows Store
3. Build for WSA Universal 10 to a folder with a long path (e.g D:\Cases\UWP\1\2\3\4\5\6\7\8\9\10\11\12)
4. Observe the error:
System.IO.DirectoryNotFoundException
Actual results: Unity throws the error
Expected results: Unity should not throw the error
Reproduced with: 2017.2.f1, 2017.3.0b6
Not reproduced with: 5.5.5p1, 5.6.4p1, 2017.1.2p2, 2017.2.f3, 2018.1.0a1
Why won't fix: .NET scripting backend is deprecated starting Unity 2018.2, this bug has an easy workaround and it doesn't reproduce on IL2CPP.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Dynamic Clipping works poorly with large scenes / terrains with the pivot point is near
- [UWP] Deploying wrong architecture through device portal ends up running a different app
- [MacOS] Standalone build contains .meta files inside native plugin bundles
- Progressive lightmapper leaks memory upon subsequent scene switches and bakes
- [AssetBundle] "The referenced script (Unknown) on this Behaviour is missing!" errors when loading object from Asset Bundle
Add comment