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
- Field names under "Anchors" in the RectTransform Component don't get focused when "tabbing" through the fields
- [macOS] Project Browser's Search by Type stops working after importing Assets into a Project and searching for Types "In Assets"
- The Particle System Trail module creates Trails with a lighter coloring than the particles when the Color Space is set to Linear
- Crash on "DynamicBranchState::PrepareState" when entering the Play Mode with a shader variant collection that has a shader with a "dynamic_branch" keyword
- Crash on "in __pthread_kill" when running the built application that has UNITY_EDITOR scripting symbol in conditional compilation
Add comment