iOS 11 Simulator unusable slow

I am experiencing the same issue.

After installing Xcode Beta 4 all my MapKit code is not usable in iOS simulator due to slow speed.

I have reverted to Beta 3 where it runs perfectly.

Hopefully this is solved in Beta 5.

Not solved in Beta 5...

I'm back to Beta 3

I tried Beta 5 with iOS 10.3.1 iPhone Simulator. It is usable but Xcode makes the CPU go crazy.

I am also back on Beta 3.

Has anybody reported this issue?

This happens to me also on a mapView. It works fine on a device but the simultor is worthless in this state. I have file a bug report.

We are aware of this issue.

You can try alternate rendering modes which should help but won't completely solve the problem:

defaults write com.apple.CoreSimulator.IndigoFramebufferServices FramebufferRendererHint X

Where X is:

0 = auto

1 = Metal

2 = OpenCL

3 = OpenGL

Tried the workarround in Beta 6. It did not help anything. It is still too slow to be usable. Especially when testing MKMapView.

It seems like Beta 6 does not stress the CPU as much as Beta 5 when running code in the simulator.

Beta 3 or hardware is still the way to go when testing.

Also experiencing really bad FPS in SceneKit (not just MapKit). Even running the default SceneKit project (with the plane spinning etc), the iOS 11 simulator runs <=3 FPS in SceneKit. Can't really understand if I am the only one having the problem. The MacBook Pro I run on is early 2015 version, but until XCode 9 I haven't had a problem at all.

Intel Core i5

16GB RAM

Intel Iris Graphics 6100 1536 MB

250GB Flash Storage (Not full)

Anyone else having this problem with SceneKit (not just MapKit) as well?

Edit: Added hardware details

OK. Please file a bug report about this, even if it is a duplicate it will be very helpful. Attach the output of "xcrun simctl diagnose".

Please file a bug report about this, even if it is a duplicate it will be very helpful. Please attach the output of "xcrun simctl diagnose".

Yes, I've seen this since the first beta of XCode 9. It's OK with the simulator for iOS10.x and earlier, but the iOS11 simulator is unusably slow (like 30 seconds to zoom them Map in or out, even when there's no annotations). There doesn't appear to be any problem when debugging on a genuine iOS11 device, so it seems to be confined to the iOS11 simulator.

I've submitted a bug report with diagnostics per the Apple Tech request.

Hey Apple, please take this seriously. It is probably blocking the UI-thread with some kind of internal background operation, causing extremly long UI delays. Hopyfully this does not slip into the GM.

Unfortunately Xcode 9 GM still contains this bug!!

I am not able to test my MapKit App due to very slow performance.

This starts to get very annoying as I have to turn to beta 3 which was the last version with good simulator performance.

Apple please...

It's still the same in the GM

Sad to see that this problem still exists in the GM build 😟

Simulator on GM is completely useless. on my Mac Pro 2009 even springbord is slow in the simulator

Still in GM. C'mon!

Apple please... Fix it...

When i launch the maps app in OS11 Simulator, the CPU is loaded up to 100%.

I confirm this! MapKit and SceneKit are unusable under simulator! Apple FIX it, pls!!!

(iMac 27-inch, Late 2012)

Regardless of the app I try to run on an iOS 11 simulator (no matter the device type), it is pathetically slow to the point of being unusable.

I've tried apps based on Cocos2D, SpriteKit, SceneKit and UIKit. In every case the simulator is useless to me.

This is with the GM Seed of Xcode.

How on earth am I supposed to update my apps to work with the iPhone X if I can't even see them run in the simulator?

Regards

Running "xcrun simctl diagnose" kills the simulator with a message like:

2017-09-14 11:35:50.965 simctl[28241:670948] CoreSimulator detected Xcode.app relocation or CoreSimulatorService version change. Framework path (/Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/CoreSimulator.framework) and version (375.21) does not match existing job path (/Library/Developer/PrivateFrameworks/CoreSimulator.framework/Versions/A/XPCServices/com.apple.CoreSimulator.CoreSimulatorService.xpc) and version (494.13.6). Attempting to remove the stale service in order to add the expected version.

I'm guessing this is because I'm running Xcode 9 GM from somewhere other than /Applications? I don't want to remove Xcode 8 until I'm confident that Xcode 9 is actually stable. Thie issue with the simulator and iOS 11 is definitely an indication it aint stable.

I'm running Xcode 9 GM, and seeing the slow down in the Simulators for iOS11, but they work fine for iOS10. Another problem is Xcode 9 destroyed all the Simulator libraries for Xcode 8.3.3, and now Xcode 8.3.3 won't install simulators any more. In addtion if I build with Xcode 8.3.3, it runs really slow on an iOS10 device now. Xcode 9 really screwed something up, and it's messed up older devices now too.

My advice to everyone is to not download Xcode 9 since it doesn't work properly.

Running Xcode 9 GM, MacBook Pro 15 inch 2012, SceneKit is really slow in iOS11 running on iPhone X simulator, MapKit is also slow. It's fine though if I run Xcode 9 GM and iPhone 7 Plus with iOS10.

In general Xcode 9 GM still feels like early beta to me.

Almost all my apps make use of MapKit in one way or another, so all of them are unusable in the simulator at this point.

I tried using real device for developement, but the new wireless debugging is also glitchy and doesn't seem to work as it should.

Indeed. Non only the simulator: wireless debugging does not always work (you have to put the old cable), not to mension the many crashes trying to reorganize the project using the new groups/folders. Very hard to do our job.

Ok, I also filed a bugreport (34428478)

I was just wondering as quite some people have the same issue. Can't you reproduce it? I have only my MPB to test, but it happens here all the time. Also for friends of mine it's happening all the time. So I am quite afraid of having to adopt my app (that has maps everywhere) for the new iPhoneX as I have to use the Simulator to test it...

I would really really appreciate it, if you could fix this bug soon 🙂 Next time I am in the US I'd buy you a beer 😀