Command Exited with Code 1 - "AsseblyConverter.exe" -platform=uap

Unity Engine
1

I am attempting to compile and build for Windows Store a current project, however I get the following error below:

" The command ““C:\Chirpy-Bird\Unity\Tools\AssemblyConverter.exe” -platform=uap -lock=“C:\Chirpy-Bird\Flappy Bird Style\project.lock.json” -bits=32 -configuration=Debug -removeDebuggableAttribute=False -uwpsdk=10.0.10586.0 -path=”." -path=“C:\Program Files\Unity\Editor\Data\PlaybackEngines\MetroSupport\Players\UAP\dotnet\x86\Debug” “C:\Chirpy-Bird\Flappy Bird Style\Assembly-CSharp.dll” “C:\Chirpy-Bird\Flappy Bird Style\UnityEngine.dll” “C:\Chirpy-Bird\Flappy Bird Style\nunit.framework.dll” “C:\Chirpy-Bird\Flappy Bird Style\UnityEngine.UI.dll” “C:\Chirpy-Bird\Flappy Bird Style\UnityEngine.Networking.dll”" exited with code 1. Flappy Bird Style C:\Chirpy-Bird\Flappy Bird Style\Flappy Bird Style.csproj 257 "

  • I have checked NuGet pacakges, references and pre-build settings and post-build settings to see references to this command. However I could not find nothing and having a bit of problems. Can anybody help me with this issue?

Thank You,

Adam Barbour

2

This looks like a similar issue (c# - Hololens Build Failing - The command AssemblyConverter.exe exited with code 1 - Stack Overflow) - could be a conflict between your Visual Studio version and your Unity one?

3

Ok! Good News!!

I’ve hit a breaking point. Thank you for your message Tonemcbride, however I did some more research and it seemed to be an incompatibility issue with Unity 5.6.1 p2 so I upgraded to 2017.2 Unity and it worked!

The issue I had however was when I debugged and built the program, I got the following error:

The program ‘[31984] Flappy Bird Style.exe’ has exited with code -1 (0xffffffff).
and there was another exited with code -0 but I forgot to copy that from the console.

The above errors occurred for the following reason:
“The program hits a breakpoint once you go through an exception”.

For the above, I simply built and compiled the program without debugging in Visual Studio 2017 and it worked awesomely well! I also did release version.

For anyone wanting to know how to do this simply hit Ctrl+F5 or Debug>Start without debugging.

I will work on a solution to figure out the problem with the exception error and come back with a reply.

I hope this helps for anyone having problems building a unity game for the Windows Store.

Regards,

Adam Barbour.

1 Like