Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.2.X, 2019.3.X
[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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
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.