ChatGPT解决这个技术问题 Extra ChatGPT

Unable to run app in Simulator: Xcode beta 6 iOS 8

I am unable to launch my app on simulator using Xcode 6 beta and iPhone 5s simulator. First I am getting an error message from Simulator

"Unable to boot the iOS simulator"

and then after Xcode is showing me following error,

Unable to run app in Simulator An error was encountered while running (Domain = DTiPhoneSimulatorErrorDomain, Code = 2)

https://i.stack.imgur.com/CNw2d.png

Have you tried restarting Xcode and/or your Mac?
Isn't this under NDA?
Beta 6? Damn! A traveller from the future!
Even if it was, it isn't the concern of the members of this community to enforce the NDA.

S
Sam B

I solved it following these steps:

Open Xcode 6 beta Go to the menu Xcode > Open Developer Tool > iOS Simulator Even if an error dialog shows up, you still would have access to the iOS Simulator's menu Select Hardware > Device > Manage Devices Click on the little + sign at the bottom Add (if missing) all the devices that you want, or delete and recreate the ones malfunctioning. If anyone of the simulator is not working then right click on it and delete it and then re-create it again

https://i.stack.imgur.com/nGgm6.png


If I create (or use) a iOS 7 simulator. It works good. It fails only with iOS 8 simulator. Some link could be broken
This worked for me. I only tried it after changing the command line tools setting as per ayalcinkaya's answer, so that may be necessary as well.
@Dayan Gonzalez I have same issue in my mac mini how can i fix?
Thank you this is exactly what I was looking for.
I solved the connection problem with these steps. Neither restart iOS simulator nor restart system can solve.
C
Cœur

Make sure you choose Xcode 6 as Command Line Tools in Preferences > Locations Section

https://i.stack.imgur.com/Zow3E.png

Make sure you open Xcode 6 from Applications not from the setup file.

Finally restarting Mac solve the problem in my case.


This didn't work for me either. I had 5.1, I changed it and restart the xcode and mac. And the error is still there
Did not fix my issue.
+1. Selecting the Location for cmd line tools and then rebooting fixed it for me!
Reboot (not even logout/login) does indeed appear to be necessary. WTF Apple?
Nothing this sort of solution is helping. What do I do.?
u
ugo

After I found some solutions on the web, a combination of procedures worked for me:

Close Xcode and iOS Simulator (and all related applications) Install (or reinstall) Xcode6-Beta to Applications folder (direct from the .dmg file) Open Xcode6-Beta and go to Xcode -> Preferences -> Locations -> Command Line Tools and select "Xcode 6.0" (be sure that you've selected the one in Applications folder) Launch the iOS Simulator and go to iOS Simulator -> Reset Content and Settings... Close all the applications and restart your mac (I unchecked "Reopen windows...") Open Xcode6-beta and test the iOS Simulator

Good luck


C
Cœur

I'm using Xcode 6 beta 2 and has problem (error code = 4 in my case) running iPad simulators. I think I had the issue because I'm running dual Mac OS boot and the Xcode is launched from another startup disk

I did both steps recommended by @ayalcinkaya and @apascual, and this worked for me.

Change the "Command Line Tool" to Xcode BETA2 (from 5.1.1 in my case) in "Xcode->Preference->Locations"

Open Xcode 6 beta 2

Go to the menu Xcode > Open Developer Tool > iOS Simulator

Even if an error dialog shows up, you still would have access to the iOS Simulator's menu Select Hardware > Devices, and switch between iPad devices and this apparently made the simulators reconfigured

While the simulator is running, run the app with the selected simulator.

After going through this manual process once, everything is fine.


The "error code = 4" (in some FBS domain) issue is not related to this issue. That issue pertains to a race condition in app install and launch. The workaround for that is unfortunately just to retry the build&run.
f
footyapps27

This happens most of the times because another instance of the simulator is running in the dock.

Kill the other instance & things should work fine.


C
Cœur

I also had this problem and found the solution by doing following steps:

Initially I downloaded Xcode 6 library in Documentation section under the path Xcode --> Preferences --> Downloads and restart my xcode but didn't solve my problem.

After that ->

Downloaded and installed the iOS 7.1 Simulator under the path Xcode --> Preferences --> Downloads.

Restart xcode again and the problem solved.

I am facing same issue again next morning.

Unsetting the DYLD_INSERT_LIBRARIES variable solves my problem:

a) Open terminal and type "sudo vi /etc/launchd.conf" command and press Enter b) Press I "Insert" mode and change this

    "setenv DYLD_INSERT_LIBRARIES /usr/lib/libimckit.dylib" 

to this

    "unsetenv DYLD_INSERT_LIBRARIES /usr/lib/libimckit.dylib" 

and press esc to exit from insert mode.

