blocks|key|724796|text|我也有过同样的问题。结果是访问同一个OpenGLES相关资源的多个线程，EAGLContext是特定的。我猜OpenGLES相关的代码可能不是线程安全的，在不同的OS版本/+iPhone+7/+7%2B中，它的行为也不同，有时会扰乱内存。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|724797|在确保数据访问跨线程同步之后，问题就解决了。|724798|entityMap^0|10|B|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

I had the same issue. It turns out to be multiple thread accessing the same OpenGLES related resource, <code>EAGLContext</code> 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.

blocks|key|724768|text|对于那些可能正在使用Ionic并得到此错误的人，请确保如果您已经从您的存储库中克隆了一个新的项目副本，即npm+install和bower+install。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|724769|我想念bower+install，这让我痛苦了两天，所以希望这能帮到别人。可悲的是，我绝不是一个使用Ionic的初学者(顶部#3回答)，但仍然能够错过这一事实，所以我希望，如果其他人遇到这个问题，它会帮助你。|724770|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/tags/ionic-framework/topusers^0|1G|B|1S|D|0|3|D|1O|4|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|H|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

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 <code>npm install</code> and <code>bower install</code>.

I was missing <code>bower install</code> 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 (<a href="https://stackoverflow.com/tags/ionic-framework/topusers">top #3</a> 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.

blocks|key|724866|text|Google地图显示和功能可以很好地处理此警告|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|724867|在这里核对我的答案：https://stackoverflow.com/a/44970665/3378076|724868|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/44970665/3378076^0|0|N|0|A|18|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@$9|T|A|U|1|V]]|E|$]]|$1|H|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

Google Map display and functionality works fine with this warning

Check my answer here:
<a href="https://stackoverflow.com/a/44970665/3378076">https://stackoverflow.com/a/44970665/3378076</a>

blocks|key|724621|text|我只是在尝试使用应用程序内采购时遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|724622|我不知道你的问题是否是同一个问题，但我意识到你必须在iTunes连接中创建一个沙盒用户，然后与该用户一起登录到iCloud设备上，以使应用程序能够工作。|724623|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

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.

blocks|key|724703|text|我可以看到沙箱帐户的设置可能在哪里起作用，但如果您正在使用的设备也连接到您的普通icloud帐户，则无法使用相同的AppleID创建沙箱。然后，您必须注销现有的icloud帐户，并使用新的icloud+(沙箱)+useid登录。这会破坏现有的icloud设备设置。因此，您无法使用您的开发人员ID，只使用您的沙箱ID。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|724704|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|2438332|text|这对我起了作用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2438333|在iTunesConnect中创建一个新的沙箱用户。是的，你必须用新的电子邮件创建一个新的iCloud用户。|ordered-list-item|2438334|在您的mac上和正在测试的设备上注销当前的iCloud用户。|2438335|在你的mac上和你正在测试的设备上与你的新iCloud用户登录。|2438336|再次在你的设备上运行你的应用程序。这一次应该管用。|2438337|希望苹果能来简化这个问题，因为这是一个真正的痛苦.|2438338|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|Q|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|R|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|S|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|T|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|N|$]]

This worked for me:

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

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

blocks|key|981953|text|我也有同样的问题，这点我的方向是正确的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|981954|我已经为MKMapView解决了同样的问题。显然，当应用程序的当前权限状态与标题(在Info.plist中声明)不对应时，就会发生这种情况。这意味着您需要调用API来显式和先发制人地收集用户权限。(例如，在地图上显示有用户位置的地图之前，请先使用LocationManager.requestWhenInUseAuthorization+)|blockquote|981955|来源：雷达://问题/11744455|offset|length|981956|entityMap|0|LINK|mutability|MUTABLE|url|http://www.openradar.me/11744455^0|0|0|3|G|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|S|8|@]|9|@$G|T|H|U|1|V]]|A|$]]|$1|I|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

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

<blockquote>
 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)
</blockquote>

Source: <a href="http://www.openradar.me/11744455" rel="nofollow noreferrer">rdar://problem/11744455</a>

blocks|key|2438498|text|我也有同样的问题。我的渲染程序是为了支持3版本的openglES(1，2和3)而编写的。在我的情况下，我意外地向基于openGLES2的呈现器类提供了openGLES2。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2438499|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had same issue. My rendering program was written to support 3 version of openglES(1, 2 and 3). On my case I was accidentally supplying <code>EAGLRenderingAPI.openGLES1 or kEAGLRenderingAPIOpenGLES1</code> to my renderer class based on openGLES2.

