Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.2.X, 2019.3.X
Votes
1
Found in
2019.1.5f1
Issue ID
1160455
Regression
No
[Scripting/Import] Scripts do not get compiled if the Unity Editor installation path contains apostrophes
How to reproduce:
1. Make sure your Unity Editor path contains an apostrophe (single quote character).
2. Create a new project
3. Create a new C# script and try to recompile it
Expected results: The script gets reimported and compiled
Actual results: The script doesn't compile and throws a "Win32Exception: The system cannot find the file specified." error
Reproducible with: 2017.4.29f1, 2018.4.2f1, 2019.1.6f1, 2019.2.0b5, 2019.3.0a5
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
- [macOS] Project fails to load when Virtual Artifacts are Corrupted
- Long scheduler times on main thread when using InstantiateAsync with a singular massive Prefab
- The project hangs upon opening it when importing the "discrete_rank2_vector_v2_0.onnx" file
- Opening the Look Dev hangs the Editor when the window is opened for the first time in the project or after deleting the Library folder
- Look Dev has blurry icons on 4k monitors
Resolution Note (fix version 2020.1):
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this issue.