[TIMOB-13354] CLI commands does not work after setup
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Low |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2013-06-06T03:42:48.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | CLI |
Labels | n/a |
Reporter | Anatoliy Odukha |
Assignee | Chris Barber |
Created | 2013-03-13T17:24:17.000+0000 |
Updated | 2017-03-20T22:22:12.000+0000 |
Description
1. Download Titanium Studio and install it.(on clean machine, it should be first attempt to install Titanium)
2. Allow Studio install everything it asks (SDK, Alloy, etc.)
3. Open shell and try execute titanium -v. And you will see error.
TypeError: Cannot call method 'match' of undefined
Workaround:
execute in console
titanium setup
and configure your appcelerator account
should note that in Titanium Studio I was successfully logged in before. But CLI ignores this login
Full error log:
aod@ubntu:~/tizen-sdk/tools/ide/bin$ node -v
v0.8.18
aod@ubntu:~/tizen-sdk/tools/ide/bin$ titanium -v
3.0.24
aod@ubntu:~/tizen-sdk/tools/ide/bin$
/usr/lib/node_modules/titanium/node_modules/node-appc/lib/analytics.js:180
sessionCookie = status.cookie.match(/(PHPSESSID=[A-Za-z0-9]+)/),
^
TypeError: Cannot call method 'match' of undefined
at /usr/lib/node_modules/titanium/node_modules/node-appc/lib/analytics.js:180:35
at async.parallel (/usr/lib/node_modules/titanium/node_modules/async/lib/async.js:476:17)
at async.forEach (/usr/lib/node_modules/titanium/node_modules/async/lib/async.js:94:25)
at async.parallel (/usr/lib/node_modules/titanium/node_modules/async/lib/async.js:473:21)
at process.on.async.parallel.osinfo (/usr/lib/node_modules/titanium/node_modules/node-appc/lib/analytics.js:56:5)
at module.exports.getOSInfo (/usr/lib/node_modules/titanium/node_modules/node-appc/lib/environ.js:215:4)
at ChildProcess.exithandler (child_process.js:538:7)
at ChildProcess.EventEmitter.emit (events.js:99:17)
at maybeClose (child_process.js:638:16)
at Process._handle.onexit (child_process.js:680:5)
Dupe of TIMOB-12771. This shouldn't be a problem if you "titanium login".
Closing ticket as duplicate.