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

后端 未结 18 1970
执笔经年
执笔经年 2020-12-02 10:55

I have a very simple application with a single view, containing several UILabels. Upon running in Simulator, the Xcode console returns the error:

libM

相关标签:
18条回答
  • 2020-12-02 11:19

    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.

    0 讨论(0)
  • 2020-12-02 11:22

    I've successfully dropped it with the disabling of the project garbage.

    Go to <Name of your Project>->Scheme->Edit Scheme Then go to Run (menu to the left side) and add the following environment variable:

    Name:OS_ACTIVITY_MODE, Value: disable

    0 讨论(0)
  • 2020-12-02 11:25

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

    0 讨论(0)
  • 2020-12-02 11:26

    I have recently updated to Xcode 10.2 and when I tried to run a project created in earlier version, Same error occurred.

    The problem was that simulator was running before updating Xcode.

    Solution was very simple for me to quit Simulator and restart so that it can get the new changes. I don't think the model of the simulator (iPhone SE or iPhone X) matters. You just need to restart your simulator for it to take effect of new update.

    I would recommend to quit both Xcode and simulator and restart your Mac.

    0 讨论(0)
  • 2020-12-02 11:27

    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.

    0 讨论(0)
  • 2020-12-02 11:30

    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.

    0 讨论(0)
提交回复
热议问题