[TIMOB-18240] CLI: Android platform targets not detected when xcopy is not available on path
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Won't Fix |
Resolution Date | 2017-07-26T03:08:18.000+0000 |
Affected Version/s | Release 3.4.1 |
Fix Version/s | n/a |
Components | CLI |
Labels | qe-3.5.0 |
Reporter | Praveen Innamuri |
Assignee | Praveen Innamuri |
Created | 2014-12-17T01:18:25.000+0000 |
Updated | 2017-07-26T03:08:18.000+0000 |
Description
On a new Windows 7 machine, though Android SDK is installed and available, the titanium info command does not return any platform targets for Android SDK. No errors are displayed with the titanium info command.
However, only when I ran android list command, the output contains "xcopy not recognized as a valid command". After updating the env variable PATH with the location of xcopy, only then titanium info command is able to resolve the Android platform targets on the machine.
So, CLI is not able to parse the "android list" output if there are any warnings/errors, though they shouldn't impact the list of platforms/emulators.
This problem also happens on Windows 8.1 systems with existing Titanium installations. The xcopy.exe command is located in %SystemRoot%\system32 (typically C:\Windows\System32, though could be elsewhere). This folder reference would typically be added to the
Path
variable in the System Variables section of the Environment Variables dialog rather than thePATH
variable in the User Variables section. Those are concatenated to create the actual environment for cmd/PowerShell. Remove %SystemRoot%\system32; from the path and the error will occur withti info
. The error appears to happen when exec'ing thewmic
command in node-app/lib/environ, here: https://github.com/appcelerator/node-appc/blob/master/lib/environ.js#L243 Runningwmic os get Caption,Version
at the prompt even with system32 missing from the path is successful.Closing due to inactivity. If this issue still exists, please raise a new ticket.