search

appveyor / ci

AppVeyor community support repository
https://www.appveyor.com
344 stars 66 forks source link

Universal Windows Platform Fall Creators Update fails to build #1984

Open godrose opened 6 years ago

godrose commented 6 years ago

Hi. I recently updated the UWP project to the latest version - FCU And referenced the .NETStandard 2.0 library. It compiles fine locally but fails to do so at appveyor.

Attached is the build's log The repo can be found at https://ci.appveyor.com/project/LogoFX/logofx-client-core log.txt

IlyaFinkelshteyn commented 6 years ago

@godrose what version of OS it builds on locally? I wonder if this is the same issue as discussed here and here.

godrose commented 6 years ago

@IlyaFinkelshteyn 1709. It looks like it's the same or very closely related indeed

IlyaFinkelshteyn commented 6 years ago

Yes, that's it. We are investigating. As you see this is tricky because Server OS has no UI... Please watch https://github.com/appveyor/ci/issues/1885.

allanrsmith commented 6 years ago

Go here: https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk

Supported operating systems
Windows 10 App Development (UWP) 
Windows 10 version 1507 or higher: Home, Professional, Education, and Enterprise (LTSB and S are not supported)
Windows Server 2012 R2 (Command line only) Windows Server 2016 (Command Line only)

Here is the direct link to the installer: https://go.microsoft.com/fwlink/p/?linkid=870807

allanrsmith commented 6 years ago

@FeodorFitsner it has been almost 6 months since this ticket was opened. What can we do about this?

allanrsmith commented 6 years ago

image

FeodorFitsner commented 6 years ago

@allanrsmith Windows 10 Fall Creators Update SDK (10.0.16299) is already installed on the current Visual Studio 2017 image:

image

What you are referring to (looking at the screenshot with error) is Windows SDK 1803 (10.0.17134) which is scheduled for this week update: https://github.com/appveyor/ci/issues/2296

godrose commented 6 years ago

@FeodorFitsner So what does this mean? Should this configuration work already? I'm still getting the UWP build errors:

    NU1201: Project LogoFX.Client.Mvvm.ViewModel is not compatible with uap10.0.16299 (UAP,Version=v10.0.16299). Project LogoFX.Client.Mvvm.ViewModel supports: netstandard2.0 (.NETStandard,Version=v2.0)
214    NU1201: Project LogoFX.Client.Mvvm.ViewModel is not compatible with uap10.0.16299 (UAP,Version=v10.0.16299) / win10-arm. Project LogoFX.Client.Mvvm.ViewModel supports: netstandard2.0 (.NETStandard,Version=v2.0)
215    NU1201: Project LogoFX.Client.Mvvm.ViewModel is not compatible with uap10.0.16299 (UAP,Version=v10.0.16299) / win10-arm-aot. Project LogoFX.Client.Mvvm.ViewModel supports: netstandard2.0 (.NETStandard,Version=v2.0)
216    NU1201: Project LogoFX.Client.Mvvm.ViewModel is not compatible with uap10.0.16299 (UAP,Version=v10.0.16299) / win10-x64. Project LogoFX.Client.Mvvm.ViewModel supports: netstandard2.0 (.NETStandard,Version=v2.0)
217    NU1201: Project LogoFX.Client.Mvvm.ViewModel is not compatible with uap10.0.16299 (UAP,Version=v10.0.16299) / win10-x64-aot. Project LogoFX.Client.Mvvm.ViewModel supports: netstandard2.0 (.NETStandard,Version=v2.0)
218    NU1201: Project LogoFX.Client.Mvvm.ViewModel is not compatible with uap10.0.16299 (UAP,Version=v10.0.16299) / win10-x86. Project LogoFX.Client.Mvvm.ViewModel supports: netstandard2.0 (.NETStandard,Version=v2.0)
219    NU1201: Project LogoFX.Client.Mvvm.ViewModel is not compatible with uap10.0.16299 (UAP,Version=v10.0.16299) / win10-x86-aot. Project LogoFX.Client.Mvvm.ViewModel supports: netstandard2.0 (.NETStandard,Version=v2.0)
220
allanrsmith commented 6 years ago

Turns out we had a patch from many months ago in our appveyor.yml file: ps: (New-Object Net.WebClient).DownloadFile('https://raw.githubusercontent.com/appveyor/ci/master/scripts/hot-fixes/vs2017-uwp-scale-100-fix/Microsoft.AppxPackage.Targets', "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\AppxPackage\Microsoft.AppxPackage.Targets") Once we removed that the build worked. Make sure you don’t also have that patch as it has been fixed.

godrose commented 6 years ago

@allanrsmith The .yaml file is very basic and does not include any scripts. Anyway, this is less relevant now as I'm able to use 1803 version and it compiles fine!