| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | Medium |
|---|
| Status | Closed |
|---|
| Resolution | Fixed |
|---|
| Resolution Date | 2013-05-05T19:46:15.000+0000 |
|---|
| Affected Version/s | Release 3.1.0 |
|---|
| Fix Version/s | 2013 Sprint 09 JS, 2013 Sprint 09, Release 3.1.1, Release 3.2.0 |
|---|
| Components | CLI |
|---|
| Labels | qe-3.1.0, qe-closed-3.1.1 |
|---|
| Reporter | Michael Pettiford |
|---|
| Assignee | Chris Barber |
|---|
| Created | 2013-04-13T22:38:48.000+0000 |
|---|
| Updated | 2013-06-05T17:42:23.000+0000 |
|---|
*Note* this did not prevent the app from being installed to the device, nor cause nay bad behavior when launching or running the app
Steps to reproduce:
1. Create a default titanium classic app
2. Run it on device
Actaul result:
The app is installed to device but the following error is printed to the console
execvp(): No such file or directory
[ERROR] Install app failed with exit code 127
*CLI output attached*
Expected result:
There isn't an error when installed to device
Further reproduction steps and logs at TC-2115.
This error is caused only when installing to device. It's happening because the detected Android SDK is "~/Desktop/android-sdk-macosx/platform-tools/adb" and the "~" is throwing off the spawn() command. We simply need to fully resolve the path in the Android library in node-appc. Line 34: sdkPath && (sdkPath = afs.resolvePath(sdkPath)); becomes Line 34: sdkPath && (sdkPath = result.sdkPath = afs.resolvePath(sdkPath));
same thing happens to me as well. However this still gets deployed to the target device.
Fixed in this commit: https://github.com/appcelerator/node-appc/commit/5aa9fda581420f464cd34b57969cc5c77a31df58
Unable to reproduce with: Mac OS 10.8.3 Safari: 6.0.4 Xcode 4.6.2 CLI: 3.1.1-alpha titanium-code-processor: 1.0.1-alpha Alloy: 1.1.3-alpha Appcelerator Studio, build: 3.1.1.201305292130 Titanium SDK version 3.1.1.v20130529114554 We have the QE team watching for this. If we see it again, we will reopen.