This question already has answers here:
Unable to boot iOS 8 Simulator
(2 answers)
Closed 8 years ago.
I am trying to run my application with X-code 6 GM seed (Latest X-code version not beta) & IOS 8 simulator is not working every time it say 'unable to boot ios simulator'.
I already tried below given link solution but all goes vain
not works for me
Not works for me
Any one know else face this problem or have any solution then please let me know.
Thanks in advance
"unable to boot ios simulator" is a generic error for when the simulated runtime's bootstrap server (launchd_sim) does not respond within a certain time period. It usually responds in less than 1/100th of this time. This can occur if something is preventing launchd_sim from running. Check for crash logs in ~/Library/Logs/DiagnosticReports or /Library/Logs/DiagnosticReports
This is most often caused by the setting of DYLD_INSERT_LIBRARIES. Do you have DYLD_INSERT_LIBRARIES set? To find out, open Terminal.app and run 'echo $DYLD_INSERT_LIBRARIES'
dyld_sim will attempt to log that it is ignoring the library because it is a host dylib and not a simulator dylib. It uses logging routines provided by the host's dyld to do this, but on Mavericks, dyld has a bug and will crash. This is fixed in Yosemite's dyld.
Try unsetting DYLD_INSERT_LIBRARIES or upgrading to Yosemite if that is the case. If that is not the case, I'm curious what your crash logs reveal.
Related
iOS 9.3 simulator get closed frequently with Appium 1.5.3, why?
Every time ios simulator get closed and run the application after 4 or 5 times.
Also, it took long time to reboot every time
Please help me on this.
I got the same situation, and I just plain and simple deleted 1.5.3 and went back to reliable 1.4.13
You can find the previous versions in:
https://bitbucket.org/appium/appium.app/downloads/
This question already has answers here:
Invalid Device State - Xcode/iOS Simulator error
(13 answers)
Closed 6 years ago.
Device not found message when run xcode app
Xcode version : 7.3
os version : EI Capitanenter image description here
//i.stack.imgur.com/VbYIr.png
Just plug out your phone and plug in again and wait until it process the symbol files and start displaying in the simulator list.
Also clean your code once.
this issue generally occurs just because you update xcode or made some changes in application folder.
To fix this Quit xcode and restart again or Restart your Mac
Another solution is
Clean your Project and try to re run the project
Please restart your xcode and open again that project and run it.
Its work for me.
May be Its helpful to you
Clean Your Code. Then Build And Run.
I just downloaded Xcode 6.4 from App Store and started to create a hello world app to learn swift but I get the error saying "Invalid Device State".
I googled a lot and tried the below things:
Restarted Mac and entered xcode and started project (as mentioned in a stack overflow thread)
I created a new iOS app with another layout but showed the same error again if I ran that project.
I deleted all projects and re-installed Xcode again. Started a new project and ran it but still getting the same error.
I am running Yosemite 10.10.1 and the Xcode version is 6.4.
Can anyone help me ?
Devices can get stuck in the creating state if errors occur in older versions of Xcode. This was fixed at some point in Xcode 7, but I'm not sure if the fix made it back into an Xcode 6.x release.
From Terminal.app, please run 'xcrun simctl list'. Locate the UDID of the device that you are attempting to boot. If it is stuck in the 'Creating' state, you can try recreating it by running 'xcrun simctl erase '.
If it is stuck in a different state, please update your question appropriately to indicate which state the device is stuck in.
On a side note, I suggest you update your OS. There have been a lot of quality fixes since 10.10.1. 10.10.5 just came out.
Try to switch from your original simulator to new one (for example from iphone 6 to 6plus) and then switch back to original one (iphone 6) and it should be ok
I have an application built against iOS 7, but targeted for iOS 5.1 since I only have an iPad 1 available for testing. It's an all native library, with very minimal iOS dependencies. I am able to run the app on my iPad just fine, but when I try to Profile it, XCode 5 immediately changes the status to 'Finished running on iPad', and the Instruments window shows a warning saying 'This device does not support this instrument'. I see this behavior regardless of which instrument I choose from the Instruments panel.
I have tried other suggestions from similar issues posted on Stackoverflow such as
1. Cleaning my app and rebuilding
2. Restarting XCode
3. Deleting my app from the device
4. Changing the deployment target from 'iPhone/iPad' to just 'iPhone'
None of these have helped me get over this problem. Is there something fundamentally not supported in the configuration that I am trying to run ? Since the app runs correctly on the iPad, this seems like just a problem with Instruments compatibility, so I welcome any comments / suggestions on resolving this.
Thanks.
This question already has answers here:
Xcode 4.3.2, issue with running on simulator
(6 answers)
Closed 9 years ago.
Once in every 10-20 runs I experience a hanging Xcode when trying to start a new App run in the simulator. The App won't start.
I can quit the simulator, but Xcode will simply ignore quits.
The only solution so far is to kill and restart Xcode. Fortunately that seems to work without side effects.
(xcode 4.3 on Lion, 8GB mac mini, 5.1 iOS)
Edit: I filed a bug report with Apple.
Edit June 2012: it's still a problem in Xcode 4.3.2 (4E2002)
Edit October 2012: with Xcode 4.5 this issue seems to have gone away. I do seem to notice that every run on the simulator now has a pause of a few seconds before starting the application. Perhaps the issue was fixed by introducing a longer wait somewhere. (There is no such thing as a free lunch.)
Found a workaround that saves you killing Xcode when this happens: if a hang occurs when you are running the iPhone simulator switch to iPad simulator, or vice versa. You will get the message that the simulator is already in use, but ignore that. Then switch back to the device simulator that caused your trouble in the first place, a new run will work!
Perhaps Xcode has trouble contacting the running process in the simulator, above workaround helps.
i have found that the hang is harder than all that. can't even get in to switch simulators. Quit Xcode won't work because it doesn't want to stop all tasks. tried killing a zombied clang task, but that didn't work. didn't see either gdb or lldb tasks, though i know clang is associated with lldb.
so ... no answer except force quit xcode or kill -9 xcode processes in terminal.
update … try this https://stackoverflow.com/a/10277189/774691 (which is also referred to by this https://stackoverflow.com/a/13400190/774691 ) ! it's impossible to believe it works, but i use this 2-3 times a day, and i laugh and i laugh and i laugh. it's insane, but it works. vote it up. the guy who came up with that answer needs some serious upvotes!
Use GDB instead of LLDB (default) for debugging. There are some bugs in LLDB right now affecting launch hangs, false memory address readouts, uncaught breakpoints resulting in EXC_BREAKPOINT kills).
Just press command+b and quickly press command+r and it will run.
I'm seeing this a lot. Every time I start XCode, I get one run and then after that if I try to run again (after Command-Q in the simulator) I have to Force Quit XCode if I want to run again. I can see running simulator processes with ps -ef, but even if I kill them (and they die), XCode still believes there's a simulator running.
I'm having some success with performing iOS Simulator > Reset Content and Settings... before I quit the simulator. I'm also having some success with Stopping the simulator (from XCode) as soon as I've finished testing it.
It seems that stopping the App currently running in the simulator before new compiling-run solve the problem : command+. and command+r
Moutain Lion (10.8) + Xcode Version 4.4.1 (4F1003)
I reported it to apple
BUG REPORT
12872744
https://devforums.apple.com/thread/175685
You can also restart the Simulator and restart the app manually and this wakes XCode up and it leaves the stuck DEBUG mode and goes back to STOP mode.
You have to start the run in Xcode again but at least its stopped hanging.