For context I am working with a fresh install of macOS Mojave and a fresh install of Xcode 10.1.
The first thing I noticed was I only had the option of
Generic iOS Device from the simulator drop down list. It seems Xcode did not download any iOS simulators with it like I thought it was supposed to.
So I went looking in the simulator list, and it was empty. So the next logical step is to try and create a simulator. Where I only found the ability to download simulators. So I downloaded four simulators and went back to try and create them. Nothing changed, I could still only download simulators. I wasn't about to select a device or a simulator.
I have tried restarting Xcode, the OS, and reinstalling Xcode none of which have worked. I have tried deleting DerivedData, but that didn't work either. So, I am now at a point where my Google searches are just turning up the same tired answers, and I am getting no where.
Edit
Here is the error message I get if I try to build anything, if it helps.
2018-12-07 05:49:31.315 ibtoold[1550:71807] Error
Domain=NSPOSIXErrorDomain Code=61 "Connection refused" UserInfo=
{NSLocalizedDescription=CoreSimulator.framework was changed while the
process was running. This is not a supported configuration and can occur
if Xcode.app was updated while the process was running. Service name
((null)) does not match expected service name
(com.apple.CoreSimulator.CoreSimulatorService).} 2018-12-07 05:49:31.315
ibtoold[1550:71807] Failed to load CoreSimulatorService. Access to
simulator services will not be available. Error=Error
Domain=NSPOSIXErrorDomain Code=61 "Connection refused" UserInfo=
{NSLocalizedDescription=CoreSimulator.framework was changed while the
process was running. This is not a supported configuration and can occur
if Xcode.app was updated while the process was running. Service name
((null)) does not match expected service name
(com.apple.CoreSimulator.CoreSimulatorService).} 2018-12-07 05:49:31.400
ibtoold[1550:71824] CoreSimulatorService connection became invalid.
Simulator services will no longer be available.
I was facing the same issue. I tried each and everything that Google has said. But didn't find any solution. So, finally, I removed all the Xcode from the system and update the mac os with Mojave 10.14(earlier it was 10.13). Then I reinstall the Xcode 10.1. This time Xcode asked the permission to install extra components. After installation of these components, I am able to see the list of all the simulators.
The problem, what I have observed, was that there was no device present in the core simulator folder under the library/developer. Please check if this folder present or not on the following path: Users/Library/Developer/CoreSimulator/Devices.
Related
While debugging any iOS application, Xcode builds and run successfully, also launches a simulator but it is not able to attach debugger from Xcode 14 to Simulator iOS app.
It throws an error in Xcode:
Xcode console says:
Could not attach to pid : “75997” Domain: IDEDebugSessionErrorDomain
Code: 3 Failure Reason: attach failed (Not allowed to attach to
process. Look in the console messages (Console.app), near the
debugserver entries, when the attach failed. The subsystem that
denied the attach permission will likely have logged an informative
message about why it was denied.) User Info: {
DVTRadarComponentKey = 855031;
IDERunOperationFailingWorker = DBGLLDBLauncher;
RawUnderlyingErrorMessage = "attach failed (Not allowed to attach to process. Look in the console messages (Console.app), near the
debugserver entries, when the attach failed. The subsystem that
denied the attach permission will likely have logged an informative
message about why it was denied.)"; }
Tried with re-installing Xcode and Command line tools, but issue persists.
Steps:
Build and run app with Debug executables true
Simulator gets launched
Error on Xcode and it gets disconnected from simulator
Is there a possibility that it can be blocked by any other app, if so how to identify ?
I solved the issue by doing the steps below:
SOLUTION 1:
Edit the scheme
Select Run
Select Build Configuration "Debug"
Select "Wait for the executable to be launched"
Close
Run the app
see the screenshot here
You will receive an error message when you run the app again.
Close the app.
Edit the scheme again and change "Wait for the executable to be launched" to "Automatically".
Now your simulator will work as expected.
SOLUTION 2:
Delete your app folder in Derived Data
/Users/[your username]/Library/Developer/Xcode/DerivedData/
Search your app name folders and delete them.
SOLUTION 3:
Open the terminal and run:
sudo DevToolsSecurity -enable
This command enables the Developer Mode. After running the command you will receive this message: [Developer mode is now enabled].
Sometimes it's happen, when you are trying to build too fast after a build has started.
First of all, quit your current simulator, delete derived data and clean the project, wait until whole processing is complete. Then do some changes / editing if required (as we clean all data) and try running on a different simulator.
Check certificates in key-chain access, if you found any untrusted certificates in key-chain access remove it.
Also if you are using beta version just make sure it is downloaded from Apple official website.
Came here to share my (strange) solution if anybody crosses the same problem with no answers working. In my case, no solution from this nor other SO answers to similar questions worked (cleaning, rebuilding project, updating, clearing derived data..)
My setup is:
Macbook M1 2022 + Xcode Version 14.2 (14C18)
This Xcode version could not attach to any of my apps (fresh new or previously developed) on different simulators (11, 12, 14) with iOS versions 13.7 - 16.2.
Editing scheme solution from answer above was not working also so I ended up in leaving scheme as:
Build configuration: Release
Debug executable Deselected(!)
Launch Automatically
And magically debugging app in Xcode started working even though it's release version with debug option deselected.. Selecting Debug executable again makes Xcode not possible in attaching to app process
Just to clarify: above steps actually makes app to run as in DEBUG mode - Xcode attaches to pid, I can do console logs and breakpoints. This Xcode version behaves opposite than options selected
My Xcode is 10.1 and has been used for over 6 months. Before upgrading Security-Updates-2009-001 from App Store in MacOS X High Sierra 10.13.6, my Xcode quitted frequently and accidentally. Today, after upgrading the security path, it finally broke my Xcode and my Storyboard in projects suddenly as the images below.
It doesn't work even I checkout my Git to previous versions. It seems that the Xcode was something wrong inside, and so does my Simulators. The Xcode cannot launch any Simulators at all and always shows "Unable to boot simulator", no matter I launch it from Scheme Building or Launchpad.
I have been testing all solutions on boards to try to recover my Simulators and Storyboards, but it doesn't work. Does anyone can give me more assistance to solve it?
Unable to boot the Simulator.
The broken Storyboard looks like this one.. and the Log text file shows
Encountered an error communicating with IBAgent-iOS. (Failure reason: IBAgent-iOS failed to launch): Failed to boot device iPhone 8 (E28478CE-81DC-4B16-A12E-16AA7086BE31, iOS 12.0, Shutdown) for context ...... The folder “disabled.plist” doesn’t exist. (Failure reason: The folder doesn’t exist.): The operation couldn’t be completed. No such file or directory (Failure reason: No such file or directory).....
and it is useless to uninstall and re-install Xcode again and again from 10.1 to 10.0 and to 10.1 again
The below permissions are worked for me.
sudo chmod -R 777 /private/tmp/
After trying again and again, I finally deleted all Xcode and re-installed Xcode 10.1 again and then changed the permission and ownership of the folder /private/tmp to 777 and root:wheel, and it finally works back!! Storyboard and xib files are workable now.
Reference: https://forums.developer.apple.com/thread/66665
This might be an issue of Command Line Tools resetting it may fix up your problem...
Run xcode-select --reset in your terminal and tell me if it works for you : D
I have spent more than 6 hours on this. Restarting the Xcode fixed it
Xcode 9.2 debugging on an iOS Simulator has completely broken for me.
I worked on this for hours and tried a ton of suggestions short of completely wiping my hard drive and starting out with a fresh operating system install. I ended up filing a bug with Apple. Posting here in case anyone has encountered this problem and has any suggestions.
Summary:
When try to build and run in debug mode with a debug executable. The simulator only opens the application to a white screen and then Xcode pops up an error:
Could not attach to pid: "<a process id>"
Ensure "<app>" is not already running, and "<user>" has permission to debug it.
Steps to Reproduce:
Make any project and try to run on any simulator.
Expected Results:
Debugger successfully attaches to debugger.
Actual Results:
Debugger is never able to attach to the iOS simulator process/app for debugging.
Debugger CAN attach and build and run successfully on a physical device.
Version/Build:
- Xcode Version 9.2 (9C40b)
- macOS Sierra 10.12.6
- Any iOS project
- Any iOS simulator
Other notes:
- Xcode 9.2 was working fine until this problem randomly started. The error initially said:
Failed to initiate service connection to simulator
DTServiceHubClient failed to bless service hub for
simulator iPhone 8 Plus <simulator identifier>
- After rebooting computer, the error shifted to "Could not attached to pid..."
I tried dozens of suggested solutions short of completely wiping my computer including:
Resetting device contents and settings on simulators
Create a new device (even different device and OS combinations)
Try different Xcode projects, even simple one-off single view applications
Looking at the etc/hosts file and verifying localhost can be pinged
Restarting computer multiple times
Deleting out derived data (multiple times)
Let it build and run without attaching debugger, then try to attach debugger by "attach to process id"
Completely uninstalling Xcode and all simulators, and reinstalling.
Removing any invalid certificates in keychain
It turns out our security software was blocking the debugger. Running sudo sysdiagnose helped me find a log entry showing that it was being blocked. The software is Cb Defense (Carbon Black Defense). Apparently the only workaround is for your security team to whitelist by a hash, and that hash could change in the future.
There is a bug in Xcode 9.0-9.2 that causes this issue to appear after running for a while. If you log out and back in it should resolve it for you.
I'm trying to run a sample app; its source can be found here: https://github.com/bandwidthcom/catapult-reference-app-voice-ios
In commit c669271, before the app was migrated to Xcode 8 and Swift 3, I was able to run it in devices from Xcode 7 - the Simulator wasn't working since one of its dependencies wasn't built for x86_64.
But since it was updated, when I try to run the application on a Simulator from Xcode 8, I get the following error:
The operation couldn’t be completed. (Mach error -308 - (ipc/mig) server died)
There's a similar error when running on a device, but since I don't have one with me right now, I'll edit this question with further details tomorrow.
I saw it working thrice. The only thing that comes to mind is that I had a clean install of Xcode each time it worked. After something like a reboot, or just a restart of Xcode, I wasn't able to run it anymore.
I don't have a firewall enabled, so the accepted answer to this question (Swift Playground and Simulator Error (ipc/mig) server died, Unable to boot the iOS Simulator) doesn't solve my problem.
Any ideas?
OBS: You have to edit the Config.swift file to be able to build the project: any value in the place of "<replace me>" will suffice.
It seems the problem was related to a framework that was being embedded in the application via symlink.
I changed one of the build scripts to copy the framework and now everything is working as expected.
Not sure why it worked before, but that seems to be the answer!
I'm using Xcode 6 with the iOS Simulator version 8.1 (build 550.3).
When I choose the "Build and Run" in Xcode everything works good, if the app isn't already installed in the simulator. If it is, however, I get the following error in Xcode:
Unable to run app in Simulator
An error was encountered while running (Domain = LaunchServicesError, Code = 0)
And the logs for the simulator show the following:
less ~/Library/Logs/CoreSimulator/CoreSimulator.log
Nov 6 11:53:47 Yggdrasil.local com.apple.dt.Xcode[4389] <Error>:
Error Domain=LaunchServicesError Code=0 "The operation couldn’t be completed.
(LaunchServicesError error 0.)" UserInfo=0x7fa697742360
{Error=PackagePatchFailed, ErrorDescription=Could not hardlink copy
/Volumes/UsersData/Users/kender/Library/Developer/CoreSimulator/Devices/AAD57C40-E208-4964-B63A-46B968B3EB36/data/Containers/Bundle/Application/FEE2DEB4-AEE3-48B7-BE71-5B027259C6FD/Baby Feeding.app
to /Volumes/UsersData/Users/kender/Library/Developer/CoreSimulator/Devices/AAD57C40-E208-4964-B63A-46B968B3EB36/data/Library/Caches/com.apple.mobile.installd.staging/temp.P8QJEE/extracted/Payload/Baby Feeding.app
with manifest /Volumes/UsersData/Users/kender/Library/Developer/CoreSimulator/Devices/AAD57C40-E208-4964-B63A-46B968B3EB36/data/Library/Caches/com.apple.mobile.installd.staging/temp.P8QJEE/extracted/com.apple.deltainstallcommands.com.owlcoding.babyfeeding}
(/Volumes/UsersData/Users/kender is my $HOME).
I tried to remove all simulators (from the Devices window in Xcode and re-add them - no luck.
I removed the entire ~/Library/Developer directory and allowed Xcode to recreate it - same issue after that.
So right now I'm stuck with Build and Run -> Make changes -> Remove app -> Build and Run flow, which kind of sucks... Anyone encountered a problem like this and found a solution, or maybe you guys have some pointers for me...
I had the same problem and it was due to localisation of the Info.plist.
My app is localised into several languages and each localisation has an InfoPlist.strings file with the CFBundleShortVersionString key. I had changed the Version string on the Target information, but not in the InfoPlist.strings files.
So I deleted the app in the Simulator, updated CFBundleShortVersionString in all the localised Info.plist files to match the version on the Target, and that resolved the issue for me.
The error indicates that installation failed because of hard linking. I suspect the filesystem for your $HOME does not support hard links. Please update your question to specify what type of filesystem /Volumes/UsersData is.
If it's not possible to support hard links on /Volumes/UsersData, then I suggest you make a local directory for your simulator data and create a symlink from ~/Library/Developer/CoreSimulator/Devices to it.
Also on a side note, deleting all of ~/Library/Developer can wreck havoc on the running simulator service. If you do that, make sure Xcode, iOS Simulator, Instruments, etc are quit, but ALSO make sure the service is killed as well by running killall -9 com.apple.CoreSimulator.CoreSimulatorService