Mixing
Xcode Error on Simulation: MGIsDeviceOneOfType is not supported on this platform
up vote
36
down vote
favorite
I have a very simple application with a single view, containing several UILabels. Upon running a simulation, the Xcode console returns the error:
"libMobileGestalt MobileGestalt.c:875: MGIsDeviceOneOfType is not supported on this platform."
The simulator itself just shows a white screen. I've also tried running it on a developer device with the same white screen. I've searched documentation but can't find any reference to 'MGIsDeviceOneOfType'.
The application is written in Swift in Xcode 10 beta on macOS 10.14. I am attempting to run it on the iPhone 7-X simulators, as well as a development iPhone 7, all running the target software (12.0).
ios swift xcode
edited 2 days ago
Cœur
17k9102139
asked Jun 5 at 13:27
Woodman
3431311
|
show 3 more comments
up vote
36
down vote
favorite
I have a very simple application with a single view, containing several UILabels. Upon running a simulation, the Xcode console returns the error:
"libMobileGestalt MobileGestalt.c:875: MGIsDeviceOneOfType is not supported on this platform."
The simulator itself just shows a white screen. I've also tried running it on a developer device with the same white screen. I've searched documentation but can't find any reference to 'MGIsDeviceOneOfType'.
The application is written in Swift in Xcode 10 beta on macOS 10.14. I am attempting to run it on the iPhone 7-X simulators, as well as a development iPhone 7, all running the target software (12.0).
ios swift xcode
edited 2 days ago
Cœur
17k9102139
asked Jun 5 at 13:27
Woodman
3431311
1
You should've mentioned that you are using XCode 10 Beta. btw having the same issue
– kironet
Jun 8 at 12:11
Are you trying to use AWS MobileHub?
– Victor 'Chris' Cabral
Jul 4 at 18:58
I am having the exact same problem. As of the current, there is no obvious way of fixing this problem, after all, the simulator worked fine in the last version. Chances are, Apple are already working on a fix for this, so expect it to work in the next beta. It couldn't hurt to leave a bug report through the feedback app, however, in case Apple are not currently aware of the problem. Sorry I can not give you an actual answer, but I hope it was useful anyways. Thanks for your time, -Jack
– jackwellertk
Jul 21 at 12:53
2
Ran into this error in the debug console when running an instructor's key MVC design app. I am running Xcode 10 (not beta). Didn't get the error when running on actual device.
– Steve Robertson
Sep 18 at 21:37
3
Having this issue after Xcode 10 update (not beta)
– MUH Mobile Inc.
Sep 19 at 18:47
|
show 3 more comments
up vote
36
down vote
favorite
up vote
36
down vote
favorite
I have a very simple application with a single view, containing several UILabels. Upon running a simulation, the Xcode console returns the error:
"libMobileGestalt MobileGestalt.c:875: MGIsDeviceOneOfType is not supported on this platform."
The simulator itself just shows a white screen. I've also tried running it on a developer device with the same white screen. I've searched documentation but can't find any reference to 'MGIsDeviceOneOfType'.
The application is written in Swift in Xcode 10 beta on macOS 10.14. I am attempting to run it on the iPhone 7-X simulators, as well as a development iPhone 7, all running the target software (12.0).
ios swift xcode
edited 2 days ago
Cœur
17k9102139
asked Jun 5 at 13:27
Woodman
3431311
I have a very simple application with a single view, containing several UILabels. Upon running a simulation, the Xcode console returns the error:
"libMobileGestalt MobileGestalt.c:875: MGIsDeviceOneOfType is not supported on this platform."
The simulator itself just shows a white screen. I've also tried running it on a developer device with the same white screen. I've searched documentation but can't find any reference to 'MGIsDeviceOneOfType'.
The application is written in Swift in Xcode 10 beta on macOS 10.14. I am attempting to run it on the iPhone 7-X simulators, as well as a development iPhone 7, all running the target software (12.0).
ios swift xcode
ios swift xcode
edited 2 days ago
Cœur
17k9102139
asked Jun 5 at 13:27
Woodman
3431311
edited 2 days ago
Cœur
17k9102139
asked Jun 5 at 13:27
Woodman
3431311
edited 2 days ago
Cœur
17k9102139
edited 2 days ago
Cœur
17k9102139
edited 2 days ago
Cœur
17k9102139
17k9102139
asked Jun 5 at 13:27
Woodman
3431311
asked Jun 5 at 13:27
Woodman
3431311
asked Jun 5 at 13:27
Woodman
3431311
3431311
1
You should've mentioned that you are using XCode 10 Beta. btw having the same issue
– kironet
Jun 8 at 12:11
Are you trying to use AWS MobileHub?
– Victor 'Chris' Cabral
Jul 4 at 18:58
I am having the exact same problem. As of the current, there is no obvious way of fixing this problem, after all, the simulator worked fine in the last version. Chances are, Apple are already working on a fix for this, so expect it to work in the next beta. It couldn't hurt to leave a bug report through the feedback app, however, in case Apple are not currently aware of the problem. Sorry I can not give you an actual answer, but I hope it was useful anyways. Thanks for your time, -Jack
– jackwellertk
Jul 21 at 12:53
2
Ran into this error in the debug console when running an instructor's key MVC design app. I am running Xcode 10 (not beta). Didn't get the error when running on actual device.
– Steve Robertson
Sep 18 at 21:37
3
Having this issue after Xcode 10 update (not beta)
– MUH Mobile Inc.
Sep 19 at 18:47
|
show 3 more comments
1
You should've mentioned that you are using XCode 10 Beta. btw having the same issue
– kironet
Jun 8 at 12:11
Are you trying to use AWS MobileHub?
– Victor 'Chris' Cabral
Jul 4 at 18:58
I am having the exact same problem. As of the current, there is no obvious way of fixing this problem, after all, the simulator worked fine in the last version. Chances are, Apple are already working on a fix for this, so expect it to work in the next beta. It couldn't hurt to leave a bug report through the feedback app, however, in case Apple are not currently aware of the problem. Sorry I can not give you an actual answer, but I hope it was useful anyways. Thanks for your time, -Jack
– jackwellertk
Jul 21 at 12:53
2
Ran into this error in the debug console when running an instructor's key MVC design app. I am running Xcode 10 (not beta). Didn't get the error when running on actual device.
– Steve Robertson
Sep 18 at 21:37
3
Having this issue after Xcode 10 update (not beta)
– MUH Mobile Inc.
Sep 19 at 18:47
1
1
You should've mentioned that you are using XCode 10 Beta. btw having the same issue
– kironet
Jun 8 at 12:11
You should've mentioned that you are using XCode 10 Beta. btw having the same issue
– kironet
Jun 8 at 12:11
Are you trying to use AWS MobileHub?
– Victor 'Chris' Cabral
Jul 4 at 18:58
Are you trying to use AWS MobileHub?
– Victor 'Chris' Cabral
Jul 4 at 18:58
I am having the exact same problem. As of the current, there is no obvious way of fixing this problem, after all, the simulator worked fine in the last version. Chances are, Apple are already working on a fix for this, so expect it to work in the next beta. It couldn't hurt to leave a bug report through the feedback app, however, in case Apple are not currently aware of the problem. Sorry I can not give you an actual answer, but I hope it was useful anyways. Thanks for your time, -Jack
– jackwellertk
Jul 21 at 12:53
I am having the exact same problem. As of the current, there is no obvious way of fixing this problem, after all, the simulator worked fine in the last version. Chances are, Apple are already working on a fix for this, so expect it to work in the next beta. It couldn't hurt to leave a bug report through the feedback app, however, in case Apple are not currently aware of the problem. Sorry I can not give you an actual answer, but I hope it was useful anyways. Thanks for your time, -Jack
– jackwellertk
Jul 21 at 12:53
2
2
Ran into this error in the debug console when running an instructor's key MVC design app. I am running Xcode 10 (not beta). Didn't get the error when running on actual device.
– Steve Robertson
Sep 18 at 21:37
Ran into this error in the debug console when running an instructor's key MVC design app. I am running Xcode 10 (not beta). Didn't get the error when running on actual device.
– Steve Robertson
Sep 18 at 21:37
3
3
Having this issue after Xcode 10 update (not beta)
– MUH Mobile Inc.
Sep 19 at 18:47
Having this issue after Xcode 10 update (not beta)
– MUH Mobile Inc.
Sep 19 at 18:47
|
show 3 more comments
10 Answers
10
active
oldest
votes
up vote
7
down vote
I just installed Xcode 10 Beta and had the same problem. Ran Xcode 9.4.1 and the problem went away.
edited Sep 21 at 1:55
mokagio
7,96713142
answered Jun 20 at 21:45
tjmister
951
12
But I want to keep using Xcode 10....
– ScottyBlades
Sep 25 at 4:37
3
This is not a viable answer IMO, especially now that xcode 10 is in the wild and still has this issue. The problem didn't "go away" on xcode 9.4.1 - it never existed to begin with. It's one thing to say "unfortunately this is an xcode 10 issue and we might have to be patient." It's another to ignore it altogether.
– Brian Sachetta
Oct 31 at 15:15
add a comment |
up vote
4
down vote
in my case: check your app delegate for method - didFinishLaunching. I had private and get the error. After remove "private" everything works fine
answered Sep 13 at 18:17
ankmara
99111
1
Mine was not private.
– ScottyBlades
Sep 25 at 4:37
That was my issue. Thanks!
– Felipe Peña
Oct 25 at 0:00
add a comment |
up vote
4
down vote
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.
answered Oct 18 at 12:35
tymac
7,62731935
This seems like a logical reason for the problem. What did you end up doing to fix the issue?
– Brian Sachetta
Oct 31 at 16:05
1
As the very last sentence suggests. Make sure sim versions & Xcode versions are compatible or just use a real device.
– tymac
Nov 3 at 7:13
You wrote 200 or so queries, but apparently there are 673 known obfuscated keys. [edit: oh well, your name is "tymac" and the blog is from "timac" ... probably not a coincidence]
– Cœur
2 days ago
add a comment |
up vote
1
down vote
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.
answered Oct 11 at 8:17
de.
1,0091222
add a comment |
up vote
0
down vote
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.
answered Sep 27 at 16:39
Strudel
11
add a comment |
up vote
0
down vote
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
answered Oct 1 at 20:30
Nuno Ferro
97498
add a comment |
up vote
0
down vote
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.
answered Oct 17 at 12:51
Bharathram C
7126
add a comment |
up vote
-1
down vote
My solution was to download an earlier version of Xcode 9.4
https://developer.apple.com/downloads/index.action
answered Oct 28 at 19:08
Philip I
1144
Duplicate of top voted answer (by tjmister).
– Cœur
2 days ago
add a comment |
up vote
-1
down vote
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.
answered Nov 15 at 23:45
ThiagoAM
35318
add a comment |
up vote
-2
down vote
Pragmatic answer: try an other simulator. The newer the iPhone model the better.
answered Oct 31 at 22:52
brainray
7,22585099
add a comment |
protected by Community♦ Oct 14 at 5:09
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
10 Answers
10
active
oldest
votes
10 Answers
10
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
7
down vote
I just installed Xcode 10 Beta and had the same problem. Ran Xcode 9.4.1 and the problem went away.
edited Sep 21 at 1:55
mokagio
7,96713142
answered Jun 20 at 21:45
tjmister
951
12
But I want to keep using Xcode 10....
– ScottyBlades
Sep 25 at 4:37
3
This is not a viable answer IMO, especially now that xcode 10 is in the wild and still has this issue. The problem didn't "go away" on xcode 9.4.1 - it never existed to begin with. It's one thing to say "unfortunately this is an xcode 10 issue and we might have to be patient." It's another to ignore it altogether.
– Brian Sachetta
Oct 31 at 15:15
add a comment |
up vote
7
down vote
I just installed Xcode 10 Beta and had the same problem. Ran Xcode 9.4.1 and the problem went away.
edited Sep 21 at 1:55
mokagio
7,96713142
answered Jun 20 at 21:45
tjmister
951
12
But I want to keep using Xcode 10....
– ScottyBlades
Sep 25 at 4:37
3
This is not a viable answer IMO, especially now that xcode 10 is in the wild and still has this issue. The problem didn't "go away" on xcode 9.4.1 - it never existed to begin with. It's one thing to say "unfortunately this is an xcode 10 issue and we might have to be patient." It's another to ignore it altogether.
– Brian Sachetta
Oct 31 at 15:15
add a comment |
up vote
7
down vote
up vote
7
down vote
I just installed Xcode 10 Beta and had the same problem. Ran Xcode 9.4.1 and the problem went away.
edited Sep 21 at 1:55
mokagio
7,96713142
answered Jun 20 at 21:45
tjmister
951
I just installed Xcode 10 Beta and had the same problem. Ran Xcode 9.4.1 and the problem went away.
edited Sep 21 at 1:55
mokagio
7,96713142
answered Jun 20 at 21:45
tjmister
951
edited Sep 21 at 1:55
mokagio
7,96713142
edited Sep 21 at 1:55
mokagio
7,96713142
edited Sep 21 at 1:55
mokagio
7,96713142
7,96713142
answered Jun 20 at 21:45
tjmister
951
answered Jun 20 at 21:45
tjmister
951
answered Jun 20 at 21:45
tjmister
951
951
12
But I want to keep using Xcode 10....
– ScottyBlades
Sep 25 at 4:37
3
This is not a viable answer IMO, especially now that xcode 10 is in the wild and still has this issue. The problem didn't "go away" on xcode 9.4.1 - it never existed to begin with. It's one thing to say "unfortunately this is an xcode 10 issue and we might have to be patient." It's another to ignore it altogether.
– Brian Sachetta
Oct 31 at 15:15
add a comment |
12
But I want to keep using Xcode 10....
– ScottyBlades
Sep 25 at 4:37
3
This is not a viable answer IMO, especially now that xcode 10 is in the wild and still has this issue. The problem didn't "go away" on xcode 9.4.1 - it never existed to begin with. It's one thing to say "unfortunately this is an xcode 10 issue and we might have to be patient." It's another to ignore it altogether.
– Brian Sachetta
Oct 31 at 15:15
12
12
But I want to keep using Xcode 10....
– ScottyBlades
Sep 25 at 4:37
But I want to keep using Xcode 10....
– ScottyBlades
Sep 25 at 4:37
3
3
This is not a viable answer IMO, especially now that xcode 10 is in the wild and still has this issue. The problem didn't "go away" on xcode 9.4.1 - it never existed to begin with. It's one thing to say "unfortunately this is an xcode 10 issue and we might have to be patient." It's another to ignore it altogether.
– Brian Sachetta
Oct 31 at 15:15
This is not a viable answer IMO, especially now that xcode 10 is in the wild and still has this issue. The problem didn't "go away" on xcode 9.4.1 - it never existed to begin with. It's one thing to say "unfortunately this is an xcode 10 issue and we might have to be patient." It's another to ignore it altogether.
– Brian Sachetta
Oct 31 at 15:15
add a comment |
up vote
4
down vote
in my case: check your app delegate for method - didFinishLaunching. I had private and get the error. After remove "private" everything works fine
answered Sep 13 at 18:17
ankmara
99111
1
Mine was not private.
– ScottyBlades
Sep 25 at 4:37
That was my issue. Thanks!
– Felipe Peña
Oct 25 at 0:00
add a comment |
up vote
4
down vote
in my case: check your app delegate for method - didFinishLaunching. I had private and get the error. After remove "private" everything works fine
answered Sep 13 at 18:17
ankmara
99111
1
Mine was not private.
– ScottyBlades
Sep 25 at 4:37
That was my issue. Thanks!
– Felipe Peña
Oct 25 at 0:00
add a comment |
up vote
4
down vote
up vote
4
down vote
in my case: check your app delegate for method - didFinishLaunching. I had private and get the error. After remove "private" everything works fine
answered Sep 13 at 18:17
ankmara
99111
in my case: check your app delegate for method - didFinishLaunching. I had private and get the error. After remove "private" everything works fine
answered Sep 13 at 18:17
ankmara
99111
answered Sep 13 at 18:17
ankmara
99111
answered Sep 13 at 18:17
ankmara
99111
answered Sep 13 at 18:17
ankmara
99111
99111
1
Mine was not private.
– ScottyBlades
Sep 25 at 4:37
That was my issue. Thanks!
– Felipe Peña
Oct 25 at 0:00
add a comment |
1
Mine was not private.
– ScottyBlades
Sep 25 at 4:37
That was my issue. Thanks!
– Felipe Peña
Oct 25 at 0:00
1
1
Mine was not private.
– ScottyBlades
Sep 25 at 4:37
Mine was not private.
– ScottyBlades
Sep 25 at 4:37
That was my issue. Thanks!
– Felipe Peña
Oct 25 at 0:00
That was my issue. Thanks!
– Felipe Peña
Oct 25 at 0:00
add a comment |
up vote
4
down vote
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.
answered Oct 18 at 12:35
tymac
7,62731935
This seems like a logical reason for the problem. What did you end up doing to fix the issue?
– Brian Sachetta
Oct 31 at 16:05
1
As the very last sentence suggests. Make sure sim versions & Xcode versions are compatible or just use a real device.
– tymac
Nov 3 at 7:13
You wrote 200 or so queries, but apparently there are 673 known obfuscated keys. [edit: oh well, your name is "tymac" and the blog is from "timac" ... probably not a coincidence]
– Cœur
2 days ago
add a comment |
up vote
4
down vote
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.
answered Oct 18 at 12:35
tymac
7,62731935
This seems like a logical reason for the problem. What did you end up doing to fix the issue?
– Brian Sachetta
Oct 31 at 16:05
1
As the very last sentence suggests. Make sure sim versions & Xcode versions are compatible or just use a real device.
– tymac
Nov 3 at 7:13
You wrote 200 or so queries, but apparently there are 673 known obfuscated keys. [edit: oh well, your name is "tymac" and the blog is from "timac" ... probably not a coincidence]
– Cœur
2 days ago
add a comment |
up vote
4
down vote
up vote
4
down vote
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.
answered Oct 18 at 12:35
tymac
7,62731935
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.
answered Oct 18 at 12:35
tymac
7,62731935
edited Oct 18 at 13:59
answered Oct 18 at 12:35
tymac
7,62731935
answered Oct 18 at 12:35
tymac
7,62731935
answered Oct 18 at 12:35
tymac
7,62731935
7,62731935
This seems like a logical reason for the problem. What did you end up doing to fix the issue?
– Brian Sachetta
Oct 31 at 16:05
1
As the very last sentence suggests. Make sure sim versions & Xcode versions are compatible or just use a real device.
– tymac
Nov 3 at 7:13
You wrote 200 or so queries, but apparently there are 673 known obfuscated keys. [edit: oh well, your name is "tymac" and the blog is from "timac" ... probably not a coincidence]
– Cœur
2 days ago
add a comment |
This seems like a logical reason for the problem. What did you end up doing to fix the issue?
– Brian Sachetta
Oct 31 at 16:05
1
As the very last sentence suggests. Make sure sim versions & Xcode versions are compatible or just use a real device.
– tymac
Nov 3 at 7:13
You wrote 200 or so queries, but apparently there are 673 known obfuscated keys. [edit: oh well, your name is "tymac" and the blog is from "timac" ... probably not a coincidence]
– Cœur
2 days ago
This seems like a logical reason for the problem. What did you end up doing to fix the issue?
– Brian Sachetta
Oct 31 at 16:05
This seems like a logical reason for the problem. What did you end up doing to fix the issue?
– Brian Sachetta
Oct 31 at 16:05
1
1
As the very last sentence suggests. Make sure sim versions & Xcode versions are compatible or just use a real device.
– tymac
Nov 3 at 7:13
As the very last sentence suggests. Make sure sim versions & Xcode versions are compatible or just use a real device.
– tymac
Nov 3 at 7:13
You wrote 200 or so queries, but apparently there are 673 known obfuscated keys. [edit: oh well, your name is "tymac" and the blog is from "timac" ... probably not a coincidence]
– Cœur
2 days ago
You wrote 200 or so queries, but apparently there are 673 known obfuscated keys. [edit: oh well, your name is "tymac" and the blog is from "timac" ... probably not a coincidence]
– Cœur
2 days ago
add a comment |
up vote
1
down vote
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.
answered Oct 11 at 8:17
de.
1,0091222
add a comment |
up vote
1
down vote
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.
answered Oct 11 at 8:17
de.
1,0091222
add a comment |
up vote
1
down vote
up vote
1
down vote
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.
answered Oct 11 at 8:17
de.
1,0091222
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.
answered Oct 11 at 8:17
de.
1,0091222
answered Oct 11 at 8:17
de.
1,0091222
answered Oct 11 at 8:17
de.
1,0091222
answered Oct 11 at 8:17
de.
1,0091222
1,0091222
add a comment |
add a comment |
up vote
0
down vote
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.
answered Sep 27 at 16:39
Strudel
11
add a comment |
up vote
0
down vote
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.
answered Sep 27 at 16:39
Strudel
11
add a comment |
up vote
0
down vote
up vote
0
down vote
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.
answered Sep 27 at 16:39
Strudel
11
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.
answered Sep 27 at 16:39
Strudel
11
answered Sep 27 at 16:39
Strudel
11
answered Sep 27 at 16:39
Strudel
11
answered Sep 27 at 16:39
Strudel
11
11
add a comment |
add a comment |
up vote
0
down vote
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
answered Oct 1 at 20:30
Nuno Ferro
97498
add a comment |
up vote
0
down vote
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
answered Oct 1 at 20:30
Nuno Ferro
97498
add a comment |
up vote
0
down vote
up vote
0
down vote
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
answered Oct 1 at 20:30
Nuno Ferro
97498
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
answered Oct 1 at 20:30
Nuno Ferro
97498
edited Oct 1 at 20:36
answered Oct 1 at 20:30
Nuno Ferro
97498
answered Oct 1 at 20:30
Nuno Ferro
97498
answered Oct 1 at 20:30
Nuno Ferro
97498
97498
add a comment |
add a comment |
up vote
0
down vote
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.
answered Oct 17 at 12:51
Bharathram C
7126
add a comment |
up vote
0
down vote
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.
answered Oct 17 at 12:51
Bharathram C
7126
add a comment |
up vote
0
down vote
up vote
0
down vote
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.
answered Oct 17 at 12:51
Bharathram C
7126
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.
answered Oct 17 at 12:51
Bharathram C
7126
answered Oct 17 at 12:51
Bharathram C
7126
answered Oct 17 at 12:51
Bharathram C
7126
answered Oct 17 at 12:51
Bharathram C
7126
7126
add a comment |
add a comment |
up vote
-1
down vote
My solution was to download an earlier version of Xcode 9.4
https://developer.apple.com/downloads/index.action
answered Oct 28 at 19:08
Philip I
1144
Duplicate of top voted answer (by tjmister).
– Cœur
2 days ago
add a comment |
up vote
-1
down vote
My solution was to download an earlier version of Xcode 9.4
https://developer.apple.com/downloads/index.action
answered Oct 28 at 19:08
Philip I
1144
Duplicate of top voted answer (by tjmister).
– Cœur
2 days ago
add a comment |
up vote
-1
down vote
up vote
-1
down vote
My solution was to download an earlier version of Xcode 9.4
https://developer.apple.com/downloads/index.action
answered Oct 28 at 19:08
Philip I
1144
My solution was to download an earlier version of Xcode 9.4
https://developer.apple.com/downloads/index.action
answered Oct 28 at 19:08
Philip I
1144
answered Oct 28 at 19:08
Philip I
1144
answered Oct 28 at 19:08
Philip I
1144
answered Oct 28 at 19:08
Philip I
1144
1144
Duplicate of top voted answer (by tjmister).
– Cœur
2 days ago
add a comment |
Duplicate of top voted answer (by tjmister).
– Cœur
2 days ago
Duplicate of top voted answer (by tjmister).
– Cœur
2 days ago
Duplicate of top voted answer (by tjmister).
– Cœur
2 days ago
add a comment |
up vote
-1
down vote
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.
answered Nov 15 at 23:45
ThiagoAM
35318
add a comment |
up vote
-1
down vote
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.
answered Nov 15 at 23:45
ThiagoAM
35318
add a comment |
up vote
-1
down vote
up vote
-1
down vote
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.
answered Nov 15 at 23:45
ThiagoAM
35318
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.
answered Nov 15 at 23:45
ThiagoAM
35318
answered Nov 15 at 23:45
ThiagoAM
35318
answered Nov 15 at 23:45
ThiagoAM
35318
answered Nov 15 at 23:45
ThiagoAM
35318
35318
add a comment |
add a comment |
up vote
-2
down vote
Pragmatic answer: try an other simulator. The newer the iPhone model the better.
answered Oct 31 at 22:52
brainray
7,22585099
add a comment |
up vote
-2
down vote
Pragmatic answer: try an other simulator. The newer the iPhone model the better.
answered Oct 31 at 22:52
brainray
7,22585099
add a comment |
up vote
-2
down vote
up vote
-2
down vote
Pragmatic answer: try an other simulator. The newer the iPhone model the better.
answered Oct 31 at 22:52
brainray
7,22585099
Pragmatic answer: try an other simulator. The newer the iPhone model the better.
answered Oct 31 at 22:52
brainray
7,22585099
answered Oct 31 at 22:52
brainray
7,22585099
answered Oct 31 at 22:52
brainray
7,22585099
answered Oct 31 at 22:52
brainray
7,22585099
7,22585099
add a comment |
add a comment |
protected by Community♦ Oct 14 at 5:09
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
1
You should've mentioned that you are using XCode 10 Beta. btw having the same issue
– kironet
Jun 8 at 12:11
Are you trying to use AWS MobileHub?
– Victor 'Chris' Cabral
Jul 4 at 18:58
I am having the exact same problem. As of the current, there is no obvious way of fixing this problem, after all, the simulator worked fine in the last version. Chances are, Apple are already working on a fix for this, so expect it to work in the next beta. It couldn't hurt to leave a bug report through the feedback app, however, in case Apple are not currently aware of the problem. Sorry I can not give you an actual answer, but I hope it was useful anyways. Thanks for your time, -Jack
– jackwellertk
Jul 21 at 12:53
2
Ran into this error in the debug console when running an instructor's key MVC design app. I am running Xcode 10 (not beta). Didn't get the error when running on actual device.
– Steve Robertson
Sep 18 at 21:37
3
Having this issue after Xcode 10 update (not beta)
– MUH Mobile Inc.
Sep 19 at 18:47