Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

Impossible to build an app with Titanium SDK

I try to build the default app to the iPhone simulator with Titanium SDK

But I've got this error in log file when starting (and it works with Titanium SDK 1.3.2)

Where it comes from?

Building from: /Library/Application Support/Titanium/mobilesdk/osx/
Platform: Darwin Kernel Version 10.4.0: Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386

Exception detected in script:
Traceback (most recent call last):
  File "/Library/Application Support/Titanium/mobilesdk/osx/", line 401, in main
  File "/Library/Application Support/Titanium/mobilesdk/osx/", line 7, in run
    proc = subprocess.Popen(args, stderr=subprocess.STDOUT, stdout=subprocess.PIPE)
  File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/subprocess.py", line 595, in __init__
  File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/subprocess.py", line 1106, in _execute_child
OSError: [Errno 2] No such file or directory

Thanks a lot for your help !

— asked October 19th 2010 by Renaud E
  • build
  • sdk
  • titanium

1 Answer

  • Accepted Answer

    From past experience, I've found that often build issues are resolved by removing the build directory inside your project, then rebuilding the project. (Simply by running it in the simulator or on a device.)

    My hunch is that if you build it with one version of Titanium and then build it with another version of Titanium, that the project doesn't build correctly, probably due to differences in the "cached" parts of the build that were originally built by another version of Titanium.

    Try that, and see if it solves your issues….

    Peter Janett


    — answered October 20th 2010 by Peter janett
    1 Comment
    • Thanks a lot Peter for your advices ! :-)
      It works now !

      — commented October 20th 2010 by Renaud E
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.