Search Unity

Trouble build for UWP and Standalone

Discussion in 'Windows' started by samuraidragon13, Apr 12, 2018.

  1. samuraidragon13

    samuraidragon13

    Joined:
    Nov 1, 2014
    Posts:
    8
    I am having trouble doing a build for UWP and Xbox Creators Program. Everything clears fine in unity with no errors but once I trying building in VS2017 it get this

    1>------ Build started: Project: Wiliam's Game, Configuration: Debug x64 ------
    1>C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\App.cs(56,13,56,71): warning CS0618: 'ApplicationView.SuppressSystemOverlays.set' is obsolete: 'Use the TryEnterFullScreen method and IsFullScreenMode property instead of SuppressSystemOverlays. For more info, see MSDN.'
    1> Wiliam's Game -> C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\bin\x64\Debug\Wiliam's Game.exe
    1> UnityWSAPlayerDir "C:\Program Files\Unity 2017.2.0b7\Editor\Data\PlaybackEngines\MetroSupport\".
    1> UnityProjectDir "".
    1> Copying unprocessed assemblies...
    1> Running AssemblyConverter...
    1> Failed to fix references for method System.Void Poly2Tri.DTSweep::FlipEdgeEvent(Poly2Tri.DTSweepContext,Poly2Tri.TriangulationPoint,Poly2Tri.TriangulationPoint,Poly2Tri.DelaunayTriangle,Poly2Tri.TriangulationPoint)
    1> Failed to fix references for type Poly2Tri.DTSweep
    1> System.Exception: Failed to resolve System.Console
    1> at Unity.ModuleContext.Retarget(TypeReference type, GenericContext context)
    1> at Unity.ModuleContext.Retarget(MethodReference method, GenericContext context)
    1> at Unity.FixReferencesStep.Visit(MethodDefinition method, GenericContext context)
    1> at Unity.FixReferencesStep.Visit(TypeDefinition type)
    1> at Unity.TypeDefinitionDispatcher.DispatchType(TypeDefinition type)
    1> at Unity.TypeDefinitionDispatcher..ctor(ModuleDefinition module, ITypeDefinitionVisitor visitor)
    1> at Unity.FixReferencesStep.ProcessModule()
    1> at Unity.ModuleStep.Execute()
    1> at Unity.FixReferencesStep.Execute()
    1> at Unity.Step.Execute(OperationContext operationContext, IStepContext previousStepContext)
    1> at Unity.Operation.Execute()
    1> at Unity.Program.Main(String[] args)
    1>C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\Wiliam's Game.csproj(418,5): error MSB3073: The command ""C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Unity\Tools\AssemblyConverter.exe" -platform=uap -lock="C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\project.lock.json" -bits=64 -configuration=Debug -removeDebuggableAttribute=False -uwpsdk=10.0.16299.0 -path="." -path="C:\Program Files\Unity 2017.2.0b7\Editor\Data\PlaybackEngines\MetroSupport\Players\UAP\dotnet\x64\Debug" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.TerrainPhysicsModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.TerrainModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.StyleSheetsModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.TextRenderingModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.TilemapModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.PerformanceReportingModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.ParticleSystemModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.ParticlesLegacyModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.Physics2DModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.SpriteMaskModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.ScreenCaptureModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.PhysicsModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.UIElementsModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.VideoModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.VehiclesModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.UnityWebRequestWWWModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.VRModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.WindModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.WebModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.UnityAnalyticsModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.UNETModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.UIModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.UnityConnectModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.UnityWebRequestTextureModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.UnityWebRequestModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.UnityWebRequestAudioModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.AccessibilityModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.AnimationModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.AIModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\Assembly-CSharp.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\Assembly-CSharp-firstpass.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.ARModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.ImageConversionModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.GridModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.IMGUIModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.JSONSerializeModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.InputModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.CoreModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.ClothModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.AudioModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.CrashReportingModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.GameCenterModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.DirectorModule.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.Timeline.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\nunit.framework.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\Newtonsoft.Json.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.UI.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.AR.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.HoloLens.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\Poly2Tri.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\UnityEngine.Networking.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\KdTreeLib.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\pb_Stl.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\ProBuilderCore-Unity5.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\ProBuilderMeshOps-Unity5.dll" "C:\Users\Jonathon\Documents\RitualGamesCompany\Builds\Wiliam's Game\Microsoft.Xbox.Services.UWP.CSharp.dll"" exited with code 1.
    ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

    I have tried other solutions on the forums like downgrading vs2017 to version 15.0. I have had to change my version of unity from 2017.4 to 2017.2.0b7 because 2017.4 was giving me build errors that don't come up in 2017.2.

    I can't even get unity to do a standalone build so that I can test out my game outside of the editor. It goes through all the motions of doing a build but nothing gets generated. Like I will click on build and the loading icon in the bottom corner of unity will spin and the build button will grey out but no results show up and it won't say that the build was successful in the console log.

    Is there anything that I can do get a build going?
     
  2. samuraidragon13

    samuraidragon13

    Joined:
    Nov 1, 2014
    Posts:
    8
    So i was able to finally do a Standalone build it it only worked after I removed the xbox live unity package from my project.
     
  3. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,680
    Do you get any errors in Unity console when you build for UWP?
     
  4. markgrossnickle

    markgrossnickle

    Joined:
    Aug 21, 2017
    Posts:
    32
    I get this same error when compiling a UWP build for Hololens or Mixed reality in visual studio. It builds fine in Unity but compiling directly to the device or building to a package to install fails with:


    1> Running AssemblyConverter...
    1> "C:\projects\Shepherd\UWP\Unity\Tools\AssemblyConverter.exe" -platform=uap -bits=32 -configuration=Release -removeDebuggableAttribute=False -uwpsdk=10.0.17134.0 -path="." -path="C:\Program Files\Unity 2018.2.0b3\Editor\Data\PlaybackEngines\MetroSupport\Players\UAP\dotnet\x86\Release" -workingDir="C:\projects\Shepherd\UWP\Garment\\" "@C:\projects\Shepherd\UWP\Garment\AssemblyConverterArgs.txt"
    1> Failed to fix references for method System.Void Poly2Tri.DTSweep::FlipEdgeEvent(Poly2Tri.DTSweepContext,Poly2Tri.TriangulationPoint,Poly2Tri.TriangulationPoint,Poly2Tri.DelaunayTriangle,Poly2Tri.TriangulationPoint)
    1> Failed to fix references for type Poly2Tri.DTSweep
    1> System.Exception: Failed to resolve System.Console
    1> at Unity.ModuleContext.Retarget(TypeReference type, GenericContext context)
    1> at Unity.ModuleContext.Retarget(MethodReference method, GenericContext context)
    1> at Unity.FixReferencesStep.Visit(MethodDefinition method, GenericContext context)
    1> at Unity.FixReferencesStep.Visit(TypeDefinition type)
    1> at Unity.TypeDefinitionDispatcher.DispatchType(TypeDefinition type)
    1> at Unity.TypeDefinitionDispatcher..ctor(ModuleDefinition module, ITypeDefinitionVisitor visitor)
    1> at Unity.FixReferencesStep.ProcessModule()
    1> at Unity.ModuleStep.Execute()
    1> at Unity.FixReferencesStep.Execute()
    1> at Unity.Step.Execute(OperationContext operationContext, IStepContext previousStepContext)
    1> at Unity.Operation.Execute()
    1> at Unity.Program.Main(String[] args)

    I read on ProCore3D's forums that I would need to disable some of their dlls in order for it to work in UWP:
    http://www.procore3d.com/forum/topi...crosoft-hololens-when-using-probuilder-basic/

    Two questions:
    1. Will runtime UWP support be coming to ProBuilder anytime soon?
    2. I don't seem to be able to Exclude Platforms on any dll file within a Package. I am using Unity 2018.2.0b3. Is that a bug or intended behavior? I tried to exclude the ProBuilder/Classes as that forum post suggests but they are greyed out.

    Thanks for any insight you may be able to provide.
     
  5. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,680
    It should work just fine if you switch to IL2CPP scripting backend.

    Can we get a bug report on this?
     
  6. markgrossnickle

    markgrossnickle

    Joined:
    Aug 21, 2017
    Posts:
    32
    Bug reported: Case 1058892

    Switching to IL2CPP did the trick. Thank you!