Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Deysha Rivera
5,088 PointsError on Xcode 10 building Fun Facts App
In my output section I am seeing this error pop up. I am following instructions and running the simulator as iPhone 6s; however, it is not an option for "view as." It is being viewed as iPhone 8. I still get the error if I run the simulator as iPhone 8. There are a lot of differences with Xcode 10 and it's been slowing me down a lot when following the videos.
2018-12-17 15:18:35.831752-0500 FunFacts[21835:13828952] libMobileGestalt MobileGestalt.c:890: MGIsDeviceOneOfType is not supported on this platform.
Any thoughts?
Deysha Rivera
5,088 PointsI should clarify this error shows in the debug console. If I change the simulation to iPhone XR, the error goes away. I don't think Xcode wants to play with iPhone 6s anymore (what's instructed in the video).
3 Answers
Matt Brody
2,041 PointsDid anyone ever get an answer for this? I'm getting this error even if I switch to iPhone Xr
Deysha Rivera
5,088 PointsI have just been running simulations in iPhone XR. You might try copying your code, deleting and pasting back in to see if it refreshes its atttude.
Matt Brody
2,041 PointsThanks for responding Deysha. I was able to solve it by uninstalling and installing a earlier version of Swift 9
Clark Reilly
6,204 PointsClark Reilly
6,204 PointsOh dear, the libMobileGestalt error... I'd like to know what causes that, too. All I can say is it happened to me once, then I just fudged around a bit and it went away. No idea what I did or why. I think it had something to do with the interaction between the viewController and IB, but I'm not sure.