This question already has an answer here:
Seeing a guid as part of the simulator choices
(1 answer)
Closed 7 years ago.
Very confused why my Xcode 6.4 suddenly stopped showing the iOS version for the simulators. Now, it just displays some identifier for each simulator and it is very annoying and hard for me to navigate between simulators.
I also have the Xcode 7 - Beta 4 installed. But i do not think that is the reason though. Because, earlier i've had Xcode 7 Betas along with Xcode 6.x and it used to work just fine;
Wanted to find out if others have faced the problem and a possible solution.
Your help is very much appreciated.
This happens to me a lot when I have installed multiple versions or updates of Xcode. Sometimes it helps just to quit Xcode and restart the computer. If that doesn't solve it, I simply open the Devices window (Window > Devices in Xcode) and delete all the simulators. Then I recreate simulators, one by one, that I actually want. This causes Xcode to behave properly again.
Related
I know that so many people have asked this question earlier. But I think my situation is different. In my case Xcode 9.2 was already installed and I upgraded macOS from 10.13.2 to 10.13.5. Then I installed Xcode 10 beta. Now when I'm running any project on Xcode 9.2 and try to use simulator, its becoming black though I can see the xcode logs. Things I have tried so far,
Uninstalled Xcode 10 Beta
Uninstalling & reinstalling Xcode 9.2
Uninstall Xcode 9.2 and install Xcode 9.4
Reset Content & Settings from simulator menu
Restart Device from simulator menu
Resizing simulator.
Followed this post and cleaned DerivedData, CoreSimulator, iOSDeviceSupport
Re add simulators from devices & simulators section
Now what should I do now?
Try running defaults write com.apple.CoreSimulator.IndigoFramebufferServices FramebufferRendererHint 3 in Terminal (source). Note that this will force Simulator to use OpenGL instead of Metal, so you'll want to re-run it with 0 once this gets fixed.
try workaround, delete Library/Developer folder and start it again
Another option that occurred for me. I subclassed UIWindow and called .init(frame: .zero). Changing to .init(frame: UIScreen.main.bounds) fixed it.
Open up XCode 9 and go to add additional simulators(pictured below) re-add iOS 10 and iOS 11 simulators
You seem to have tried everything except changing the iOS simulator version you are trying to run.
Maybe the problem lies with that specific version of iOS simulator eg. iOS 11.x iPhone 6. Change that and it may run OK.
If you do not have desired version with you, go to XCode->Preferences->Components, and download one of the older iOS simulators available at the time of XCode 9.x.
Then, go to XCode->Windows->Devices and Simulators. Press + sign at the bottom left of the screen. Add your desired simulator version (give your desired name), so that this newer simulator appears in runnable scheme list of XCode.
This is just for the users that failed trying everything to save Xcode 10 and then reinstalled Xcode 9.4.1 and the simulator still not working.
Here is what I did to give Xcode 9.4.1 back running.
After I got this problem after upgraded to Xcode 10.
I tried that famous FramebufferRendererHint, didn't work for me.
I have found out the Xcode 10.1 beta release didn't fix the problem for someone else, so I didn't bother to try 10.1 beta.
From the online research I know the problem is in /Library/Developer/PrivateFrameworks/CoreSimulator.framework.
Without Xcode even installed on your Mac /Library/Developer doesn't exist.
So it is installed by Xcode when your first time run Xcode. You would notice a screen showing "Installing Components"
But after you installed Xcode 10 and then install/run Xcode 9.4.1 it won't touch that folder anymore. So problem stays even you put Xcode 9.4.1 back
That's why after I downloaded Xcode 9.4.1 expanded and ran it. Problem still there.
I didn't backup my Mac. So I decided to start from scratch. Restored my MacBook from Internet, downloaded Xcode 9.4.1 again. and now everything is back to normal.
I can keep releasing the App to App Store now.
In my case (xcode 10), I just left the computer for 10 minutes or so (out of frustration!) and when I came back I found it at the starting screen! .... I guess for the first time it takes time
I'm trying to get UI testing set up for my project - I encountered a crash with previous betas. (See this stack overflow question if you are interested)
Anyway, I was quite thrilled to try it with Xcode 7 Beta 5. I created a simple Single Page app, added a text field and button, and ran it in Simulator. The simulator loads but the app doesn't get installed.
I've tried it in different simulators, all iOS 9 - same behavior in all of them.
Anyone else see this behavior? Am I missing something?
I have a project which I developed under Xcode 6. Since only Xcode 7 lets me install apps on a physcial device without developer programm, I opened the same project that ran without errors in Xcode 6 in Xcode 7 and got 35 issues. I didn't want to resolve them so I closed the Beta version. Even though nothing was changed in the source code, I still got 24 issues when I opened the same project that before ran smoothly in Xcode 6 when reopening in Xcode 6, stuff like "println has been changed to print", even though it's still Xcode 6. Does anybody know how to fix this issue? Even the SplitViewController template produces a whole lot of errors!
Xcode remembers the warnings of the last compile process in the project. So the warnings will automatically disappear as soon as you compile the app again using Xcode 6.
The correct answer was posted in the comments to my question by the user Avt:
Press Alt+Shift+Cmd+K to clean build folder. Then recompile. – Avt
I recently tried to run a simulation of a new iOS 7 app on Xcode 6.1.1 using my MacBook Pro during a visit to Indonesia. The app was based on AddMusic and made iOS 7 compatible. When I tried to run the simulator abroad iOS simulation targets available while testing in Australia had simply disappeared from the pulldown menu in Xcode. Moreover since I came home these simulators only reappeared when I removed, downloaded and reinstalled Xcode.
Until I reinstalled Xcode the only option Xcode offered was to run the app on an iOS device but I wasn't prepared to do this in front of clients without first being able to test a revision on a simulator.
Thankfully on this occasion I was able to demonstrate earlier versions I had installed on an iPhone 4 and iPhone 5 C before I left home. But it would be really good to know what I might be able to do to avoid this situation during my next visit abroad.
I suspect the issue may have been brought on by differences between my Internet connections at home and abroad.
Has anyone else experienced a similar problem that might be related ?
Top to your Right Click on
Window > Devices
You will see that no devices will be showing Do the following
Bottom Left
Click on the +
And then start adding your devices.
Just closing the projects from the File Menu, quitting Xcode and restarting Xcode worked for me
the version is the latest Xcode 7
Some things which might help you
Check deployment target in your project settings. Switching to lower versions of OS might help you get back all simulators.
Check your xcode version used in the command line tools. Go to Xcode -> Preferences -> Locations -> Command line tools
Quit Xcode and restart your system.
Hope these things help !!
I'm using Xcode 5.1.1 on a MacBook Pro running OS 10.8.5. I've built an iPhone app (my first) using the iOS 7 SDK. Things are very stable, and the app is, I believe, ready for TestFlight.
Now I'm assailed by Xcode 6 and iOS 8. I want to go forward, but am kind of spooked that switching Xcode at this point may run the risk of breaking things. A lot of the reviews I read are negative, but I expect people who have problems are more likely to bellyache than those for whom things go smoothly. OTOH, I read that TestFlight is well-integrated into Xcode 6.
I recognize that answers to this question may be opinion-based, but I haven't found anything specific offering guidance for my particular circumstance.
Should I take the chance and upgrade Xcode and the app, or wait until I've launched, then upgrade and work iOS 8 support into an update?
Afterthought
I just checked and the upgrade to Xcode 6 requires an OSX upgrade to 10.9.3, which adds another layer of terror. :-O
Resolution
Ok, I steeled myself and went forward with the upgrade--Mavericks and Xcode 6. First thing I noticed is that my keyboard isn't appearing in my user input modals. But that's a subject for another post. Other than that, the OS and Xcode seem to be working ok.
Yes! There will be a few adjustments to make, but there always is. The only thing that's caused me extra time so far is Xcode 6 Auto-Layout for iOS 7 devices (e.g. layout margins). But it's not too bad.
Chances are many of your users are already on iPhone 6 and 6 Plus and/or iOS 8. Do you really want to ship to them without optimizing for their devices?