Search Issue Tracker
Fixed in 5.2.1
Votes
0
Found in
5.2.0f2
Issue ID
724566
Regression
No
BuildPipeline.BuildPlayer WSAPlayer fails to run when given a relative path
To reproduce:
1. Open attached project.
2. In the menu bar navigate to Build > build
3. This starts building the player. BuildOption.AutoRunPlayer is also set
4. Notice the errors in the console: Exception: Failed to build Visual Studio project.
This is happening due to 2 things, the BuildOption.AutoRunPlayer and the relative path given. If you don't do an autoRun or you provide an absolute path this issue can be workarounded. It appears that the solution generated can still be deployed manually, but it's not deployed/run automatically)
This does not happen when targeting WP8Player, so appears to be WSA specific. (Tried WSASDK.SDK81 and WSASDK.PhoneSDK81)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment