[TIMOB-23758] Windows: Unable to build to 10.0.10586 emulator after installing Windows SDK 10.0.14393

GitHub Issue	n/a
Type	Bug
Priority	None
Status	Closed
Resolution	Fixed
Resolution Date	2016-08-16T17:35:41.000+0000
Affected Version/s	Release 5.4.0
Fix Version/s	Release 6.1.0
Components	Windows
Labels	qe-5.4.0
Reporter	Ewan Harris
Assignee	Kota Iguchi
Created	2016-08-10T19:02:29.000+0000
Updated	2017-05-08T19:19:04.000+0000

Description

After installing Windows 10 SDK 10.0.14393 I can no longer build to a 10.0.10586 emulator. The build fails on install with the error below. This is because in the apps solution file the minimum SDK is set to 10.0.14393, it should be set to one of the following.

Lowest possible version of Windows 10, 10.0.10240.0

Lowest version installed on development machine

I will file a separate ticket to allow these SDK values to be configured by the user in the tiapp.xml

[ERROR] :  Failed to install app (code 2148734208): Windows App Deployment Tool
Version 10.0.0.0
Copyright (c) Microsoft Corporation. All rights reserved.
Opening connection to device at '169.254.119.193'.
Installing app...
Disconnecting.
0x80131500 - Failed to install or update package: Unspecified error
0x80131500 - Unspecified error
[ERROR] :  Error: Failed to install app (code 2148734208): Windows App Deployment Tool
Version 10.0.0.0
Copyright (c) Microsoft Corporation. All rights reserved.
Opening connection to device at '169.254.119.193'.
Installing app...
Disconnecting.
0x80131500 - Failed to install or update package: Unspecified error
0x80131500 - Unspecified error
    at ChildProcess.<anonymous> (C:\ProgramData\Titanium\mobilesdk\win32\5.4.0.v20160804185318\node_modules\windowslib\lib\wptool.js:827:10)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at maybeClose (internal/child_process.js:827:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)

*Notes* I believe this is true for devices, but I do not have a device with an OS version lower than 10.0.14393 to test this theory. Some information about these settings can be found [here](https://msdn.microsoft.com/library/windows/apps/mt590210.aspx?f=255&MSPPError=-2147217396)

Steps to reproduce

On a machine with 10.0.14393 SDK installed build to a 10.0.10586 emulator

Actual result

The build will fail

Expected result

The build should not fail

Attachments

File	Date	Size
emulator10586issue.txt	2017-02-07T21:40:35.000+0000	29595

Comments

Kota Iguchi 2016-08-12

https://github.com/appcelerator/titanium_mobile_windows/pull/818
Kota Iguchi 2016-08-15

https://github.com/appcelerator/titanium_mobile_windows/pull/818

Samir Mohammed 2017-01-27

Hey [~kota] when trying to run a 10.0.10586 emulator I get the following error even if no previous application has been installed.

   [ERROR] :  A debug application is already installed, please remove existing debug application
   [ERROR] :  Error: A debug application is already installed, please remove existing debug application
       at ChildProcess.<anonymous> (C:\ProgramData\Titanium\mobilesdk\win32\6.1.0.v20170126175503\node_modules\windowslib\lib\wptool.js:834:15)
       at emitTwo (events.js:87:13)
       at ChildProcess.emit (events.js:172:7)
       at maybeClose (internal/child_process.js:829:16)
       at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)

Any idea why? (Windows 8.1 emulator and Windows 10.0.14393 seem to be working fine) *Environment*

   
   Appc Studio version: 4.8.1.201701192045 
   Mobile emulator: 10.0.10586 1080p  6inch 2gb
   Operating System:
   Name                        = Microsoft Windows 10 Pro
   Version                     = 10.0.14393
   Architecture                = 64bit
   CPUs                      = 4
   Memory                      = 17034395648
    
   Node.js:
   Node.js Version             = 4.6.0 
   npm Version                 = 2.11.3
    
   Titanium SDK:
   SDK Version                 =  6.1.0.v20170126175503

Kota Iguchi 2017-02-06

[ERROR] : A debug application is already installed, please remove existing debug application As far as I know, this could happen when there is already an app installed that has same guid. I am wondering if there is already another Titanium application installed? Please check out the guid in the tiapp.xml and changing it may work to avoid this installation error.
Samir Mohammed 2017-02-06

[~kota] Even after changing the guid I am still getting the same installation error.
Abir Mukherjee 2017-02-07

[~kota] I am seeing the same as [~smohammed] in Studio. I also tried a new GUID, and still see the same failure. Although I don't see the error message using the CLI, it still does fail and the app doesn't launch. I attached the log when using the CLI.

Kota Iguchi 2017-02-08

[~smohammed] [~amukherjee] I forgot to mention about the required configuration about target platform version. You need to specify target platform version in this case, you can specify it on your tiapp.xml or through --wp-sdk option.

   ...
   <windows>
       ...
       <TargetPlatformVersion>10.0.10586.0</TargetPlatformVersion>
       <TargetPlatformMinVersion>10.0.10586.0</TargetPlatformMinVersion>
       ...
   </windows>
   ...
   
   and then
   
   appc run -p windows --target wp-emulator

Or you can specify it through --wp-sdk option.

   appc run -p windows --target wp-emulator --wp-sdk 10.0.10586.0

Abir Mukherjee 2017-02-22

Environment: NPM Version: 2.15.9 Node Version: 4.6.0 Windows OS: 10.0.14393.693 Appc CLI: 6.1.0 Appc CLI NPM: 4.2.8 Titanium SDK version: 6.1.0.v20170220091247 Appcelerator Studio, build: 4.8.1.201612050850 Windows Emulator: 10.0.10586.0 I was able to validate the fix using both CLI and through Studio. I tried three different ways, all were found to work as expected: 1. Typing this command on CLI: appc run -p windows --target wp-emulator --wp-sdk 10.0.10586.0. 2. Modifying tiapp.xml as Kota stated in his comment, and typing on CLI: appc run -p windows --target wp-emulator. 3. Installing app within Studio and modifying tiapp.xml as stipulated by Kota in his comment above.

JSON Source