[TIMOB-24183] Windows Unable to build to Windows device with SDK 6.1.0
GitHub Issue | n/a |
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2017-01-30T12:55:45.000+0000 |
Affected Version/s | Release 6.0.0, Release 6.1.0 |
Fix Version/s | Release 6.0.2 |
Components | Windows, Windows phone |
Labels | n/a |
Reporter | Joachim Deneumostier |
Assignee | Kota Iguchi |
Created | 2016-11-04T14:15:42.000+0000 |
Updated | 2017-02-14T17:51:55.000+0000 |
Description
Issue Description
I am not able to build an app on a windows phone with the SDK 6.1.0. I get this error:
[ERROR] : Invalid "--device-id" value "0"
If I try using the CLI, it says no device is connected.
However, it works with SDK 5.5.1, so I think this is a regression bug.
Comments
JSON Source
FYI: I tried with 2 devices and I get the same error...
Same problem for me, my device is recognized by my pc but CLI says there is no device...
Hi, any news about this issue?Thanks
I alse tried with the SDK 6.0.0. GA and it doesn't work neither. Could you check please?
Hi, Sorry for the inconvenience. Are you trying to build on Windows Phone Emulator or devices ? Please try to build with CLI and let us know if you get error again. [Windows Phone Emulator](http://docs.appcelerator.com/platform/latest/#!/guide/Appcelerator_CLI_Tasks-section-43306725_AppceleratorCLITasks-WindowsPhoneEmulator) Regards, Aminul
Hi, I'm trying to build the app on a windows device. I've already tried to build using the cli and I get the same error. The emulator works fine. Thanks!
Tested, this is a regression , it works on 5.5.1 GA
This sounds familiar for me. Can you use
uuid
instead of number value0
for--device-id
? You can get your devicesuuid
by running following command, that should showDevices
section for your connected devices.If this still show no devices for you, I suspect this has to something to do with TIMOB-23976. Could you guys check if Windows 10 Emulators are installed on your environment?
Hi, I installed both windows 8.1 and 10 emulators with Visual Studio but I don't see the windows 10 emulators (only the 8) in the Appcelerator Studio. The result of this command shows that there are no windows 10 emulators and no no devices connected.
Hi, Any news about this issue? Thks
[~joachim] Let me clear about the environment to separate the issue...Does following command show Windows 10 emulators for you? Or only Appcelerator Studio does not list the emulators?
If Windows 10 emulators are not listed in the command above, I suspect if Visual Studio installation is broken. Would you try "Repair" in the Visual Studio installer if that's the case?
Hi, I don't see the windows 10 emulators in the studio but they have installed with Visual Studio. I've already tried the "repair" action in the Visual Studio, but no luck... I've tried on two computers, same issue. Thanks
[~joachim] Do you see any emulators and devices when you run following command in Windows PowerShell?
appc ti info -p windows -o json
Also, do you haveC:\Program Files (x86)\Windows Kits\10\bin\x86\WinAppDeployCmd.exe
installed on your PC? If so what's the outtput fromWinAppDeployCmd devices
command? FYI: https://msdn.microsoft.com/en-us/library/mt203806.aspxHi, It gives me the same result as Studio does...empty result for windows 10 emulators and devises...
In that case I strongly think that Visual Studio installation is broken. In case "Repair" doesn't work, I would try clean-uninstall Visual Studio. I haven't try this but Microsoft provides a document about Visual Studio "Total Uninstaller" here: https://msdn.microsoft.com/en-us/library/mt720585.aspx
It works with previous SDK versions as I said before... People at Appcelerator admitted this is a regression bug. We are waiting for a patch for this issue.
Would you paste your
appc ti info -p windows -o json
? Output fromWinAppDeployCmd devices
may help too.Info already sent to people at Appcelerator. They admitted this is a regression bug. We are waiting for a patch for this issue.
Why don't you attach output form
appc ti info -p windows -o json
as well as output fromWinAppDeployCmd devices
on this ticket so we can look into see what's exactly happening there?Hi, I don't think I have the rights to attach files, could you please check? thanks.
Hmm I don't have the rights to change the permission. Can you paste it into this comment area using formatting notation *\{code\} \{code\}*?
What will be happening when you specify
--wp-sdk 8.1
explicitly when you build the app?https://github.com/appcelerator/windowslib/pull/64 https://github.com/appcelerator/titanium_mobile_windows/pull/915 Note that
windowslib
in [titanium_mobile](https://github.com/appcelerator/titanium_mobile) needs to be updated in order to make this work.For
6_0_X
https://github.com/appcelerator/titanium_mobile/pull/8798 https://github.com/appcelerator/titanium_mobile_windows/pull/938Verified, was able to build to a Windows 8.1 device and 10.0.143943 device on SDK 6.0.2.v20170202114945. *Environment*
Validated with this environment: NPM Version: 2.15.9 Node Version: 4.5.0 Windows OS: 10.0.14393 Appc CLI: 6.1.0 Appc CLI NPM: 4.2.8 Titanium SDK version: 6.1.0.v20170123141052 Titanium SDK version: 6.0.2.v20170213083448 Appcelerator Studio, build: 4.8.1.201612050850 Windows Device: 10.0.14393 and 8.1 I created a default classic app in both Studio and with the CLI, and I was able to install and run the app on both Windows 10.0.14393 device and Windows 8.1 Device.