[TIMOB-11433] Unable to create Titanium Project

GitHub Issue	n/a
Type	Bug
Priority	Critical
Status	Closed
Resolution	Fixed
Resolution Date	2012-10-16T21:43:23.000+0000
Affected Version/s	Release 3.0.0
Fix Version/s	Release 3.0.0, Release 3.1.0, 2012 Sprint 21 JS, 2012 Sprint 21
Components	Core
Labels	js, qe-ios100112, regression
Reporter	Deepti Pandey
Assignee	Chris Barber
Created	2012-10-12T08:30:11.000+0000
Updated	2013-01-11T03:17:06.000+0000

Description

This is a regression bug. Steps to reproduce : 1.Lanunch Titanium Studio. 2.Create > New > Titanium Project. 3.Enter project name > enter App id > Press "Finish". Actual Result: "Unable to create Project " error is thrown . Screenshot attached .

Attachments

File	Date	Size
logs.rtf	2012-10-12T08:30:11.000+0000	1652
Screen Shot 2012-10-12 at 1.09.54 PM.png	2012-10-12T08:30:11.000+0000	339232

Comments

Dustin Hyde 2012-10-12

Does this happen from the command line?
Michael Xia 2012-10-12

The error indicates the CLI could not find ~/.titanium/config.json file, and I got it to reproduce by manually deleting the file. The problem persists even after I reinstall the CLI. It seems CLI should create one when needed if the file doesn't exist.
Chris Barber 2012-10-13

You're probably using an old version of the CLI. This was an issue several days, maybe a week ago. I'll re-verify.
Chris Barber 2012-10-13

This has already been fixed (I think when I fixed the setup command) by this commit: https://github.com/appcelerator/titanium/commit/6e541e391a689cdff40faa6e234fdd46f2311eae.
Ingo Muschenetz 2012-10-16

I just want to make sure that we don't required the user to run the setup command, as they won't be doing so from inside Studio.
Chris Barber 2012-10-16

@Ingo, I confirmed, you do NOT need to run setup to create a new project.

Dustin Hyde 2012-10-16

Bug persists, blocking critical workflow. Titanium Studio: 3.0.0.201210151149 Titanium SDK: 3.0.0.v20121015174610 Titanium CLI: 3.0.5 OS: Lion 10.7.5 error when running titanium from command line:

   sfeloneyMBA:~ sfeloney$ titanium
   
   /usr/local/lib/node_modules/titanium/node_modules/longjohn/index.js:111
         throw e;
               ^
   Error: ENOENT, no such file or directory '/Users/sfeloney/.titanium/config.json'
       at Object.fs.openSync [as openSync] (fs.js:338:18)
       at Object.fs.writeFileSync [as writeFileSync] (fs.js:756:15)
       at path.existsSync (/usr/local/lib/node_modules/titanium/lib/titanium.js:47:7)
       at config.user.config.user (/usr/local/lib/node_modules/titanium/lib/titanium.js:38:5)
       at ChildProcess.exithandler (child_process.js:534:7)
       at ChildProcess.EventEmitter.emit [as emit] (events.js:91:17)
       at maybeClose (child_process.js:634:16)
       at Socket.ChildProcess.spawn.stdin (child_process.js:805:11)
   ---------------------------------------------
       at Object.exports.execFile [as execFile] (child_process.js:590:9)
       at exports.exec (child_process.js:477:18)
       at detectLocale (/usr/local/lib/node_modules/titanium/lib/titanium.js:37:4)
       at setLocale (/usr/local/lib/node_modules/titanium/lib/titanium.js:44:3)
       at /usr/local/lib/node_modules/titanium/lib/titanium.js:67:3
       at Object.<anonymous> (/usr/local/lib/node_modules/titanium/lib/titanium.js:69:3)
       at Module.Module._compile [as _compile] (module.js:449:26)
       at Object.Module._extensions..js [as .js] (module.js:467:10)

Dustin Hyde 2012-10-16

The work-around is to manually add a .titanium folder in the user directory.
Anshu Mittal 2013-01-11

Tested with: SDK: 3.1.0.v20130110133402, 3.0.1.v20130109180643 Studio:3.0.1.201212181159 Able to create the titanium project successfully.

JSON Source