Search Issue Tracker
Fixed in 4.6.5
Votes
0
Found in
5.0.0f4
Issue ID
677960
Regression
No
[WSA] Build and run error in the editor
Pressing "build and run" button when building to WSA platform (specific build parameters are given below) editor shows such error:
---
Exception: Failed to build Visual Studio project. Output:
UnityInstallationDir "C:\Program Files\Unity\Editor".
UnityWSAPlayerDir "C:\Program Files\Unity\Editor\Data\PlaybackEngines\metrosupport".
UnityProjectDir "C:\BUILD AND RUN TEST\510a3".
Copying unprocessed assemblies...
C:\BUILD AND RUN TEST\510a3\Assembly-CSharp-metro-vs2013.csproj(3,3): error MSB4019: The imported project "C:\BUILD AND RUN TEST\510a3\UnityCommon.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
C:\BUILD AND RUN TEST\510a3\Assembly-CSharp-firstpass-metro-vs2013.csproj(3,3): error MSB4019: The imported project "C:\BUILD AND RUN TEST\510a3\UnityCommon.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
---
More of errors are in the attached log file "log.txt";
"Build and run" doesn't make error to appear when building to WSA, sdk8.1, without Unity C# projects
Reproducible on 4.5, 4.6. 5.0, 5.1;
Different version provides slightly different error messages;
Repro steps:
1. create an empty project;
2. set such settings in build settings:
>sdk: 8.0, without Unity C# projects
or
>sdk: 8.0, with Unity C# projects
or
>sdk: 8.1, with Unity C# projects
3. press "build and run" button;
Workaround: don't use "build and run" button.
Comments (2)
Add comment
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Fabien Renaud
Jul 08, 2015 18:33
I have the same issue with Unity 5.1.1f1 and i'm building from command line.