iOS Simulator Doesn't Install Application - objective-c

Using Xcode 5.1 to debug an iOS 7.1 iPad application.
When I build and run my project in the iOS Simulator, the simulator opens and my app icon pops up for a second. Then it looks like the app stops installing and the simulator goes to the home screen. Xcode still thinks it's debugging and it doesn't show any errors in Xcode or the simulator. I can go to my app in the simulator and click it again, but it just crashes. I get the same behavior in iPad, iPad Retina, and iPad Retina (64 bit). Any subsequent tries to run the app in the simulator doesn't even attempt to pop the app icon up until I quit the iOS Simulator and try again. All the usual fixes haven't worked for me yet.
Fixes I've Tried:
1. iOS Simulator > Reset Content and Settings...
2. Window(in Xcode) > Organizer > Delete Derived Data & Delete Snapshots
3. Delete Contents in ~/Library/Application Support/iPhone Simulator
4. Uninstall Xcode and reinstall
5. Clean project and rebuild
6. Restart machine
I'm out of ideas. Is there something I've missed?
Thanks all!

Create another app with the exact same template and look at the app delegates and make sure they are the same.
Example: AppDelegate.h and AppDelegate.m
You might've accidentally deleted an area that helps load the App.

Alright I found the problem. I was playing with how we load our frameworks because we were having other issues before and I left a bad value in our Linking settings.
Here's how I fixed it:
Project > Build Settings > Linking > Mach-O Type set to "Executable"
It was set to "Bundles" before which causes Xcode to package the app in a way that caused ours to break.
Helpful Post: In Xcode project target build settings, What is Mach-O Type?

Related

App crashing on launch with instrumentation w/ calabash-ios

UPDATE: This was fixed by resetting the phone's settings. General -> Reset -> "Reset all settings".
We are having on issue on iPhones 6 and 6+ when launching our IBM MobileFirst-based app.
When calabash instrumentation is linked and I manually launch the app, the splash screen will come up and the app will quit almost instantly.
Double tapping home shows me the app running in the background, but Xcode does not recognize it as a running process. After force-closing the app and re-launching, it will usually do the same thing, but sometimes it comes up.
I've noticed our automation is sometimes stuck in an infinite loop of launching and crashing. This only happens on the instrumented app.
The crash log throws EXC_BAD_ACCESS. I found a thread on the google group from a few years back that talks about linker flags, but I don't have any of the weaker flags mentioned there.
Steps to reproduce:
*App must be instrumented with the calabash automation framework (calabash-ios setup must have been executed in same directory as xcodeproj file.)
Build application and deploy native iOS project to XCode via eclipse.
Build the -cal target with the "Run" configuration.
Kill the debugger/application.
Manually launch the app on the device. The app will successfully launch maybe 15%-20% of the time, otherwise it will just quit.
Using calabash-cucumber version 0.14.3.
Linker flags:
$(inherited)
-force_load
"$(SRCROOT)/calabash.framework/calabash"
-lstdc++
It appears $(inherited) contains -ObjC for Debug.
Xcode installed at: /Applications/Xcode.app/Contents/Developer
Xcode version: 6.1.1
Xcode build: 6A2008a
The user is unresponsive, the fix was:
Actually I just found the fix to this. What I had to do is reset the
phone's settings in Settings -> General -> Reset -> "Reset All
Settings" (the first option). Have not seen the behavior since.
I had exact same problem, tried so many different ways and finally found how to fix it - I changed project directory, pulled from Git, then bundle install, pod install and build the app with calabash target as usual
Xcode 7.3.1, calabash-cucumber (0.19.1)

How to test my app on ios 7 using Xcode 6 simulator

I'm trying to test my app with ios7 using Xcode 6's simulator but I can't find the option to change it. Currently it only loads ios8 while my deployment target is set to 7.
Also according to this message from Apple:
Starting February 1, 2015, new iOS apps uploaded to the App Store must include 64-bit support and be built with the iOS 8 SDK, included in Xcode 6 or later. To enable 64-bit in your project, we recommend using the default Xcode build setting of “Standard architectures” to build a single binary with both 32-bit and 64-bit code.
Does this mean that new apps cannot run on ios7 anymore?
Thank you for your help.
First, Change Deployment Target to 7.You can change Deployment target from target under Deployment Info.
Go to Xcode Preferences, Select Downloads tab and download iOS7 Simulator.
Now go to Xcode, you can find iOS7 Simulator on target device list, if not than quit and restart Xcode.
Hope it will help.
The deployment target is the minimum version of iOS that your application will be expected to run on. It effects how your app is BUILT and not where you run it. You need to choose an iOS 7 device from the run destinations menu and then do a Build&Run to build, install, and run the app on the iOS 7 device.
If you don't have an iOS 7 simulator device in the run destinations menu, go download the iOS 7 runtime from Xcode -> Preferences -> Downloads
Yes you can, go to xcode(7) preferences>select Components here you can download Simulater and Documents also.