blocks|key|981505|text|我收到了这个控制台警告信息，因为多个苹果开发者帐户的问题。显然，您不能使用现有的Apple+Developer帐户拥有一个沙箱帐户。我没有尝试创建一个沙箱帐户，但它似乎检查了我的默认帐户，这也是一个旧的苹果开发帐户，我不使用，因此不再有权。这个问题已经被其他人多次报告给苹果，我还没有找到解决的办法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|981506|抑制此警告的解决方法是在方案设置中将OS_ACTIVITY_MODE环境变量设置为禁用。您可以单击应用程序名称，然后单击编辑方案.，或从顶部菜单中单击Product>Scheme->Edit.：|offset|length|style|BOLD|981507|​|981508|📷|atomic|981509|981510|然后编辑"Run“设置，并添加环境变量并将其设置为禁用。|981511|981512|981513|981514|注意：在提交应用程序之前，一定要将这个环境变量设置为启用，以便查看是否存在其他警告。在将应用程序提交到app之前，可能还有其他警告应该修复。|981515|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/6048d4731e3327b4e57797870c8d51db.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/9d5d2ecb1de68bca76f2bbd2767ba9ec.png^0|0|I|G|15|2|1O|5|23|L|0|0|0|1|0|0|0|5|3|P|2|0|0|0|1|1|0|0|0|2|Q|2|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@$D|17|E|18|F|G]|$D|19|E|1A|F|G]|$D|1B|E|1C|F|G]|$D|1D|E|1E|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1F|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1G|8|@]|9|@$D|1H|E|1I|1|1J]]|A|$]]|$1|M|3|I|5|6|7|1K|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1L|8|@$D|1M|E|1N|F|G]|$D|1O|E|1P|F|G]]|9|@]|A|$]]|$1|P|3|I|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|Q|3|K|5|L|7|1R|8|@]|9|@$D|1S|E|1T|1|1U]]|A|$]]|$1|R|3|I|5|6|7|1V|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1W|8|@$D|1X|E|1Y|F|G]|$D|1Z|E|20|F|G]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|21|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11|12|-4]]|13|$5|X|Y|Z|A|$10|14|12|-4]]]]

I got this console warning message because of issues with multiple Apple Developer accounts. Evidently you cannot have a sandbox account with an existing Apple Developer account. I didn't try to create a sandbox account but it seems to check my default account, which is also an old Apple Developer account that I don't use and hence is no longer entitled. This issue has been reported to Apple many times by other people and I have not yet seen a solution. 

My workaround to suppress this warning was to set the OS_ACTIVITY_MODE environment variable to disable in my scheme settings. You can click on the app name and then click Edit Scheme... or from the top menu you can click Product->Scheme->Edit Scheme... :

<img src="https://i.stack.imgur.com/otwVD.png" alt="Edit Scheme...">

Then you edit the "Run" settings and add the environment variable OS_ACTIVITY_MODE and set it to disable:

<img src="https://i.stack.imgur.com/90rUW.png" alt="Run Environment Variables">

NOTE: Be sure to set this environment variable to enable before you submit your app so that you can see if there are other warnings. There may be other warnings you should fix before you submit your app to the App Store.

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

This is the message I get:

<pre><code>libMobileGestalt MobileGestaltSupport.m:153: pid 304 (OpenGLES_Ch4_1) does not have sandbox access for ... and IS NOT appropriately entitled 
libMobileGestalt MobileGestalt.c:549: no access to InverseDeviceID 
</code></pre>

Does anyone have an idea about these messages? 

<hr>

I wonder if it is bugs or something else in <code>iOS10.3</code>? Because when I run the app on <code>iPhone5s</code> <code>iOS10.2</code>, those messages did not shown on the screen. While I upgraded the phone to <code>iOS10.3.1</code>, the massages shown again. 

The reason why I ask this question is that some animation effects perform quite stuck on my iPhone7+, but it is completely smooth on iPhone5s. But now it seems it is no relationship between the message above and the stuck, and I have to check my iPhone7+...

MobileGestalt no access to InverseDeviceID

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

当我尝试在iPhone7+上使用iPhone7+和iOS10.3时，每个应用程序都会出现这种情况。但它在我的iPhone7 iOS10.1上没有任何问题。这是我得到的信息：libMobileGestalt MobileGestaltSupport.m:153: pid 304 (OpenGLES_Ch4_1) does not have sandbox access for ... and IS 

问MobileGestalt不访问InverseDeviceID
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MobileGestalt不访问InverseDeviceIDEN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MobileGestalt不访问InverseDeviceID
EN