CODEWITHSUNDEEP
iosios-simulatorxcode5
user3022503
user3022503

Reputation: 1

iOS simulator failed to install the application, common fixes not working

Today, while trying to fix an issue with outlets within my app, I tried to launch it and received the "iOS simulator failed to install the application" error. There are no issues within the app. The only thing I changed between the time that it worked and that it didn't was to type in the custom class setting. I deleted what I had typed after I noticed it not working. I have tried the reset contents and settings option multiple times, and I have cleared all the "issues" with the app, and it still will not launch. Anyone have any other ideas? (xCode 5 for iOS, BTW)

Upvotes: 0

Views: 217

Answers (1)

David Hoerl
David Hoerl

Reputation: 41642

So try all of the following one by one, until it works

  • delete the app from the Simulator (press and hold just like on a real device)
  • shut down Xcode, the Simulator, reopen and try again
  • clean the app, recompile, try to run again
  • from the organizer, remove the Derived Data folder, rebuild and run
  • try using a different simulator - that is Retina 3.4, Retina 4, etc
  • reset the Simulator

Sigh - if you get here Xcode is hosed, or your project got hosed. Add a comment if all else fails, I'll give you some more thoughts.

EDIT: so still no luck. At this point you almost have to brute force it. Lets assume now that something small but really serious has happened. You need to make 100% sure that the Storyboard file is both named correctly in the file view, in the plist, and the storyboard is in the "copy files to bundle".

Do you have even a zipped old copy? If so you can use it to compare to the latest broken project, or if not then choose any similar project (some iPhone app).

Look at the Scheme to make sure all is correct there - and compare to a working project.

Now go looking at and comparing the PLIST, the project settings, then the Target settings. Look at the Target build settings, and the list of files in the Copy Bundle Resources (where you better see the image assets, the storyboards, etc). Look at everything.

Build the app in say Release mode (you did try both Release and Debug already, right?), go to your derived folder. Compare the broken app to a good one. Are the folder structures the same, are the files you expect to find there, including the binary object, there. Images too. You can go to the folder using Terminal and find out the types of objects in the binary - I think "file fileExecutable" does it but there is some other command too.

Upvotes: 1

Related Questions