Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.1.1f1
Issue ID
1062210
Regression
Yes
Unity throws Visual Studio integration related XMLException when the project is located in a path containing '&'
How to reproduce:
1. Create a folder named "Project&"
2. Create a new Unity project inside this folder
3. Open the project in Unity
4. Create a new script
5. Observe console
Expected result: Unity is able to work with projects located in folders containing '&' characters
Actual result: Unity throws an unclear error message indicating that some illegal character has been encountered
Reproducible with: 2018.1.9f1, 2018.2.1f1, 2018.3.0a6
Not reproducible with: 2017.1.5f1, 2017.2.3p2, 2017.4.8f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment