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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment