Nsryjdtyk

I just installed Xcode 10 Beta and had the same problem. Ran Xcode 9.4.1 and the problem went away.

MobileGestalt

The libMobileGestalt.dylib provides a central repository for all of the iOS's properties. It can be analogous to OS X's Gestalt, which is part of CoreServices. OS X's Gestalt is documented for example Gestalt Manager and has been deprecated as of 10.8. MobileGestalt is entirely undocumented by Apple as it is a private library.

MobileGestalt allows for the testing of system properties that may or may not be compatible on different simulators.

Quite a few system processes and apps in iOS rely on MobileGestalt, which is located at /usr/lib/libMobileGestalt.dylib. It's more of a basic library, but its exposed APIs follow the Apple framework conventions and uses the MG API prefix for example MGIsDeviceOneOfType.

If you look for MobileGestalt on the iOS filesystem you won't find it - like all private frameworks and libraries, it has been prelinked into the /System/Library/Caches/...etc. If you like hacking and pen-testing then you can use tools to extract it.

MobileGestalt provides plenty of information - around 200 or so queries - on various aspects of the system. Here are a few.

libMobileGestalt.dylib

//Answers to MG queries



MGCopyAnswer(@"5MSZn7w3nnJp22VbpqaxLQ");

MGCopyAnswer(@"7mV26K/1a+wTtqiunvHMUQ");

MGCopyAnswer(@"BasebandAPTimeSync");

MGCopyAnswer(@"BasebandPostponementStatus");

MGCopyAnswer(@"BasebandPostponementStatusBlob");

MGCopyAnswer(@"BasebandSecurityInfoBlob");

MGCopyAnswer(@"BasebandStatus");

MGCopyAnswer(@"BuildVersion");

MGCopyAnswer(@"CoreRoutineCapability");

MGCopyAnswer(@"DeviceClass");

MGCopyAnswer(@"DeviceClassNumber");

MGCopyAnswer(@"DeviceName");

MGCopyAnswer(@"DeviceSupports1080p");

MGCopyAnswer(@"DeviceSupports720p");

MGCopyAnswer(@"DiskUsage");

MGCopyAnswer(@"GSDeviceName");

MGCopyAnswer(@"HWModelStr");

MGCopyAnswer(@"HasBaseband");

MGCopyAnswer(@"InternalBuild");

MGCopyAnswer(@"InverseDeviceID");

MGCopyAnswer(@"IsSimulator");

MGCopyAnswer(@"MLBSerialNumber");

MGCopyAnswer(@"MaxH264PlaybackLevel");

MGCopyAnswer(@"MinimumSupportediTunesVersion");

MGCopyAnswer(@"PasswordConfigured");

MGCopyAnswer(@"PasswordProtected");

MGCopyAnswer(@"ProductType");

MGCopyAnswer(@"ProductVersion");

MGCopyAnswer(@"RegionCode");

MGCopyAnswer(@"RegionalBehaviorNTSC");

MGCopyAnswer(@"RegionalBehaviorNoPasscodeLocationTiles");

MGCopyAnswer(@"ReleaseType");

MGCopyAnswer(@"SIMStatus");

There are hundreds more e.g. AirplaneMode, MobileEquipmentIdentifier, etc.

MobileGestalt maintains a table of OSType selector codes.
for example c:890 in the message: libMobileGestalt MobileGestalt.c:890: MGIsDeviceOneOfType is not supported on this platform. In this case MGIsDeviceOneOfType is a method of the MobileGestalt library.

Instead of checking the simulator version there is a separate selector for directly querying the capabilities of the simulator. The messages we are seeing indicate incompatibilities between simulator versions and Xcode versions.

in my case: check your app delegate for method - didFinishLaunching. I had private and get the error. After remove "private" everything works fine

Ran into this when opening some project from GitHub on Xcode 10.0.

The pragmatic solution was: just hit 'Continue program execution' multiple times and probably disable your exception breakpoint. Apparently the exception was recoverable.

It's not a real solution but it was good enough for me at that point.

I had the same issue, but with MapKit, where a MapView did not show up, just the white screen and the same error, MGIsDeviceOneOfType is not supported on this platform.

Solved it by fixing "Ambiguous layout" warnings tied to the MapView object. Now it's working perfectly fine, and the errors went away.

If you have fonts provided by the app, you need to add to Info.plist
And check if the file have the Target Membership selected

In my case, the Target's Deployment Target was at iOS 8. When I pushed it up to iOS 10.3, it ran fine, both on the Simulator and the device.

This error will only occur when testing/debugging on simulators.

The newer the simulator the better.

Case: I run simulator iPhone 8 plus I got this message in the debugger.

Solution: I changed to a newer simulator no error message in the debugger.

My solution was to download an earlier version of Xcode 9.4
https://developer.apple.com/downloads/index.action

I was having that exact same problem with Xcode 10.1 and simulator on iOS 12.1. Turns out it was being caused by a recursion causing an infinite loop.

Pragmatic answer: try an other simulator. The newer the iPhone model the better.