Titanium Community Questions & Answer Archive

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

Testing the Prerelease of 1.5 - Getting this error

Just a heads up. It didnt get this error at first but the second or third time I complied I am getting this error when compiling for Android:

File "/Library/Application Support/Titanium/mobilesdk/osx/1.5.0/iphone/builder.py", line 869, in main
execute_xcode("iphonesimulator%s" % iphone_version,["GCC_PREPROCESSOR_DEFINITIONS=__LOG__ID__=%s DEPLOYTYPE=development TI_DEVELOPMENT=1 DEBUG=1 TI_VERSION=%s" % (log_id,sdk_version)],False)
File "/Library/Application Support/Titanium/mobilesdk/osx/1.5.0/iphone/builder.py", line 792, in execute_xcode
output = run.run(args,False,False,o)
File "/Library/Application Support/Titanium/mobilesdk/osx/1.5.0/iphone/run.py", line 31, in run
sys.exit(rc)
SystemExit: 1
— asked November 6th 2010 by Dave F
2 Comments

  • Same problem here. I had a 1.4.1.1 project. I downloaded a continuous build 1.4.2. Rebuilt, no problems.

    Then I downloaded 1.5.0, rebuilt and get the above problem. I'll have to try a new project and see what happens.

    — commented November 8th 2010 by Steven Day

  • This problem also seems to be addressed at: http://developer.appcelerator.com/question/67871/question-about-the-continuous-builds

    — commented November 8th 2010 by Steven Day

5 Answers

  • This happens when you do a grounds up rebuild…make a new project, launch it with 1.5.0 and sample sources for both platforms, and then copy your Resouces folder in the new project. You will bypass the problem. But it is a problem for the 1.5.0 build, as not being able to create a new project, so that you need to create it as 1.2.0 and then save it as 1.4.1/1.5.0.

    — answered November 6th 2010 by Vali Filip
    permalink
    1 Comment

    • I experienced the same error. So I removed all files from my build/iphone directory and was able to build the project

      — commented November 11th 2010 by Marek Zwick

  • interesting. Thanks for the heads up. I was actually working with an existing app that was previous built with 1.4.2 but I'll try creating a new project later tonight and see how it goes?

    Would you say its fairly stable? Just curious if it improves on android b/c the version i'm working with has some "issues".

    thanks!

    Fish

    — answered November 6th 2010 by Dave F
    permalink
    1 Comment

    • I could not say that, being that curently I'm developing just for the iPhone, and I'm new to the pact also :)
      That is the thing, you were working on the 1.4.2, and saved the project as 1.5.0, so then a clean rebuild had to be done, and the problem occurs ;) use the standard sources to clean build the project and then replace with your own.

      — commented November 7th 2010 by Vali Filip

  • So where do I post Q&A about this Q&A system? :-) Kept saying error on post of answer. Apparently they all posted. lol

    — answered November 9th 2010 by Steven Day
    permalink
    0 Comments

  • As I mentioned in the comments in the question, I also experienced this… to fix the problem I created a new project, copied over the Resource directory and it worked fine under 1.5. Not an acceptable solution to me, but it worked nonetheless.

    — answered November 9th 2010 by Steven Day
    permalink
    0 Comments

  • The easiest solution to this is to delete the contents of your build/iphone folder…

    — answered December 3rd 2010 by Matthew Lanham
    permalink
    0 Comments
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.