I recently updated my Mac OS to 10.8.5 and installed Xcode 5. First couple of times it opened but it was excruciatingly slow. Actions like cleaning, building the project took ages and when it finally ran, even the app won't function properly. It was like the app was frozen. So I quit Xcode to re-open it but now even Xcode won't start. I had to force quit every time I tried to open it.
I removed Xcode and installed it twice. One time from the .dmg I downloaded separately and the other time, through the Mac App store. But both time the same not responding issue persisted.
Can anyone please tell me how to rectify this issue? I'd really appreciate any suggestion.
Thanks
Related
I know similar questions have been asked many times.
My xcode projects ran fine on the simulator. Ive started a new project today and the first time I tried running it I get the black screen and 'unable to boot simulator error'.. and I have to force quit xcode. Now all my projects are getting the same error??? They were working fine before.. I have not updated anything either? Whats the problem?
Thank you
After many failed attempts at fixing the problem I ended up updating the OS from El Capitan to Sierra and I completely uninstalled Xcode and reinstalled a fresh version (from 7.3 to 8). The problem is now gone. I am assuming there was some kind corruption in Xcode as I cant figure how else this specific issue would occur.
I've just downloaded Xcode beta 6.2 however every time, e-v-e-r-y time, I launch it OS X is verifying it which is takes several minutes.
Did anybody else have the same problem and knows how to stop it from happening all the time.
Try this in a terminal window:
xattr -d com.apple.quarantine /path/to/Xcode.app
That should prevent OS X from having to verify it.
See http://furbo.org/2014/09/03/xcode-vs-gatekeeper/
I had something similar. Each time I would launch Xcode, Gatekeeper would kick in and verify the package.
I solved the problem by going to the app store and installing Xcode.
I am building a Mac OS X application and from time to time, I get this error message from Xcode (Version 5.0.1 (5A2034a)):
However the architecture (i386 or x86_64, it seems to happen on both) is supported by my system (Mac OS X 10.9).
Clicking a second time on the Run button (or press Cmd+r) sometimes fix the problem.
Sometimes I have to delete the application in my build folder and then rebuild it.
Note: I am using cmake to generate the Xcode project.
The same thing just started happening to me.
As was suggested here, stopping and starting Xcode cleared the problem.
My Xcode 3.2.6 is hanging up constantly.
While I'm coding with no apparent reason it starts consuming more and more CPU, CPU temperature rises up to 80 celsius, the fan get exhausted and I'm forced to "force-quit" it and relaunch it to be able to continue working...
It start happening this week and nobody else on my project is having the same troubles.
My OS is Snow leopard 10.6.8
Any ideas on what could be happening?
I had the same exact issue with my Xcode 3.2.6 project... Would start out using one core and if I let it sit, would use all 8 cores of my i7 MBP. Very frustrating having to restart Xcode every 5 minutes.
My issue actually was resolved when I removed an iPhone from the Organizer that was running iOS 5.0.1. Xcode was trying to get information from the iPhone, and wasn't able to, since the iOS SDK requires Xcode 4.x
I also removed all the user settings from within the project's *.xcodeproj package as well; not sure if that had additional effect. removing those without removing the iPhone had no effect, though.
Have you tried doing a "clean" on the target? Have you tried checking your disk with Disk Utility?
it happened for me a lot but it's not happening every time ..
some times when i launch iphone application from xCode 4.1 in lion osx it closes all application and can't reopen them again unless i restart the machine.. what the wrong
is this happen to me alone?
File a bug at http://developer.apple.com/bugreporter/ and hopefully the issue can be triaged.
The more info you provide in a bug, the better chance there is to figure out the cause.