Titanium Community Questions & Answer Archive

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

NOTE: WHEN UPDATING MOBILE SDKS

Just something that I've been noticing a lot lately is people saying things like "New SDK is not launching simulator!" and stuff like that, well here is the fix:

  1. When you update your 1.4.1 files, make sure you CLOSE TITANIUM DEVELOPER COMPLETELY.
  2. Navigate into "$PROJECTDIRECTORY$/build/" and delete the entire "build/iphone" directory. Don't worry, Titanium will re-create it! (If you delete the directory and you can't find the "iphone" tab, simply create a new folder in the same spot named "iphone")
  3. Navigate into "$PROJECTDIRECTORY$/build/" and delete "build/android/bin" directory. Don't worry, Titanium will re-create it.

If those all don't work, go to the "Edit" tab, re-click the 1.4.1 SDK, then hit "Save Changes" and try running the Simulator again.

If you have a problem as stated here, simply download the latest 1.4.1 build from here and it should fix the problem.

PS - I know I'm not a creator/staff member of Appcelerator, I'm just trying to help cause I've encountered these problems before! :)

— asked September 16th 2010 by Colton Arabsky
  • androidsdk
  • iphone
  • iphonesdk
0 Comments

2 Answers

  • nice one mate. was actually just sorting the same issue as I read this…

    — answered September 16th 2010 by Critter
    permalink
    0 Comments
  • I also noticed if you get the error:

    Detected an attempt to call a symbol in system libraries that is not present on the iPhone:  bunch of errors
    

    You can download the latest git and it will correct the issue. At least it did for me.

    http://developer.appcelerator.com/doc/mobile/get_continuous_builds

    You can also search the Q&A to get the answer for issues that come up, most the time someone else has had the same issues.

    — answered September 16th 2010 by Jeffrey Messick
    permalink
    1 Comment
    • Yep. The latest build fixed that "symbol" or "image" problem.

      — commented September 16th 2010 by Colton Arabsky
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.