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
- Scene Asset is not attached to a Lighting Data Asset for a URP Package Sample Scene
- Gizmos are not rendered for the Base Camera when using Camera Stacking
- UI Mask Component does not apply correctly when Canvas Render Mode is set to Screen Space - Camera
- UI Toolkit Dropdown list elements use default color instead of USS color override when hovering mouse over them
- BuildOptions.Development is ignored when running a batch mode build for the win64 buildTarget
Fabien Renaud
Jul 08, 2015 18:33
I have the same issue with Unity 5.1.1f1 and i'm building from command line.