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.
Related
I upgraded my OSX to macOS Big Sur version 11.1. Ever since I got this problem when trying to sign in in Xcode:
at the time I had an earlier version of xcode (12.2). I upgraded to Xcode 12.3 and the problem disappeared but then I came back up again. What can I do to fix this?
What I tried
rebooting in safe mode, didn't help
upgrading Xcode, solved the problem temporarily
tried to rebuild the dynamic link editor cache as suggested here but it was a dead end:
sudo update_dyld_shared_cache –force
This tool is deprecated.
I am having a weird issue with simulator it shows me this screen
I have searched around for a solution and have tried to reset the content and settings it didn't work
Currently, I have Xcode version 11.3 (11C29) and macOS version 10.15 beta installed. When I run the project with iPhone 11 pro 13.3 it shows me the black screen.
Unlike regular/ initial ios simulator set up, there are no apps installed by default.
I am running mac on VMware. Any kind of help is really helpful.
I was facing a similar issue, got it fixed by using the correct version of Xcode
For VMWare Catalina - 10.15 Beta(197a471t) use Xcode - 10.3
Use this site to Download Specefic Xcode from Apple -> https://xcodereleases.com
It also fixed a Assets.Xcassets problem I was facing (LaunchImage Problem), really bad the MacOS is so specific with these versions
Hope you get it fixed...
P.S for virtual Box users there is a command line fix ->https://wasaytechtips.com/springboard-quit-unexpectedly/
Yesterday i updated to the latest version of Xcode, since the update i experience a very strange glitch:
When i try to run the app on a device the Xcode start with the process and say "finish run the app on iPhone" and then the Xcode crashes.
what could cause this problem?
before the update everything worked perfect.
I was seeing this same issue and even trying to view the device from Window -> Devices would cause Xcode to crash. I updated the device to the latest version of iOS (8.0.2) and that seems to have fixed the problem (for this afternoon at least).
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
i have snow leopard 10.6.3 installed via iAtkos..everything runs good even XCode as well.I can successfully build iPhone apps run them on the simulator and the device but when i use the "build and archive" option( for adhoc distribution or itunes connect ) XCode simply crashes..does anybody have a solution for this?
thanks in advance
btw XCode version 3.2.3(tried 3.2.3 as well same result,also in safe mode)
Mac OS X version 10.6.3
I had the exact same problem, and it turned out it was caused by a variable of wrong type in info.plist. My short bundle version was created as int instead of string.
I was getting the warnings about it, but it didn't seem relevant since the crash happened only when archiving, and normal building worked fine, the app ran fine. I suggest you check your benign looking warnings, one of them could fix the issue.
You might try 3.2.4 (available now).