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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment