libMobileGestalt MobileGestaltSupport.m:153 MobileGestalt.c:550 Xcode Console

Question

I am getting Following messages on Xcode Console View

• libMobileGestalt MobileGestaltSupport.m:153: pid 231 (myproject) does not have sandbox access for frZQaeyWLUvLjeuEK43hmg and IS NOT appropriately entitled

• libMobileGestalt MobileGestalt.c:550: no access to InverseDeviceID (see )

---

MacOs Sierra Version: 10.12.4 Xcode Version 8.3 Programming Language : Objective C

I get this message after application launch, Device is plugged with xcode while running the application. It seems like a rare issue. Anyone can help me to solve this?

Answer 1

I had a similar issue:

2017-08-04 12:02:44.936288+0100 Demos[1112:472604] libMobileGestalt MobileGestaltSupport.m:153: pid 1112 (Demos) does not have sandbox access for frZQaeyWLUvLjeuEK43hmg and IS NOT appropriately entitled

2017-08-04 12:02:44.936524+0100 Demos[1112:472604] libMobileGestalt MobileGestalt.c:550: no access to InverseDeviceID (see )

2017-08-04 12:02:44.970997+0100 Demos[1112:472749] [INFO] {DefaultFileSource}[Database]: cannot open file at line 38277 of [0e5ffd9123] (Code 14)

2017-08-04 12:02:44.971157+0100 Demos[1112:472749] [INFO] {DefaultFileSource}[Database]: [0e5ffd9123]:38277: (0) open(/var/mobile/Containers/Data/Application/735DAEF4-D6F0-4565-A89E-4FA3A377485B/Library/Application Support/navenio.Demos/.mapbox/cache.db) - (Code 14)

Finally I followed the link indicated there: rdar://problem/11744455 and it pointed me in the right direction. In my case, it had to do with user's permissions to use their location:

I've managed to solve the same problem for MKMapView. Apparently, that happens when your app's current permissions state doesn't correspond to entitled (declared in Info.plist) one. That effecively means that you need to call APIs to gather user's permissions explicitly and preemptively. (E.g. LocationManager.requestWhenInUseAuthorization before displaying a map with user location on it)

Maybe your situation is different. But still ,there's a bunch of cases covered in that link.

Answer 2

I came across the same issue, it turns out to be issue with multithreading.

Multiple threads was accessing the same piece of data (to be exact, EAGLContext, and some OpenGL stuffs) and probably messed up the memory. The issue is gone after making sure accesses are synchronised.