Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.3.X
Votes
0
Found in
5.6.3p3
Issue ID
959804
Regression
No
[WSA] MSBuild step fails if project contains files with ampersand in their name
Steps to reproduce:
1. Open the attached project
2. Switch platform to Windows Store
3. Build for WSA Universal 10
4. Observe the error:
ApplicationLauncherImpl.RunMSBuild (System.String args)
Actual results: Unity throws the error
Expected results: Unity should not throw the error
Reproduced with: 5.5.5p1, 5.6.4p1, 2017.1.2p2, 2017.2.f3, 2018.1.0a1
Fixed: 2017.3.0f2, 2018.1.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Remote Config] PreparePayloadWithConfigType function is looking for camelCase property names, when the JSON objects are using PascalCase naming
- UI Builder Viewport's Tool Gizmo has deadzones
- SpriteShapes are rendered using multiple draw calls when the SRP Batcher determines their nodes are incompatible in a specific project
- UI Toolkit Debugger "Pick Element" selects Scene view panel when trying to select a world space UI element in the Scene view
- MSAA warnings are thrown when custom post-processing is used and the Scene contains transparent GameObjects
Add comment