Titanium Community Questions & Answer Archive

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

Install Error When Building For iPhone

–This issue has been solved; see below for the solution–

I've installed all of the proper certificates, provisioning profiles, etc. as well as cleared my build/iphone folder and for some reason, my app keeps giving me an install error when trying to do on-device development in Titanium (the emulator works fine though). It detects all of the required certificates and profiles fine and it built everything fine one time, and then after I changed some files (non-critical files in the app) and now I can't build at all.

It happens within 5-10 seconds after I click allow for the codesign prompt. I'd really appreciate anybody's help with this issue. I know it sounds drastic but I've already wiped my hard drive twice to fix this and I've followed the instructions in the setup guide to the dot.

Thank you.

— asked August 23rd 2010 by Grant Derderian
  • error
  • install
  • iphone
  • mac
  • os
  • x
0 Comments

17 Answers

  • Bump. I am experiencing this exact problem as well and desperately need some help!! I've followed both Apple and Appcelerator's guides to running on the device and neither have worked.

    — answered August 25th 2010 by Colton Arabsky
    permalink
    1 Comment
    • Do you get the install error before or after the codesign prompt? I'm really struggling to find out what's causing this and come to a resolution (as you can tell by me wiping my HD three times)…

      — commented August 25th 2010 by Grant Derderian
  • Hey everyone,

    After hours of fail I have found a solution (in my instance anyways, i hope it saves someone else the same pain).

    I verified all required certificates were valid and present, then installed the 'Kitchen Sink' app onto my phone.

    To my surprise, this worked, installed just fine.

    Then performed a full iPhone sync with iTunes.

    Launch your app in the emulator, close, then run on device, your app should now load into iTunes and sync.

    No idea why it worked, but hope it's useful for someone.

    I gotta say i love the platform, but flaky is definitely the word!

    — answered October 5th 2010 by Aaron Bentley
    permalink
    0 Comments
  • what do the crash log & build log say?

    — answered August 23rd 2010 by danno watts
    permalink
    0 Comments
  • XCode's Base SDK is set to iPhone Simulator 4.0 and it builds fine- no errors. But Titanium doesn't build it and gives that install error right after the codesign prompt. Here's the complete XCode build log, with my app name and username taken out: https://gist.github.com/c5a6eb0720771f8000ff

    Thanks again for your help.

    — answered August 23rd 2010 by Grant Derderian
    permalink
    0 Comments
  • Bump- I'm hoping somebody can help…

    Thanks again.

    — answered August 24th 2010 by Grant Derderian
    permalink
    1 Comment
    • This actually happens for me too. I would appreciate some help aswell!

      — commented August 25th 2010 by Colton Arabsky
  • I found the solution! Try checking all of the PNG's in the app. For me, the default.png (my splash screen file) somehow got saved in a weird, almost-corrupted way after I edited it in Photoshop and the app then couldn't compile it properly because of that.

    I would suggest trying to open any photo files you have in your app from your computer, and if you see any direct error (Photoshop told me there was an unknown error and it couldn't open the image at all), delete the file and re-create it. That solved it for me!

    — answered August 27th 2010 by Grant Derderian
    permalink
    2 Comments
    • I haven't actually solved it yet, but I found a fix-around: I still build it via Titanium Developer, but when it gives me the "Install Error" I open my Xcode, go to the Organizer, go to my Device, go to the "Applications" part and click the little black "+".

      From there, I browse to the build/iphone/build/release-iphoneos/ folder of my Application and open the ".app" file, and it imports it directly to whichever device I have selected.

      Might be longer than just using Titanium, but it's better than having hours and hours of problems as I get "Install Errors" :P

      — commented August 27th 2010 by Colton Arabsky
    • I was having the vague "Install Error", usually when that happens I just build directly from Xcode. But this time it didn't work. I read your answer above and thought, "no way, it can't be that simple!". Then I actually read the error info in Xcode, and voila! Corrupt PNG file! Awesome! Thanks for posting this!

      — commented October 29th 2010 by karlo kilayko
  • I haven't actually solved it yet, but I found a fix-around: I still build it via Titanium Developer, but when it gives me the "Install Error" I open my Xcode, go to the Organizer, go to my Device, go to the "Applications" part and click the little black "+".

    From there, I browse to the build/iphone/build/release-iphoneos/ folder of my Application and open the ".app" file, and it imports it directly to whichever device I have selected.

    Might be longer than just using Titanium, but it's better than having hours and hours of problems as I get "Install Errors" :P

    — answered August 27th 2010 by Colton Arabsky
    permalink
    0 Comments
  • I too get this error.

    What i would like is a more meaningful error message. Install error is fairly useless and gives you no idea where to start debugging it.

    I have the correct appid and provisioning profile.
    I went to organiser in xcode and there was no provisioning profile for this app on my phone, so titanium had not put it there. Therefore this error was way before the device stuff somewhere in the signing chaos that is apps and itunes/provisioning profile.

    It would be great to get this fixed, but in the meantime could we have a clue about what is actually happening?

    — answered September 8th 2010 by Jez Manser
    permalink
    0 Comments
  • I have the same problem but my build directory is empty after I click install. The simulator works just fine…

    — answered September 20th 2010 by Magnus Ottosson
    permalink
    0 Comments
  • doubles :S

    — answered October 5th 2010 by Aaron Bentley
    permalink
    0 Comments
  • I fixed the install error issue by saving all my pngs as PNG-24. I hope this helps!

    — answered October 31st 2010 by Philip Joyner
    permalink
    0 Comments
  • I tried fixing all the PNGs and installing directly from the organizer but it still breaks. The organizer does show an error though:

    The application at /Users/username/Projects/TestApp/build/iphone/build/Release-iphoneos/TestApp.app does not specify a CFBundleExecutable

    Any ideas?

    — answered November 1st 2010 by Luis Gomez
    permalink
    0 Comments
  • its definitely the PNG files for me as well, especially the Default.png, I fixed it and it works fine :-)

    — answered December 8th 2010 by Tan Le
    permalink
    0 Comments
  • its definitely the PNG files for me as well, especially the Default.png, I fixed it and it works fine :-)

    — answered December 8th 2010 by Tan Le
    permalink
    0 Comments
  • Had the same problem. Found out that I had accidentally saved a a Word attachment into the 'images' directory of my project :S I removed it and everything started to work fine.

    — answered January 25th 2011 by Gerardo Lopez
    permalink
    0 Comments
  • what do u guys meant CORRUPT Png File?

    — answered August 7th 2012 by Adnan Ahmad
    permalink
    0 Comments
  • Hi Adnan, Corrupt png files are those which iPhone does not able to compress when try installing your app.
    This error can be found only using X-Code. so open your build project in X-Code if face problem like this.

    — answered August 7th 2012 by Ashish Nigam
    permalink
    2 Comments
    • Asish where can I see the message of corrupt file? I am using the same default.png file ships with Titanium

      — commented August 8th 2012 by Adnan Ahmad
    • Adnan those png files are not generally corrupt, but to check if any is there, build the project for iOS device and then open the project using X-Code and try building again.

      — commented August 8th 2012 by Ashish Nigam
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.