Hi,
the iOS 11 Simulator is unusable slow for me when using MKMapKit. I'm getting <= 1 FPS with major UI lag when:
- Running an app using MKMapView
- Running the preinstalled Maps app
I'm on High Sierra (17A315i), using Retina MBP Mid 2012, Intel Core i7 2.3 GHz, 16 GB DDR3 Ram, Intel HD 4000 / GeForce GT 650M.
iOS 10.x Simulators are working fine with Xcode 9.
Unfortunatly, the problem persists in XCode 9.1 Beta.
Hope this helps someone. I was having the same issue with Xcode 9 GM and unticking the below Simulator option fixed it for me.
Simulator Menu > Debug > Slow Animations (untick)
For me the same, open Simutalor load OpenGL objects and Emulator cpu rise to 150%, really... i use device to test.. but sometimes quickfix via simulator helps.. Now is unusable.
Dude, that is so disheartening to hear.
Really hope they don't miss this in the next update.
I faced to this problem too. All my OpenGL applications slowed down by iOS11 Simulator after Xcode9 beta 4.
The reason is Simulator's OpenGL.framework which is contained in Xcode9.
I swaped the Simulator's OpenGL.framework with Xcode9 beta 3's OpenGL.framework.
All my OpenGL applications work as prevous now.
Hey, can you upload libCoreVMClient.dylib from Beta 3 somewhere? Thank you vey much!
An update. Still haven't solved things, but the problems I had creating the diagnose reports were because I hadn't run xcode-select to cause xcrun to reference the Xcode 9 installation.
I've been able to create a bug report now, #34737584.
Hi mixer555,
Here, you can get it.
https://www.dropbox.com/s/1bdyh86eo01x2em/libCoreVMClient.dylib?dl=0
When I replace that file with the one provided for download I get a "EXC_BAD_ACCESS (Code Signature Invalid)" upon launching the iPhone X Simulator.
You should be able to get it from developer.apple.com still.
Yes, we are aware. It's a top concern for us (and has been since it was originally reported about 2 months ago). Unfortunately, the OpenGL team did not get a fix in time for 9.1 Beta 1, but a fix for the performance issue will be available in an update soon.
It looks like you *copied* the file into place, which will cause it to keep the same inode. The new contents will fail to match the old signature. You can address this by using 'mv' instead of 'cp' or deleting the old file first. I suggest you just reboot to clear the cache.
Replacing the file helps, thanks! But Apple, please fix this in the Xcode 9.1 GM.
Where should I put the new libCoreVMClient.dylib?
This is probably because you have the wrong Xcode selected with xcode-select.