Xcode Error on Simulation: MGIsDeviceOneOfType is not supported on this platform












51















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).










share|improve this question




















  • 1





    You should've mentioned that you are using XCode 10 Beta. btw having the same issue

    – kironet
    Jun 8 '18 at 12:11













  • Are you trying to use AWS MobileHub?

    – Victor 'Chris' Cabral
    Jul 4 '18 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 '18 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 '18 at 21:37






  • 4





    Having this issue after Xcode 10 update (not beta)

    – MUH Mobile Inc.
    Sep 19 '18 at 18:47
















51















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).










share|improve this question




















  • 1





    You should've mentioned that you are using XCode 10 Beta. btw having the same issue

    – kironet
    Jun 8 '18 at 12:11













  • Are you trying to use AWS MobileHub?

    – Victor 'Chris' Cabral
    Jul 4 '18 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 '18 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 '18 at 21:37






  • 4





    Having this issue after Xcode 10 update (not beta)

    – MUH Mobile Inc.
    Sep 19 '18 at 18:47














51












51








51


9






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).










share|improve this question
















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 19 '18 at 11:11









Cœur

17.6k9105145




17.6k9105145










asked Jun 5 '18 at 13:27









WoodmanWoodman

4381511




4381511








  • 1





    You should've mentioned that you are using XCode 10 Beta. btw having the same issue

    – kironet
    Jun 8 '18 at 12:11













  • Are you trying to use AWS MobileHub?

    – Victor 'Chris' Cabral
    Jul 4 '18 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 '18 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 '18 at 21:37






  • 4





    Having this issue after Xcode 10 update (not beta)

    – MUH Mobile Inc.
    Sep 19 '18 at 18:47














  • 1





    You should've mentioned that you are using XCode 10 Beta. btw having the same issue

    – kironet
    Jun 8 '18 at 12:11













  • Are you trying to use AWS MobileHub?

    – Victor 'Chris' Cabral
    Jul 4 '18 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 '18 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 '18 at 21:37






  • 4





    Having this issue after Xcode 10 update (not beta)

    – MUH Mobile Inc.
    Sep 19 '18 at 18:47








1




1





You should've mentioned that you are using XCode 10 Beta. btw having the same issue

– kironet
Jun 8 '18 at 12:11







You should've mentioned that you are using XCode 10 Beta. btw having the same issue

– kironet
Jun 8 '18 at 12:11















Are you trying to use AWS MobileHub?

– Victor 'Chris' Cabral
Jul 4 '18 at 18:58





Are you trying to use AWS MobileHub?

– Victor 'Chris' Cabral
Jul 4 '18 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 '18 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 '18 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 '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 '18 at 21:37




4




4





Having this issue after Xcode 10 update (not beta)

– MUH Mobile Inc.
Sep 19 '18 at 18:47





Having this issue after Xcode 10 update (not beta)

– MUH Mobile Inc.
Sep 19 '18 at 18:47












13 Answers
13






active

oldest

votes


















9














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.






share|improve this answer





















  • 1





    This seems like a logical reason for the problem. What did you end up doing to fix the issue?

    – Brian Sachetta
    Oct 31 '18 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 '18 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
    Nov 19 '18 at 11:16





















8














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






share|improve this answer





















  • 21





    But I want to keep using Xcode 10....

    – ScottyBlades
    Sep 25 '18 at 4:37






  • 6





    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 '18 at 15:15



















5














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






share|improve this answer



















  • 3





    Mine was not private.

    – ScottyBlades
    Sep 25 '18 at 4:37











  • That was my issue. Thanks!

    – Felipe Peña
    Oct 25 '18 at 0:00



















3














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.






