MobileGestalt no access to InverseDeviceID

Question

This happens with every app when I try to use OpenGLES on my iPhone7+ with iOS10.3. But it works without any problems on my iPho

Answer 1

For those of you who are maybe using Ionic and getting this error, please just make sure that in case you've cloned a new fresh copy of the project from your repository that you did both npm install and bower install.

I was missing bower install and this was torturing me for like two days, so hope this helps someone. Sad thing is that I'm by all means not a beginner with Ionic (top #3 answerer on SO) but was still able to miss this fact so I hope that in case someone else runs into this problem it will help you.

Answer 2

This worked for me:

1. Create a new sandbox user in iTunesConnect. YES, you have to create a new iCloud user with a new email.
2. Log OUT your current iCloud user on your mac AND on the device you are testing on.
3. Log IN with your new iCloud user on your mac AND on the device you are testing on.
4. Run your app on your device again. This time it should work.

Hopefully Apple will come around and simplify this issue since this is a real pain in the ...

Answer 3

I had the same issue. It turns out to be multiple thread accessing the same OpenGLES related resource, EAGLContext to be specific. I guess it is possible that OpenGLES related codes are not thread-safe, and it behaves differently in different OS versions / iPhone 7 / 7+, sometimes it messes up the memory.

After making sure data accesses are synchronised across threads, the problem is gone.

Answer 4

I can see where the setting up of a sandbox account might do the trick, but if the device you are using is also connected to your normal icloud account, you can't create a sandbox with the same AppleID. You then have to log out of your existing icloud account, and log in with the new icloud (sandbox) useid. Which screws up your existing icloud device settings. So you are unable to use your Developer ID, only your Sandbox ID.

Answer 5

I had the same issue, and this point me in the right direction:

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)

Source: rdar://problem/11744455

Answer 6

I just had this issue when trying to use in-app-purchases.

Not sure if yours is the same issue, but I realised that you HAVE to create a Sandbox User in iTunes Connect, then log into iCloud on an iOS device with that user to enable the app to work.