c) Save changes by typing ":wq" Press Enter d) Reboot your system and problem solved.

https://i.stack.imgur.com/J59s7.png

Prior to that I didn't found any iOS version in front of each listed devices but after installation or by unsetting DYLD_INSERT_LIBRARIES variable I found the same in front of each devices.


G
Golden Thumb

I got this problem after renaming the default folder name "Xcode-Beta2" to "Xcode". When I renamed it back to "Xcode-Beta2", the simulator worked as before.


l
lubert

What worked for me was removing all of the devices in "Manage Devices" and adding them back after rebooting


OMG thank you for this post... this has been the second time the simulator has been shut down for me this beta period. FIXED
In my case, rebooting did the trick. No need to remove and readd devices.
The only relevant bit there was the reboot. You didn't need to delete and re-add devices. I suspect that you renamed Xcode.app after first launch which causes you to no longer be able to use the iOS Simulator in that Xcode.app.
K
Kof

Clean -> Run fixed it for me.

I've tried the rest, nothing helped. Although it may be required too.


H
HBublitz

I've had the same problem, when running an app with the same name as a previously run different app.

Run "foo" -> make a new project named "foo" -> run -> error.

Whatsoever - it seems to me that there are several reasons for iOS-Simulator to say "ehm, what do you want from me? OK, I'll throw an error..." ;-)

MY SOLUTION: Close iOS simulator, run app again.

That's it in most of cases like this.


J
Jeremy Huddleston Sequoia

The most common cause for the error reporting is that DYLD_INSERT_LIBRARIES is set. Most people reporting this issue have had it set in /etc/launchd.conf. You can edit that file to remove it (or just delete the file as that's likely the only line) and reboot to address the issue.

Another possible cause for this problem is that you may have renamed Xcode.app after running it the first time. If that's the case, just reboot (or rename it back to what it was before).


C
Community

Yes apascual is correct https://stackoverflow.com/a/24080160/2905967

But for me, before step 5, I have deleted the simulator device (select and by pressing Delete key from keyboard) Which device is giving the Problem. Reference: apascual answer


z
zvjerka24

I had the same problem and only solution that helped me to fix this was to reinstall Xcode.


R
Renetik

Delete simulator/s and create again in Xcode/Window/Devices worked for me...


C
Cœur

I found that I have to update to newest OS X 10.10.1 (From OS X 10.9.5) to get iOS 8.1 to work.


N
Noor

Perfect answer for this fix is here

In this case, launchd is crashing when trying to launch. This could be as a result of deleting the /private/tmp folder. To resolve this, I typed the following commands on my terminal: sudo mkdir /private/tmp sudo chmod 1777 /private/tmp


l
lewis

In Xcode 11, I found running the following in Terminal worked:

sudo xcode-select --reset

Src: https://ekartco.com/2019/10/xcode-11-unable-to-boot-simulator-diehard/


V
Vittal Pai

None of the above suggestions worked for me.

Changed the Embed setting for the complained framework to Do Not Embed resolved the issue.

https://i.stack.imgur.com/C80b9.png


S
Sabito 錆兎 stands with Ukraine

What worked for me is just open the simulator and leave it open for a while it will probably boot up. I think in my case it was just trying to load the things or something like that or just my mac is slow.

Try leaving the simulator open for some time if it still does not boot then you may try any of the solutions here.


S
Sabito 錆兎 stands with Ukraine

These steps may help you with your problem. Try this:

Click iOS Simulator at the top of your screen Click Reset Contents and Settings Click Reset when the Alert comes up Run the App again on the Simulator

This will simply reset all the contents and settings on the iOS Simulator previously.


C
CSPearson

I had this problem until I put the Xcode 6-beta application file from inside a folder I had in my application directory to the Application directory itself. Restarted computer. Then it worked.

To test, I created a folder in my Application directory again and put my Xcode application in there and, again, it did not work. Put it back into Application directory itself; it worked. I didn't even have to restart in these cases.

I would really hope Apple is beyond hardcoding paths.


The paths aren't hard-coded. The issue is that you loose access to the simulator if you rename Xcode.app after the first time you launch it. This is a known issue and is indeed in the release notes for Xcode 6.
g
guri23

i was facing the same problem, what i done is I downloaded simulator for IOS7 what you need to do is go to:- 1.Xcode->preferences->Downloads->Components 2.after that in your project under general settings-select Deployment target as 7.0 3.the last thing is select any simulator under 7.0 :)


F
FishStix

I received this error trying to run one of my iPad only apps on the iPhone Simulator. It's built as a universal app, I've run it multiple times on the iPhone for testing, and I only recently checked the "iPad" only checkbox in the Target config.

When trying to run it on my iPhone Device, I got the much more helpful error message: "The application at [/location/..../Name.app] can only be installed on iPads."