share|improve this answer































    2














    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.



    Changing the deployment target to fix libMobileGestalt error






    share|improve this answer































      1














      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.






      share|improve this answer































        1














        Am seeing this problem. Using Xcode 10.1. Created a brand new project - doesn't do anything except show a white screen. Discovered it was showing up on simulator for older devices. For example, iPad Pro (12.9 inch) and iPad Pro (12.9 inch) (2nd generation) show the problem, but problem is gone for iPad Pro (12.9 inch) (3rd generation). Does not show up for iPhone XR simulator.



        Basically seems annoying.






        share|improve this answer































          0














          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.






          share|improve this answer































            0














            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






            share|improve this answer

































              0














              The regular way when strange errors happens helped:



              1) Clean project;

              2) Shut down simulator;

              3) Reinstall pods.



              Xcode 10.






              share|improve this answer































                0














                What worked for me was to change within general > Deployment Info > Main Interface to CDVLaunchScreen and do the same within general > App Icons and Launch Images > Launch Screen File to CDVLaunchScreen as well.



                I come from Ionic, so this might not be a problem for those who develop in Swift / Objective-C.






                share|improve this answer
























                • How did you fixed it? I was also having the same problem. But this only happens when running it on production in ionic and after that I got stuck in the splash screen loader

                  – KnowledgeSeeker
                  17 hours ago



















                -2














                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.






                share|improve this answer































                  -3














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






                  share|improve this answer






















                    protected by Community Oct 14 '18 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?














                    13 Answers
                    13






                    active

                    oldest

                    votes








                    13 Answers
                    13






                    active

                    oldest

                    votes









                    active

                    oldest

                    votes






                    active

                    oldest

                    votes









                    9














                    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.






                    share|improve this answer





















                    • 1





                      This seems like a logical reason for the problem. What did you end up doing to fix the issue?

                      – Brian Sachetta
                      Oct 31 '18 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 '18 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
                      Nov 19 '18 at 11:16


















                    9














                    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.






                    share|improve this answer





















                    • 1





                      This seems like a logical reason for the problem. What did you end up doing to fix the issue?

                      – Brian Sachetta
                      Oct 31 '18 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 '18 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
                      Nov 19 '18 at 11:16
















                    9












                    9








                    9







                    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.






                    share|improve this answer















                    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.







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Oct 18 '18 at 13:59

























                    answered Oct 18 '18 at 12:35









                    tymactymac

                    7,91332236




                    7,91332236








                    • 1





                      This seems like a logical reason for the problem. What did you end up doing to fix the issue?

                      – Brian Sachetta
                      Oct 31 '18 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 '18 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
                      Nov 19 '18 at 11:16
















                    • 1





                      This seems like a logical reason for the problem. What did you end up doing to fix the issue?

                      – Brian Sachetta
                      Oct 31 '18 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 '18 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
                      Nov 19 '18 at 11:16










                    1




                    1





                    This seems like a logical reason for the problem. What did you end up doing to fix the issue?

                    – Brian Sachetta
                    Oct 31 '18 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 '18 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 '18 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 '18 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
                    Nov 19 '18 at 11:16







                    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
                    Nov 19 '18 at 11:16















                    8














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






                    share|improve this answer





















                    • 21





                      But I want to keep using Xcode 10....

                      – ScottyBlades
                      Sep 25 '18 at 4:37






                    • 6





                      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 '18 at 15:15
















                    8














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






                    share|improve this answer





















                    • 21





                      But I want to keep using Xcode 10....

                      – ScottyBlades
                      Sep 25 '18 at 4:37






                    • 6





                      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 '18 at 15:15














                    8












                    8








                    8







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






                    share|improve this answer















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







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Sep 21 '18 at 1:55









                    mokagio

                    8,19713242




                    8,19713242










                    answered Jun 20 '18 at 21:45









                    tjmistertjmister

                    1051




                    1051








                    • 21





                      But I want to keep using Xcode 10....

                      – ScottyBlades
                      Sep 25 '18 at 4:37






                    • 6





                      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 '18 at 15:15














                    • 21





                      But I want to keep using Xcode 10....

                      – ScottyBlades
                      Sep 25 '18 at 4:37






                    • 6





                      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 '18 at 15:15








                    21




                    21





                    But I want to keep using Xcode 10....

                    – ScottyBlades
                    Sep 25 '18 at 4:37





                    But I want to keep using Xcode 10....

                    – ScottyBlades
                    Sep 25 '18 at 4:37




                    6




                    6





                    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 '18 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 '18 at 15:15











                    5














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






                    share|improve this answer



















                    • 3





                      Mine was not private.

                      – ScottyBlades
                      Sep 25 '18 at 4:37











                    • That was my issue. Thanks!

                      – Felipe Peña
                      Oct 25 '18 at 0:00
















                    5














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






                    share|improve this answer



















                    • 3





                      Mine was not private.

                      – ScottyBlades
                      Sep 25 '18 at 4:37











                    • That was my issue. Thanks!

                      – Felipe Peña
                      Oct 25 '18 at 0:00














                    5












                    5








                    5







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






                    share|improve this answer













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







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Sep 13 '18 at 18:17









                    ankmaraankmara

                    112211




                    112211








                    • 3





                      Mine was not private.

                      – ScottyBlades
                      Sep 25 '18 at 4:37











                    • That was my issue. Thanks!

                      – Felipe Peña
                      Oct 25 '18 at 0:00














                    • 3





                      Mine was not private.

                      – ScottyBlades
                      Sep 25 '18 at 4:37











                    • That was my issue. Thanks!

                      – Felipe Peña
                      Oct 25 '18 at 0:00








                    3




                    3





                    Mine was not private.

                    – ScottyBlades
                    Sep 25 '18 at 4:37





                    Mine was not private.

                    – ScottyBlades
                    Sep 25 '18 at 4:37













                    That was my issue. Thanks!

                    – Felipe Peña
                    Oct 25 '18 at 0:00





                    That was my issue. Thanks!

                    – Felipe Peña
                    Oct 25 '18 at 0:00











                    3














                    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.






                    share|improve this answer




























                      3














                      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.






                      share|improve this answer


























                        3












                        3








                        3







                        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.






                        share|improve this answer













                        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.







                        share|improve this answer












                        share|improve this answer



                        share|improve this answer










                        answered Nov 23 '18 at 8:19









                        JhonnyTawkJhonnyTawk

                        1015




                        1015























                            2














                            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.



                            Changing the deployment target to fix libMobileGestalt error






                            share|improve this answer




























                              2














                              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.



                              Changing the deployment target to fix libMobileGestalt error






                              share|improve this answer


























                                2












                                2








                                2







                                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.



                                Changing the deployment target to fix libMobileGestalt error






                                share|improve this answer













                                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.



                                Changing the deployment target to fix libMobileGestalt error







                                share|improve this answer












                                share|improve this answer



                                share|improve this answer










                                answered Oct 17 '18 at 12:51









                                Bharathram CBharathram C

                                9126




                                9126























                                    1














                                    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.






                                    share|improve this answer




























                                      1














                                      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.






                                      share|improve this answer


























                                        1












                                        1








                                        1







                                        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.






                                        share|improve this answer













                                        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.







                                        share|improve this answer












                                        share|improve this answer



                                        share|improve this answer










                                        answered Oct 11 '18 at 8:17









                                        de.de.

                                        1,0391222




                                        1,0391222























                                            1














                                            Am seeing this problem. Using Xcode 10.1. Created a brand new project - doesn't do anything except show a white screen. Discovered it was showing up on simulator for older devices. For example, iPad Pro (12.9 inch) and iPad Pro (12.9 inch) (2nd generation) show the problem, but problem is gone for iPad Pro (12.9 inch) (3rd generation). Does not show up for iPhone XR simulator.



                                            Basically seems annoying.






                                            share|improve this answer




























                                              1














                                              Am seeing this problem. Using Xcode 10.1. Created a brand new project - doesn't do anything except show a white screen. Discovered it was showing up on simulator for older devices. For example, iPad Pro (12.9 inch) and iPad Pro (12.9 inch) (2nd generation) show the problem, but problem is gone for iPad Pro (12.9 inch) (3rd generation). Does not show up for iPhone XR simulator.



                                              Basically seems annoying.






                                              share|improve this answer


























                                                1












                                                1








                                                1







                                                Am seeing this problem. Using Xcode 10.1. Created a brand new project - doesn't do anything except show a white screen. Discovered it was showing up on simulator for older devices. For example, iPad Pro (12.9 inch) and iPad Pro (12.9 inch) (2nd generation) show the problem, but problem is gone for iPad Pro (12.9 inch) (3rd generation). Does not show up for iPhone XR simulator.



                                                Basically seems annoying.






                                                share|improve this answer













                                                Am seeing this problem. Using Xcode 10.1. Created a brand new project - doesn't do anything except show a white screen. Discovered it was showing up on simulator for older devices. For example, iPad Pro (12.9 inch) and iPad Pro (12.9 inch) (2nd generation) show the problem, but problem is gone for iPad Pro (12.9 inch) (3rd generation). Does not show up for iPhone XR simulator.



                                                Basically seems annoying.







                                                share|improve this answer












                                                share|improve this answer



                                                share|improve this answer










                                                answered Dec 15 '18 at 22:48









                                                anorskdevanorskdev

                                                1,1241813




                                                1,1241813























                                                    0














                                                    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.






                                                    share|improve this answer




























                                                      0














                                                      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.






                                                      share|improve this answer


























                                                        0












                                                        0








                                                        0







                                                        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.






                                                        share|improve this answer













                                                        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.







                                                        share|improve this answer












                                                        share|improve this answer



                                                        share|improve this answer










                                                        answered Sep 27 '18 at 16:39









                                                        StrudelStrudel

                                                        11




                                                        11























                                                            0














                                                            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






                                                            share|improve this answer






























                                                              0














                                                              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






                                                              share|improve this answer




























                                                                0












                                                                0








                                                                0







                                                                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






                                                                share|improve this answer















                                                                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







                                                                share|improve this answer














                                                                share|improve this answer



                                                                share|improve this answer








                                                                edited Oct 1 '18 at 20:36

























                                                                answered Oct 1 '18 at 20:30









                                                                Nuno FerroNuno Ferro

                                                                97499




                                                                97499























                                                                    0














                                                                    The regular way when strange errors happens helped:



                                                                    1) Clean project;

                                                                    2) Shut down simulator;

                                                                    3) Reinstall pods.



                                                                    Xcode 10.






                                                                    share|improve this answer




























                                                                      0














                                                                      The regular way when strange errors happens helped:



                                                                      1) Clean project;

                                                                      2) Shut down simulator;

                                                                      3) Reinstall pods.



                                                                      Xcode 10.






                                                                      share|improve this answer


























                                                                        0












                                                                        0








                                                                        0







                                                                        The regular way when strange errors happens helped:



                                                                        1) Clean project;

                                                                        2) Shut down simulator;

                                                                        3) Reinstall pods.



                                                                        Xcode 10.






                                                                        share|improve this answer













                                                                        The regular way when strange errors happens helped:



                                                                        1) Clean project;

                                                                        2) Shut down simulator;

                                                                        3) Reinstall pods.



                                                                        Xcode 10.







                                                                        share|improve this answer












                                                                        share|improve this answer



                                                                        share|improve this answer










                                                                        answered Dec 14 '18 at 19:44









                                                                        Nik KovNik Kov

                                                                        3,1622551




                                                                        3,1622551























                                                                            0














                                                                            What worked for me was to change within general > Deployment Info > Main Interface to CDVLaunchScreen and do the same within general > App Icons and Launch Images > Launch Screen File to CDVLaunchScreen as well.



                                                                            I come from Ionic, so this might not be a problem for those who develop in Swift / Objective-C.






                                                                            share|improve this answer
























                                                                            • How did you fixed it? I was also having the same problem. But this only happens when running it on production in ionic and after that I got stuck in the splash screen loader

                                                                              – KnowledgeSeeker
                                                                              17 hours ago
















                                                                            0














                                                                            What worked for me was to change within general > Deployment Info > Main Interface to CDVLaunchScreen and do the same within general > App Icons and Launch Images > Launch Screen File to CDVLaunchScreen as well.



                                                                            I come from Ionic, so this might not be a problem for those who develop in Swift / Objective-C.






                                                                            share|improve this answer
























                                                                            • How did you fixed it? I was also having the same problem. But this only happens when running it on production in ionic and after that I got stuck in the splash screen loader

                                                                              – KnowledgeSeeker
                                                                              17 hours ago














                                                                            0












                                                                            0








                                                                            0







                                                                            What worked for me was to change within general > Deployment Info > Main Interface to CDVLaunchScreen and do the same within general > App Icons and Launch Images > Launch Screen File to CDVLaunchScreen as well.



                                                                            I come from Ionic, so this might not be a problem for those who develop in Swift / Objective-C.






                                                                            share|improve this answer













                                                                            What worked for me was to change within general > Deployment Info > Main Interface to CDVLaunchScreen and do the same within general > App Icons and Launch Images > Launch Screen File to CDVLaunchScreen as well.



                                                                            I come from Ionic, so this might not be a problem for those who develop in Swift / Objective-C.







                                                                            share|improve this answer












                                                                            share|improve this answer



                                                                            share|improve this answer










                                                                            answered yesterday









                                                                            RaulGMRaulGM

                                                                            187416




                                                                            187416













                                                                            • How did you fixed it? I was also having the same problem. But this only happens when running it on production in ionic and after that I got stuck in the splash screen loader

                                                                              – KnowledgeSeeker
                                                                              17 hours ago



















                                                                            • How did you fixed it? I was also having the same problem. But this only happens when running it on production in ionic and after that I got stuck in the splash screen loader

                                                                              – KnowledgeSeeker
                                                                              17 hours ago

















                                                                            How did you fixed it? I was also having the same problem. But this only happens when running it on production in ionic and after that I got stuck in the splash screen loader

                                                                            – KnowledgeSeeker
                                                                            17 hours ago





                                                                            How did you fixed it? I was also having the same problem. But this only happens when running it on production in ionic and after that I got stuck in the splash screen loader

                                                                            – KnowledgeSeeker
                                                                            17 hours ago











                                                                            -2














                                                                            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.






                                                                            share|improve this answer




























                                                                              -2














                                                                              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.






                                                                              share|improve this answer


























                                                                                -2












                                                                                -2








                                                                                -2







                                                                                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.






                                                                                share|improve this answer













                                                                                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.







                                                                                share|improve this answer












                                                                                share|improve this answer



                                                                                share|improve this answer










                                                                                answered Nov 15 '18 at 23:45









                                                                                ThiagoAMThiagoAM

                                                                                37118




                                                                                37118























                                                                                    -3














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






                                                                                    share|improve this answer




























                                                                                      -3














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






                                                                                      share|improve this answer


























                                                                                        -3












                                                                                        -3








                                                                                        -3







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






                                                                                        share|improve this answer













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







                                                                                        share|improve this answer












                                                                                        share|improve this answer



                                                                                        share|improve this answer










                                                                                        answered Oct 31 '18 at 22:52









                                                                                        brainraybrainray

                                                                                        7,268850100




                                                                                        7,268850100

















                                                                                            protected by Community Oct 14 '18 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?



                                                                                            Popular posts from this blog

                                                                                            Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

                                                                                            ComboBox Display Member on multiple fields

                                                                                            Is it possible to collect Nectar points via Trainline?