运行模拟器时偶尔会出现涉及 Gatekeeper 的日志消息
我正在为 iPhone 开发一个应用程序。有时我会收到此日志：
未找到命名服务“com.apple.PersistentURLTranslator.Gatekeeper”。 assetd 已关闭或配置错误。事情不会按照你期望的方式进行。 10 月 4 日星期二 11:59:21 my-Mac-Pro.local[2958]：未找到命名服务“com.apple.assetsd.changehub”。 assetd 已关闭或配置错误。事情不会按照你期望的方式进行。
当我呈现模态 UIImagePickerController 时，就会发生这种情况，但并非每次都会发生。
有人有什么想法吗？
I am developing an app for iPhone. Sometimes I get this log :
Named service 'com.apple.PersistentURLTranslator.Gatekeeper' not found. assetsd is down or misconfigured. Things will not work the way you expect them to.
Tue Oct 4 11:59:21 my-Mac-Pro.local[2958] : Named service 'com.apple.assetsd.changehub' not found. assetsd is down or misconfigured. Things will not work the way you expect them to.
It is happening when I present a modal UIImagePickerController, but not every time.
Has anybody got any ideas?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我同意其他受访者的观点，即这是一个错误。
同时，解决方法是退出 iOS 模拟器并重新启动它。当我在不同设备之间交替测试时，我必须这样做。
I agree with the other respondents that this is a bug.
In the mean time, a work-around is to quit the iOS Simulator and restart it. I've had to do this as I alternate testing between different devices.
你可以尝试 Xcode 4.5 的测试版来看看这种行为是否存在吗？如果存在，我建议提交 Radars ： https:// /bugreport.apple.com
Can you try the beta of Xcode 4.5 to see if this behavior exists ... If it does, I suggest filing Radars : https://bugreport.apple.com
新的操作系统 Mountain Lion 有一个名为 Gatekeeper 的功能，该服务正在尝试运行该功能。我听说 Xcode 和新操作系统存在很多错误。我的猜测是，这是一个错误，一旦苹果推出更新和许多错误修复，可能就会得到解决。
The new os mountain lion has a feature called Gatekeeper that the service is trying to run through. What i have heard is that there are lots of bugs with Xcode and the new OS. My guess is that it is a bug and will probably be resolved once apple comes out with an update and many bug fixes.
同意这是一个错误。重新启动模拟器对我来说不起作用，但在我在模拟器中手动运行有问题的应用程序（而不是通过 Xcode 中的“运行”启动）后，我就很好了，随后能够正常使用“运行”。
Agree this is a bug. Relaunching simulator didn't work for me, but after I manually ran the app in question in simulator (as opposed to launching via 'Run' in Xcode) I was fine, and was subsequently able to use Run as normal.