Description
When building to a Windows Mobile device or emulator that already has a different Titanium application installed the CLI will hang on the install of the application, it appears that similar to TIMOB-23762 the error code/message has been changed in the new tooling.
Running winappdeploycmd manually gives me the below. Code appears to be
2148734208
C:\Users\Ewan\Documents\Appcelerator_Studio_Workspace\preprodalloy>"C:\Program Files (x86)\Windows Kits\10\bin\x86\WinAppDeployCmd.exe" install -file C:\Users\Ewan\Documents\Appcelerator_Studio_Workspace\preprodalloy\build\windows\win10.ARM\AppPackages\Preprodalloy\Preprodalloy_1.0.0.0_Debug_Test\Preprodalloy_1.0.0.0_ARM_Debug.appxbundle -ip 127.0.0.1
Windows App Deployment Tool
Version 10.0.0.0
Copyright (c) Microsoft Corporation. All rights reserved.
Opening connection to device at '127.0.0.1'.
Installing app...
Disconnecting.
0x80131500 - Failed to install or update package: Unspecified error
0x80131500 - Unspecified error
Steps to reproduce
Build an application to a Windows mobile device or emulator
Without uninstalling the previous app, build a different app to a Windows mobile device or emulator
Actual result
The CLI seems to hang on install
Expected result
As with previous SDKs the CLI should log an error to the user telling them to uninstall the other app
https://github.com/appcelerator/windowslib/pull/54 Note: This needs to be pushed to
titanium_mobile 6_0_Xin order to close this ticket.[6_0_X] https://github.com/appcelerator/titanium_mobile/pull/8272 [master] https://github.com/appcelerator/titanium_mobile/pull/8275
Verified using: OS: Microsoft Windows 10 Pro 10.0.14393 Appc core: 6.0.0-38 Appc NPM: 4.2.8-6 Ti SDK: 6.0.0.v20160904203840 CLI no longer hangs and the correct error message is now output
[ERROR] : Error: A debug application is already installed, please remove existing debug application at ChildProcess.<anonymous> (C:\ProgramData\Titanium\mobilesdk\win32\6.0.0.v20160901034311\node_modules\windowslib\lib\wptool.js:836: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)