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

Question

I get the following messages in the Xcode console view

• libMobileGestalt MobileGestaltSupport.m: 153: pid 231 (myproject) does not have access to the sandbox for frZQaeyWLUvLjeuEK43hmg and is NOT properly titled

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

---

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

I get this message after starting the application, the device connects to xcode when the application starts. This seems like a rare issue. Can anyone help me solve this?

Answer 1

I had a similar problem:

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

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 the file on line 38277 from [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 there: rdar: // problem / 11744455 , and he pointed me in the right direction. In my case, this is due to the permissions of users to use their location:

I managed to solve the same problem for MKMapView. Apparently, this happens when the current permission status of your application does not match the name (declared in Info.plist). This effectively means that you need to call the APIs to collect user rights explicitly and proactively. (For example, LocationManager.requestWhenInUseAuthorization before displaying a map with the user's location on it)

Perhaps your situation is different. Nevertheless, there are many cases in this link.

Answer 2

I ran into the same problem, it turned out to be a multithreading issue.

Several threads accessed the same piece of data (more precisely, EAGLContext and some OpenGL materials) and probably messed up the memory. The problem disappeared after checking access synchronization.

Answer 3

Update # 1:

In addition, I found that the same message appeared in subsequent builds, but the failure was due to invalid Outlets in my storyboard that needed to be renamed or disconnected from the storyboard / controller: Terminating app due to uncaught exception 'NSUnknownKeyException',...

Original answer

In my case, I started to see this problem after adding Firebase modules to my application. After some debugging with a new stub, I fixed my problem by adding a custom URL scheme to enter my URL Types projects at the bottom of the info panel.

As indicated in the instructions:

• Copy value from REVERSED_CLIENT_ID from your GoogleService-Info.plist
• Click on your blue project file
• Go to the "Information" section of the project panel
• At the bottom of the Add New URL panel, enter and paste the copied text into the URL Schemes field

( Source , Google Instructions)

Answer 4

I get the same problem when trying to display GoogleMap using GMSMapView. but this is just a warning (I still don't know how to get rid of it). What I wanted to say is the display of the display of the Google map, and the functionality works fine with this warning. (I checked in iOS 10.3)

check if you are trying to display the map in the preview, there is a separate display method (this is a simple guide I found - http://www.ryanwright.me/cookbook/ios/obj-c/maps/gmap/subview )

otherwise try

self.view = gmsMapView;