[TIMOB-26139] Windows: Unable to build to device when using Windows SDK 15063 and newer tooling is installed
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2018-07-12T03:21:24.000+0000 |
Affected Version/s | Release 7.3.0, Release 7.2.0 |
Fix Version/s | Release 7.3.0 |
Components | Windows |
Labels | n/a |
Reporter | Josh Longton |
Assignee | Kota Iguchi |
Created | 2018-06-19T14:25:01.000+0000 |
Updated | 2018-08-26T01:45:40.000+0000 |
Description
I am unable to build applications to windows device.
*Steps to reproduce*
Build to device
*Log and Error*
https://gist.github.com/longton95/62ab044c898b31ef92f35048cb72d735
*Log and Error with --deploy-type production flag*
https://gist.github.com/longton95/320cb804efbfee3f3b1c25029bc72856
[~jlongton] I am still unable to reproduce this. I saw similar issue on the [developer forum](https://developercommunity.visualstudio.com/content/problem/135719/build-full-database-file-for-solution-fails-for-st.html) which suggests to update Visual Studio...Would you try to update Visual Studio 2017 to the latest state just in case? (Go to Control Panel -> All Control Panel Items -> Programs and Features -> Select "Visual Studio Community 2017" -> Change)
[~kiguchi] I tried the update and still got the same error, I then completely removed visual studio from my machine and reinstalled from scratch but I still see the error.
[~eharris] Any ideas on this?
[~kiguchi] Nothing I can shed any light on sorry :/, I'm reinstalling Windows soon so I'll aim to get it done ASAP and then hopefully see if I run into this issue
[~jlongton] Could you try listing what VS compoenents are installed on your machine. - Install [vssetup](https://github.com/Microsoft/vssetup.powershell) by opening powershell (maybe in administrator) and run
Install-Module VSSetup -Scope CurrentUser
- Run the below command to list all the things you have installed[~eharris] {noformat} Name: Visual Studio Community 2017 Type Id ---- -- Workload Microsoft.VisualStudio.Workload.CoreEditor Workload Microsoft.VisualStudio.Workload.NativeDesktop Workload Microsoft.VisualStudio.Workload.Universal Workload Microsoft.VisualStudio.Workload.VisualStudioExtension Component Microsoft.Component.ClickOnce Component Microsoft.Component.MSBuild Component Microsoft.Component.NetFX.Native Component Microsoft.Component.VC.Runtime.OSSupport Component Microsoft.ComponentGroup.Blend Component Microsoft.Net.Component.4.5.TargetingPack Component Microsoft.Net.Component.4.6.1.SDK Component Microsoft.Net.Component.4.6.1.TargetingPack Component Microsoft.Net.Component.4.6.TargetingPack Component Microsoft.Net.Component.4.7.1.SDK Component Microsoft.Net.ComponentGroup.DevelopmentPrerequisites Component Microsoft.Net.Core.Component.SDK Component Microsoft.VisualStudio.Component.AppInsights.Tools Component Microsoft.VisualStudio.Component.CoreEditor Component Microsoft.VisualStudio.Component.Debugger.JustInTime Component Microsoft.VisualStudio.Component.DiagnosticTools Component Microsoft.VisualStudio.Component.Graphics Component Microsoft.VisualStudio.Component.Graphics.Tools Component Microsoft.VisualStudio.Component.Graphics.Win81 Component Microsoft.VisualStudio.Component.JavaScript.Diagnostics Component Microsoft.VisualStudio.Component.JavaScript.TypeScript Component Microsoft.VisualStudio.Component.NuGet Component Microsoft.VisualStudio.Component.Phone.Emulator.15254 Component Microsoft.VisualStudio.Component.PortableLibrary Component Microsoft.VisualStudio.Component.Roslyn.Compiler Component Microsoft.VisualStudio.Component.Roslyn.LanguageServices Component Microsoft.VisualStudio.Component.SQL.CLR Component Microsoft.VisualStudio.Component.Static.Analysis.Tools Component Microsoft.VisualStudio.Component.TextTemplating Component Microsoft.VisualStudio.Component.TypeScript.2.8 Component Microsoft.VisualStudio.Component.UWP.Support Component Microsoft.VisualStudio.Component.VC.ATL Component Microsoft.VisualStudio.Component.VC.CMake.Project Component Microsoft.VisualStudio.Component.VC.CoreIde Component Microsoft.VisualStudio.Component.VC.DiagnosticTools Component Microsoft.VisualStudio.Component.VC.Redist.14.Latest Component Microsoft.VisualStudio.Component.VC.TestAdapterForBoostTest Component Microsoft.VisualStudio.Component.VC.TestAdapterForGoogleTest Component Microsoft.VisualStudio.Component.VC.Tools.ARM Component Microsoft.VisualStudio.Component.VC.Tools.ARM64 Component Microsoft.VisualStudio.Component.VC.Tools.x86.x64 Component Microsoft.VisualStudio.Component.VisualStudioData Component Microsoft.VisualStudio.Component.VSSDK Component Microsoft.VisualStudio.Component.Windows10SDK.15063.Desktop Component Microsoft.VisualStudio.Component.Windows10SDK.15063.UWP Component Microsoft.VisualStudio.Component.Windows10SDK.15063.UWP.Native Component Microsoft.VisualStudio.Component.Windows10SDK.16299.Desktop Component Microsoft.VisualStudio.Component.Windows10SDK.16299.Desktop.arm Component Microsoft.VisualStudio.Component.Windows10SDK.16299.UWP Component Microsoft.VisualStudio.Component.Windows10SDK.16299.UWP.Native Component Microsoft.VisualStudio.Component.Windows10SDK.17134 Component Microsoft.VisualStudio.ComponentGroup.NativeDesktop.Core Component Microsoft.VisualStudio.ComponentGroup.UWP.Cordova Component Microsoft.VisualStudio.ComponentGroup.UWP.NetCoreAndStandard Component Microsoft.VisualStudio.ComponentGroup.UWP.VC Component Microsoft.VisualStudio.ComponentGroup.UWP.Xamarin Component Microsoft.VisualStudio.ComponentGroup.VisualStudioExtension.Prerequisites Component Microsoft.VisualStudio.ComponentGroup.WebToolsExtensions {noformat}
Took Josh's installed components and built a install config from it, able to reproduce the error. Attempting to work backwards to figure out what the cause is. Attached the config, to use it download the VS 2017 installer and then run it from command line with
--in <path_to_config>
so likeC:\Users\awam\Downloads\vs_community__733517741.1530097118.exe --in C:\Users\awam\Desktop\config.json
Removed the following packages and wp-device builds started working again
Even though Josh has newer SDK, because of the check [here](https://github.com/appcelerator/titanium_mobile_windows/blob/9eb09da5eec1d3ab35419d30cbf05352e422c768/cli/commands/_build/generate.js#L158-L164), and our minimum sdk stated [here](https://github.com/appcelerator/titanium_mobile_windows/blob/9eb09da5eec1d3ab35419d30cbf05352e422c768/package.json#L29), 15063 is always getting selected. 15063 was fairly heavily tested when it was released due to the VS2015 incompatibility bugs we fixed see (TIMOB-25031 and related tickets). I'm unsure as to why it is now suddenly breaking, it could be due to incompatibilities with newer tooling? I'm currently uninstalling the newer SDKs and seeing if that fixes anything. I think we definitely need to upgrade the min supported versions
I just got my PC clean-installed with VS 2017, and now I am able to reproduce this issue. I can see that 15063 sdk is selected even when I should have newer versions. I'll try to upgrade min supported versions.
https://github.com/appcelerator/titanium_mobile_windows/pull/1268
7_3_X backport: https://github.com/appcelerator/titanium_mobile_windows/pull/1269
Merged to master and 7_3_X. Should be available on tomorrow's nightly build.
*Closing ticket.* The fix is present in SDK: {noformat} 7.3.0.v20180711185043 {noformat} Thanks [~kiguchi]