Running the app on the simulator shows: "Unable to boot the iOS simulator"

Running the app on the simulator shows: "Unable to boot the iOS simulator". I'm on Xcode 6.0.1.
I tried everything: resetting the simulator; selecting the Xcode 6.0.1 command line tools; restarting the Mac. The problem is still present.
Try this. In Xcode menu: Open Developer Tool > iOS Simulator. When it opens, use the menu to go to Hardware > Device > Manage Devices.... In that list, delete the non-working simulators and re-add them.
Also make sure that the Downloads section of Xcode preferences is up to date.
Do you have DYLD_INSERT_LIBRARIES set? If so, this is a dupe of:
Unable to boot iOS 8 Simulator
Check /etc/launchd.conf

Xcode 5 fails to launch app with error: failed to launch '/path/to/.app' -- Busy

I am using XCode 5, with an iPhone 5s as the dev device. Every other time I run the app I get a pop that says "Could not launch [app name] \n busy". My iPhone 5s then appears to crash and the only way it will respond is if I hold the home and lock button until it resets.
The application is a single view application, the only thing I have done is added the Parse.framework from here and used
[Parse setApplicationID:appID clientKey:clientKey];
[PFAnalytics trackAppOpenedWithLaunchOptions:launchOptions];
In applicationDidFinishLaunchingWithOptions, along with some UI that isn't hooked up to anything.
I'm not sure if this has to do with Parse or possibly the App settings.
So to be clear, the behavior is:
Fresh reset > Build and Run application on iPhone 5s > application runs fine > Build and Run application on iPhone 5s > application appears to launch but screen remains black and iPhone is no longer responsive except the screen will turn off when the lock button is pressed (but not back on) > Build and Run application on iPhone 5s > XCode says "could not launch app - busy" > hard reset iPhone
When I run this on the 64-bit simulator it works fine.
Edit 1:
I have tested with multiple applications now that we know work on multiple other devices (iPhone 5, iPhone 4, iPhone 4s) and the simulators. I don't have another iPhone 5s so it is hard to compare exactly but everything crashes my 5s..
My device was completely stuck with black screen. "To fix you have to hard reboot, holding the power and home button until the phone reboots - doesn't lose any of the data you have on your phone (a concern the first time I did it)." as stated here:
http://blog.paulhadfield.net/2014/01/iphone-hangs-when-running-from-xcode.html
For iPhone7 there is a different approach:
Press and hold down the power button located on the right side of
the iPhone 7.
While holding down the power button, press and hold
down the Volume Down button on the left side of the iPhone 7.
http://www.hongkiat.com/blog/force-reset-iphone7-7plus/
You were using your phone when you ran the app. Make sure you don't use your phone after you press build and run, otherwise it will be "busy"
Which Xcode version do you use? Same issue with Xcode 5.0.1 + iPhone 5S (iOS 7.0.4). It crashed my iPhone 5S even by the simple application created by Xcode's default project template.
It seems this issue has been fixed in Xcode 5.0.2. Xcode 5.0.2 works fine for me by now.
I've got the same problem for several times. It seems that this problem always happens when iCloud or other background App is running & the App I was debug is already in running mode.
My suggestion is: Avoid any background App running when debug and Make sure the App debugging is fully killed before restart a debug.
It is obvious a bug in iOS 7 + Xcode 5.
I had the same issue and upgrading to Xcode 5.0.2 resolved it.

Get "No such file or directory" when testing on iPad device but not in simulator

I have an app that i am release as iPhone and iPad even if it developed as Universal. The reason is that i have release an English version that is Universal and just want to update the iPhone and iPad Swedish versions as it have been with separate apps for the different devices.
When i run on the iPhone device i have no problems but when testing with iPad i get the message below, which i do not know how to remove:
"Could not launch “FamilyQuiz_3"
No such file or directory (/Users/peterk/Library/Developer/Xcode/DerivedData/MyApp_3-fosmfwberzyfryenqrjlfpacftjv/Build/Products/Debug-iphoneos/MyApp_3.app/MyApp_3)
I can start the app from the iPad device but it do not start automatically when submit from XCODE.
1)make sure your iOS Deployment Target version is the same or lower than the one on your device in build settings.
2)delete it from the device
3)close xcode
4)Goto /Users/peterk/Library/Developer/Xcode/DerivedData/ on your computer and delete the
MyApp_3-fosmfwberzyfryenqrjlfpacftjv folder
if that still doesnt work go and try deleting the app restarting your phone, and then restarting your computer even, and doing it again.