Titanium Community Questions & Answer Archive

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

Bad CPU type

Hello All,
I just installed new titanium 1.1 and I get following error:

[INFO] Launching application in Simulator
/bin/sh: /Library/Application Support/Titanium/mobilesdk/osx/1.1.0/iphone/iphonesim: Bad CPU type in executable
[INFO] Launched application in Simulator (73.14 seconds)

Does anyone has any clue what kind of error is that and whether this version is not compatible with the CPU of the laptop I posses?

— asked March 23rd 2010 by Skinkers Developer
  • iphone
0 Comments

5 Answers

  • I receive this same error. Any info is appreciated.

    — answered March 23rd 2010 by Mike Dosey
    permalink
    0 Comments
  • I get the same error on one of my Macs, but it compiles fine on the other. Both intel macs.

    Off to reinstall the SDK in case there is a problem there.

    — answered March 23rd 2010 by Andrew Henshaw
    permalink
    0 Comments
  • Have the same issue. Using 3.1.2. Causes app to crash after load. Titanium stop logging but I can re-open the app and it works fine itself (without logging).

    [INFO] One moment, building ...
    [INFO] Detected pre-compiled app, will run in interpreted mode to speed launch
    [INFO] Launching application in Simulator
    /bin/sh: /Library/Application Support/Titanium/mobilesdk/osx/1.1.0/iphone/iphonesim: Bad CPU type in executable
    [INFO] Launched application in Simulator (1.18 seconds)
    [INFO] Application has exited from Simulator
    
    — answered March 23rd 2010 by Ryan Gartin
    permalink
    0 Comments
  • I am getting the same error as well.

    — answered March 24th 2010 by Fred Anderson
    permalink
    0 Comments
  • Just want to add that I have the same issue. I was very excited to see the start time speed up
    but it was useless since I can not use it. Any workaround?

    — answered March 25th 2010 by Cuong Tran
    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.