Related
I just updated my mac to macOS Big Sur, and am trying to update to the next version of XCode. It has been on 75-80% progress for hours:
Also, when I go to launchpad I see this:
Is anyone else having this issue or know how to fix it?
As a first test to check if everything is just going fine but really slow, try this:
Keep the App Store window open (thanks to #Dhruv Saraswat to point this out).
Open the "Console" app (not the "Terminal", but the "Console")
Go to the "Search bar" and type "App Store".
Push "Start" button.
Log lines will be added from time to time showing you how the installation process goes. In my case, I saw "... Completed: 825 of 1000", and some time later I got "... Completed: 826 to 1000", and so on.
That way you can at least check if everything is working, although really slow. You can then guess how long it will take to the "Completed: 1000 to 1000" step in your own situation.
This is weird behaviour everyone face nowadays when installing from AppStore. Instead of that download dmg of required xcode version from apple developer account and install.
Please refer below link to download XCode versions.
Xcode download link for all versions.
Above link contains download link from XCode version 1.0 till the latest.
mine was stuck for about 3 days and even rebooting didn't help!
i was trying to update to xcode 13.2.1 on MacOS Monterey
what i did was:
1- opened Activity Monitor and force quitted "installd" (not sure if it was necessary though!)
2- opened Launcher, held Option key (to make the icons jiggle) and clicked the x on xcode's corner! asked me if i want to delete the app and i confirmed but magically it stayed and when i opened it it was updated to the latest version! so basically it was done installing just didn't know it.
in my case force quit installd, close and open appstore, run update again
Had the same issue after updating my MacBook to Big Sur and trying to update Xcode to version 12.5.
Tried to reinstall, reboot my Mac, delete the app and install it again from App Store.
Decided to leave the installation overnight and it helped! In the morning Xcode was installed successfully.
I was stuck at Completed : 808 of 1000.
This is workaround.
Left down side of App store application screen, there is an account button.
Press account, then you can see message you should ACCEPT something.
Press accept and enter iCloud password.
Then magic. Console's app store log numbers going up.
Just FYI: On the latest Macbook Air M1, 8GB RAM, 256GB SSD, I installed XCode from the App Store. I had exactly the same issue. I thought my installation is stuck. I left Macbook for the whole night, then it downloaded XCode (around 12 GB). After that, it started installing it. I left it for the whole day and didn't touch it. In the evening XCode was installed. I just needed to leave it for around 24 hours to do the job.
Best way is to open 'console' (not terminal) app on Mac and type 'App Store' in the search bar then hit 'go' button as per first screen shot
You will start to see the lines come in and you need to make it wide enough so you get to see the parts number and notice the progress like in the second screenshot
You will notice some of those numbers will move fast, some will take up to 10 minutes, but at least you know you are not 'stuck'!
I had exactly the same situation, I updated MacOS and then updated Xcode to 12.5.1 and it got stuck on 7.2GB of 7.2GB. I left it for 4 hours with nothing happening (but in Activity Monitor 'installd' was working away). I left it overnight and it had sorted itself out by the morning.
If (like me) you only need the command-line tools, you may want to give this a try:
force-quit installd (using ActivityMonitor or ps -kill)
run xcode-select --install from the Terminal command line
Worked for me!
For me, the solution suggested by #thelawnmowerman worked perfectly.
Just need to check the number that is currently in progress out of the total threads. Once it completes the total, in a few mins, the xcode can be launched.
Although it does not speed up, but in Mac App Store, you should see the spinning wheel next in Xcode - place the cursor ON the wheel and you should see the installation progress (eg 52%).
If it does not move, cancel the Xcode installation and start again.
Confirm it has in 13.2 and 13.2.1 as well. Viewing the console app in the top answer will show you when it's done
I updated Xcode on M1 macbook pro with lots of RAM and lots of SSD MacOS 12.1 today from 12.2 to 12.3. It took 4.5 hours. So patience helps, and watching the logs as well.
I had the same problem, and for me, the tips in this thread did not work. What I found to be the problem is that App Store didn't think I had enough space when in fact I had enough space for Xcode.
To solve the "space" problem you can create a dummy file and directly remove it. This allows you to trick your computer that you actually have enough space. (Has to do with containers, read here for more info: https://medium.com/geekculture/installing-xcode-with-not-enough-disk-space-available-b96c8f17115b)
STEP BY STEP GUIDE:
Open the Terminal
Move to the location where you want to create your file using cd. Like cd Documents
Now use command mkfile G your-file-name.ext ( example: mkfile 4G mymovie.mov => will create a movie file with name mymovie of size 4GB)
Hit Enter, It will take some time to complete the process (depends on the file size)
When the command completes the prompt should return and a file would be created.
Go to finder and remove your file. (Move to trash)
Emeditly install Xcode again.
Hope you find it helpful :)
I faced the same issue. I monitored the process using #thelawnmowerman answer. But the process was getting stuck after progressing.
I terminated the App Store every time the process got stuck and opening it again also started monitoring process again, it started progressing every time and I reached to the 1000 (100%).
I am using a base Macbook Air M1 2021 (8 GB RAM). I downloaded Xcode from the
apple developer portal and installed it with the xip command. Open your Terminal and type the below:
xip -x ~/file-location
Double-clicking the file takes too long, the above command took ~5-8 minutes to expand the file. After that just move it to the applications folder so you can find it in the Launchpad.
Reference to answer: https://stackoverflow.com/a/56913909/15425440
Turning off the file shield of your antivirus will helped in my case.
While an anti-virus shouldn’t technically block an app from the Mac App Store, it seems that Xcode is an app with its own unique set of problems which is why disabling the anti-virus works in some cases.
The Console is very helpful. It shows that installation is working, albeit slowly.
I had to download xCode 3 times. Re-install it 3 times. All in all about 8-12 hours effort.
It is still proceeding, SLOWLY.
It would be very helpful if the Apple team put in a better "installation progress" indicator -- like exists for so many other products.
I faced a similar issue while installing the 13.3 version. My progress bar was showing installing for about 1-2 hours and then it started showing waiting. What eventually worked for me was installing it using terminal code "xcode-select --install".
Solved - My new MacBook Air M2 was struggling with downloading and installing Xcode. The problem, I think, was that the laptop sleeps after a short period of time and that stops the download/install process. Download/install restarts at 80% or 0% when the laptop is reawakened - repeat. A simple way to avoid the laptop from sleeping is to open the Terminal application (Application/Utilities/Terminal) and type "caffeinate". That prevents the laptop from sleeping and lets the download/install process complete itself. When done type control-c into the Terminal and it will quit caffeinate.
This was so frustrating for me
When I checked the console, I felt like there was a problem with my account.
Because I changed my password once before.
So I went to App Store -> my account -> I had to login again.
After trying to update to Xcode 14.1 on Ventura for nearly 24 hours, I eventually trashed the Xcode application, rebooted, started only the App Store, and did a new install, leaving the App Store in the foreground. It downloaded (about 7 GB in 20 minutes) and completed the install in less than an hour on my M1 Mac mini.
Background:
After updating to Ventura, there was an update to Xcode 14.1 in the App Store. As with previous versions, I had trouble installing it. This time though, the install would progress to 61% (seen by hovering the mouse over the spinning circle in App Store), then stay there. Filtering for ASDAppQuery in the Console, as suggested in other answers, showed progress for a while, but then also stopped. The installd process was still using a lot of CPU. However, after a while it would stop doing so. It seemed that the App Store app would stop, and a couple of times I checked Activity Monitor and saw that it was in "App Nap" mode. After waking up again, the appstoreagent would run at 95% CPU (one core) for a while, followed by installd running again, at around 300% CPU. This cycle continued, but with no progress. I tried leaving it overnight, but in the morning it was in the same state: neither appstoreagent nor installd doing anything, but then seeming to wake up and grind away again, but making no progress. I had also tried quitting the App Store and starting again, but the same kept happening - going to 61%, then spinning away with no progress indication. Finally, I decided to trash Xcode, reboot, and install - that worked quickly and flawlessly.
fixed forcing close the installd process and run again the App store
Oh, it really helpful!
I user IOS12.3.1 in VMWare Station, and when I update xcode from 13.2 to 13.3, it get stucked.
additoin: my cpu is i5-9
You can open the app store, search XCode and click the stop button. Worked!
System Preferences is trying to unlock users & Groups preferences
Unable to open System preferences for the my MacOs High Sierra.
sudo commands helps to provided the access to unlock the usergroups?
Also had this problem recently, however my account was an admin account, as shown in the Users & Groups pane. sudo in the terminal was working correctly, and I could even create new users (admins) using the terminal, however logging in as them would give me the same problem.
Solution was to reset the SMC:
Power off the Mac
Power on the Mac while holding Control+Option+Shift and continue to hold the Power button for around 10 seconds.
Release the buttons and power it on again if it has done it already.
Only admins can change the settings for the Users&Groups. You need to type in your login (username and password) to be able to change the settings. If you are not an admin on this machine, you need to have somebody else who is type in their credentials.
It’s works after doing this
Restart mac hold
Ctrl + S
It’s open OS X terminal
mount -uw /
rm /var/db/.ApplesetupDone
reboot
Then follow the instructions to setup for admin
SMC reset worked for me just now (same problem, after upgrading to Big Sur)
Restarting in boot mode and running the following commands should help.
fsck –fy
mount –uw /
rm /var/db/.AppleSetupDone
reboot
More details can be found here: https://youtu.be/2NhTlvCjFJI
I was trying to install ruby on my Mac and i just opened terminal and it won't let me type anything in it, when i go to open it 2 windows pop up both with the same message on.
[forkpty: Resource temporarily unavailable]
[Could not create a new process and open a pseudo-tty.]
I don't really know what it means and i have never come across this problem before, i tried quitting terminal and restarting my Mac but it just does the same thing.
Any help is appreciated.
I have fixed this problem! I tried logging into guest user and then going back into my current user and it seems to have been fixed.
Anyone has experienced this problem?
Yesterday I still can run my app in simulator but now I cannot run my app since Xcode prints this error in console:
error: failed to attach to process ID <ID number>
I have tried to reinstall, do this post and create new project but returns no luck.
Anyone can resolve this issue?
I use Xcode 4.5 Preview 2 and try to run iOS simulator 6
Resetting the content and settings in the simulator worked for me. This is available in the "iOS Simulator" menu.
go to the Product menu and find the Edit Scheme menu there.
While in Edit Scheme window, select the "Run" option on the left hand side of the screen and then on the right hand side, change the debugger from LLDB to GDB.
I experienced the same problem, and after a while I found out that it was due to the fact that my XCode project included a Folder Reference to a folder named Resources.
It seems that XCode doesn't like that name.
Just removing the folder reference or renaming the folder solved the issue.
TWO METHODS
Method 1 : Inside the folder Application Support -> iPhone Simulator -> In the each simulator version of iOS -> Applications -> Delete all the files present here.
Now go to Products -> Clean
Now run it on any simulator and it will work.
Method 2 :
Step1: ping
$ ping localhost
This should return something like
PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.028 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.048 ms
...
If this works, this answer won't fix your problem, try something else.
If ping return something else for example: ping: cannot resolve localhost: Unknown host something is screwed up with your /etc/hosts file, go to Step 2
Step2: Check /etc/hosts
Check that the top of your /etc/hosts file looks like this
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
If it doesn't have these entries in the file, enter them at the top of the file, flush the dns cache using $ dscacheutil -flushcache and go back to Step 1, otherwise continue to Step 3.
Step3: Correct File Format: It should be unix or LF *
$ file /etc/hosts
This should return: /etc/hosts: ASCII English text
If it returns something like /etc/hosts: ASCII English text, with CR line terminators then the file is in the wrong format and is likely being ignored.
Change the file line endings to unix or LF using your favorite text editor.
In Sublime Text 2 this can be done throught the view menue: View > Line Endings > Unix
Flush the dns cache ($ dscacheutil -flushcache) and go back to step 1
Similar to fundtimer's answer, the local hosts file seems to have been the culprit.
I had to change my /etc/hosts permissions back to the default after an inadvertent change:
sudo chmod 644 /etc/hosts
After that, simulator/LLDB worked for me.
This is an old topic, but I believe things have changed a bit for the latest version of macOS.
I've stumbled on the issue while trying to run an UI test suite for an iOS app in the simulator on macOS Mojave Beta and Xcode 9.4.1.
Turns out, on macOS Mojave the codesign tool (which is a part of the OS itself and not a part of the Command Line Tools or Xcode) signs processes into a hardened runtime environment which includes runtime code signing enforcement, library validation, hard, kill, and debugging restrictions. This, together with the System Integrity Protection in macOS Mojave, prevents the lldb debugger from connecting to the running target.
To resolve this, you have to options:
An obvious one, probably, is just to use Xcode 10. It does seem to handle the connection gracefully.
Reboot the OS into the Recovery Mode and turn off the System Integrity Protection from the Terminal with csrutil disable. The debugger then connects happily.
I've spent quite an amount of time banging my head on this and was able to resolve it all after reading the following article: http://www.lapcatsoftware.com/articles/debugging-mojave.html
Just my two cents. Hope this helps someone.
I had somehow removed or deleted records from my /etc/hosts file and I got the same error.
You should check whether you have in your /etc/hosts file the line "127.0.0.1 localhost".
This helped me!
I know this is an old question, but it came up first for me when I did a google search for "failed to attach to process ID". I'm using Xcode 7. Happened after iOS9 was released and I had updated my swift app for swift 2.
Deleting my app in the simulator and doing a new build and run cleared it up.
I've had the same problem when debugging on the device. The app crashed on start but didn't appear as a running process.
My solution is to use some process viewer app (e.g. System Status or similar). Find your stale app and then find the parent process id which usually is debugserver.
Go on Xcode, Product -> Attach to Process -> By process id and attach to the debugserver process PID. Wait a second and then press the Stop button.
The stale debugserver and app processes disappear.
(When using the simulator, the equivalent would be to use the terminal, ps, and kill the App process. Haven't tried that, though).
I just removed the application from the simulator (just like you would on an actual device), and when I re-ran it everything worked fine.
I have also same problem and for me the solution is :-
Just delete the app from the Simulator and then clear and Run the project.
May it help also to someone else.
I fixed this problem by removing Xcode Derived data contents.
In finder press SHIFT+CMD+G and type below path and remove all data inside DerivedData:
~/Library/Developer/Xcode/DerivedData
Also reset simulator builds
~/Library/Application Support/iPhone Simulator/6.0/Applications
I just posted this on the Developer Forum. It was a simple solution and may help someone here:
I had exactly the same problem: when using any current version of Xcode 4.xx and the LLDB debugger, plus any version of the Simulator, XCode consistently crashed with 'failed to attach to process ...' My only resolution was to switch to the GDB debugger. This was disappointing since I really wanted to try the new, robust LLDB in XCode 4.6-DP.
And then I remembered; I had changed my network/server host file at ...etc/hosts some time ago to accomodate several Apache2 server virtual hosts, i.e., I removed the line:
127.0.0.1 locahost
That was it. Removing that line, XCode crashed on attaching to the Simulator with LLDB.
Restoring that line, XCode worked just fine with LLDB and the Simulator.
Anyway, this may not be your problem but it's worth exploring. As far as I'm concerned, it's a serious undocumented bug.
In my case the solution was different: the run mode was "Release". Changing to "Debug" fixed it. Xcode 4.5.x had no problem with it.
The issue for me was caused by a pretty stupid mistake: I created a new target for my project by duplicating an existing target and forgot to change the Bundle Identifier in the target's info.plist file.
Above answer really helped me.
https://stackoverflow.com/a/12819757/1752988
Because in my XCode I used story board and custom view controller. and in its warning list that I saw some of the nib files are missing. I was miss leaded by seeing that. However, I saw this answer,
and even though I didn't like to reset my App simulator content, I did it and it really worked for me.
And also Changing the Debugger from Product -> Scheme -> Edit Scheme (Run) from LLDB to GDB didn't work for me either.
P.s.:- Pardon me,I added this answer as a support comment to above, as I don't have 15 reputation upvote the above answer or 50 points of reputation to comment on above.
I solved this problem by quitting XCode and Simulator. Reopen the Project. Done.
The following worked for me on iOS 9.1 :
Just uninstall the app from the simulator
Quit the simulator (Cmd+Q)
Clean your Xcode project
Run on simulator
Note: No need to reset the simulator.
I am working on Ionic 2 application, I am new to this and even Xcode and simulator.
Initially my app was working on simulator but after some time it start generating error like-
xcode error: failed to attach to process id
I searched for, tried all above answers but my issue was not resolved.
Then I updated (Ionic, npm, cordova) my machine setup-
******************************************************
Dependency warning - for the CLI to run correctly,
it is highly recommended to install/upgrade the following:
Install ios-deploy to deploy iOS applications to devices. `npm install -g ios-deploy` (may require sudo)
******************************************************
Your system information:
Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0-beta.10
Ionic CLI Version: 2.1.8
Ionic App Lib Version: 2.1.4
ios-deploy version: Not installed
ios-sim version: 5.0.8
OS: OS X Yosemite
Node Version: v6.2.2
Xcode version: Xcode 7.2 Build version 7C68
******************************************************
After this I just run a command from my application home directory
ionic run -l
ionic build ios.
imported xcode changes to xcode.
Reset content and setting as-
clear product from xcode,
Run Xcode and now it is working on simulator.
Happy to see this!!!
So many answers to this and I didn't see what I believe is the correct one. It's an issue with authorization. Type this in the Terminal:
sudo DevToolsSecurity -enable
On Xcode 9+ do the following:
Go to the Xcode menu: Product-Scheme - Edit Scheme and under Run tab be sure that the Debug Executable checkbox is checked! That's it!
Just reset content and settings of iOS simulator and then clean code by pressing command+shift+k keys to clean code.This worked for me
As lame as it is, restarting my computer was the only solution that worked. I tried switching from LLDB to GDB, resetting the contents of the Simulator, and restarting Xcode. The only thing that worked was restarting my computer, reopening Xcode, and re-running the app.
I had the same problem. I did some combinations of answers given to make it work. :)
clean the Build Folder by clicking "Product" in the MenuBar. while pressing the Alt-key click on "Clean Build Folder". Now restart your xcode and simulator.
Now it should work. if not, also try changing bundle identifier and Simulator "Content Reset" and then restart xcode and simulator.
Ran across this today. I accidentally removed my Launch images from my Target Settings.
try to do next steps:
Go to Product/Scheme/Edit Scheme then select Run section.
Select Info Tan and set Debugger None.
Run project. It must be working (without debugger)
Go back to Edit Scheme and selecet debugger LLDB
Run project. It is working.
Maybe additionally you need to delete derived data and do Product/Clean
Do you have multiple users logged in to your machine? I have "personal" and "work" accounts on my laptop. I got this error when I was trying to debug from my personal account, but I had left the simulator running in my work account. Quitting the simulator in the other account fixed my problem.
and another one for the record: (none of the suggestions worked for me)
Mountain Lion: XCode 4.6.3
I moved the whole Application to Trash and deleted following other folders
/Users/[USERNAME]/Library/Developer
/Users/[USERNAME]/Library/Caches/com.apple.dt.XCode
/Users/[USERNAME]/Library/Application Support/iPhone Simulator
reboot System and reinstall XCode
Also had same problem today. i was using Xcode 4.6.3. i closed my project and open it in Xcode 5 and it is running perfect.
Strange but True
I keep getting this error when launching my app on the iOS Simulator:
Couldn't register com.mycompany.MyApp with the bootstrap server. Error: unknown error code.
This generally means that another instance of this process was already running or is hung in the debugger.
I've read other reports of this error and it seems there is no obvious fix for it (restarting the iOS Simulator, restarting Xcode etc..)
At this point here's a list of things I've tried:
Restarting the Simulator
Restarting Xcode
Rebooting my machine
Deleting my app's Derived Data, and Cleaning
Deleting the iOS Simulator App Support directory
Reverting to a 2 weeks old version of the app (which was working 2 weeks ago)
Deleting the application in the Simulator (by clicking-holding on it and hitting the X button)
Upgrading Xcode form 4.1 to 4.2, and running the app both in iOS Simulator 4.3 and 5.0
Nothing worked, I still get the same bootstrap error.. Any (and at this point I really do mean ANY) suggestion would be appreciated.
Edit: Just wanted to add that the app runs fine on a device. I only get this error on the simulator...
As the GDB said:
This generally means that another instance of this process was already running or is hung in the debugger
So find out it and kill it. ;)
I restarted the mac, and it run successfully.
Tip: Well, this may be not work sometimes, so I strongly suggest that you press cmd+. to make sure that you do have stopped the simulator (or device). I find that in most cases the simulator (or device) will not stop exactly when it crashes. I rarely met this issue again with pressing the cmd+. every time it crashes or even just normal exit. Hope this will be helpful. :)
I just closed my xcode & restart my device(ipad2) and it works for me :)
You can try this :: Couldn't register with the bootstrap Server
Another solution, go to clear the memory of the iphone simulator
Simulator > recovery content and setting
then run the program again.
i just change the identifier and the app can work again.
I had to change my bundle identifier finally
No matter you reboot all devices and cleanup all , it gets stuck hard in the debugger..
don't know how to clear it..
As I experienced, device (or simulator) restart does solve the issue,
BUT it would be better not to couse it.
Also my experience is that:
You can find the place of crash by cousing it. In such time developers usually press "STOP the running scheme" this could cause zombie process stuck in device.
BUT
if you press "COUNTINUE program execution", debugger will terminate the process, it will not become a zombie.
I had this error too and I noticed that it works for me if you close the simulator and stop the program and then change your company name.
I don't know why but it works for me.
I opened Activity Monitor and searched for my app name, and found another instance of it listed. I used Activity Monitor to quit that instance, and the problem went away for me.