Search Unity

  1. Unity 2018.3 is now released.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. We've updated our Terms of Service. Please read our blog post from Unity CTO and Co-Founder Joachim Ante here
    Dismiss Notice
  4. Want to provide direct feedback to the Unity team? Join the Unity Advisory Panel.
    Dismiss Notice
  5. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice

Unity UWP build fails in visual studio

Discussion in 'Editor & General Support' started by Astrobyte_, Sep 16, 2018.

  1. Astrobyte_


    Jun 30, 2015
    I am currently trying to build my game for xbox one, using UWP build module. The app export succeeds, but when attempting to build for a remote or local machine in VS 2017, the build fails with the following error.

    Error The command ""C:\Users\USERNAME\Unity Game Builds\GAMENAME\Builds\XboxBuilds\Trial8\Unity\Tools\AssemblyConverter.exe" -platform=uap -bits=64 -configuration=Release -removeDebuggableAttribute=False -uwpsdk=10.0.17134.0 -path="." -path="C:\Program Files\Unity\Hub\Editor\2018.2.8f1\Editor\Data\PlaybackEngines\MetroSupport\Players\UAP\dotnet\x64\Release" -workingDir="C:\Users\USERNAME\Unity Game Builds\GAMENAME\Builds\XboxBuilds\Trial8\GAMENAME\\" "@C:\Users\USERNAME\Unity Game Builds\GAMENAME\Builds\XboxBuilds\Trial8\GAMENAME\AssemblyConverterArgs.txt"" exited with code 1. GAMENAME C:\Users\USERNAME\Unity Game Builds\GAMENAME\Builds\XboxBuilds\Trial8\GAMENAME\GAMENAME.csproj 509

    (I replaced my name with ''USERNAME" and the project name with "GAMENAME")
    I'm on unity version 2018.2.8.f1 and the latest version of VS. Here are my player settings:

    Any help would be very appreciated. I'm just trying to test my game on my Xbox one. Thanks in advance to any replies.
  2. Tautvydas-Zilys


    Unity Technologies

    Jul 25, 2013
    It's likely you have an incompatible with .NET scripting backend DLL in your project somewhere. Do you get any errors in the console when you build from Unity?

    An easy fix would be to switch to IL2CPP scripting backend.