为什么我的应用程序图标在临时安装后消失 (iPhone)
我有一个正在尝试通过标准 OTA 即席安装的应用程序。在 iOS 4.1 上应用程序安装正常。在较新的版本（已测试 4.3.1 和 4.3.3）上，应用程序安装时不会出现错误，但安装完成后图标会从 Springboard 中消失。如果我重新启动设备，图标就会回来。
我有两个问题：
- 有谁知道导致这种行为的原因是什么？
- 这是应用程序的问题吗 商店提交？
编辑：消失的是整个图标，而不仅仅是图形。无法从 Springboard 启动应用程序。
I have an app that I'm trying to install via standard OTA ad hoc. On iOS 4.1 The app installs ok. On newer versions (4.3.1 and 4.3.3 tested) the app installs without error, but the icon disappears from Springboard when the install is done. If I restart the device the icon is back.
I have two questions:
- Does anyone know what causes this behaviour?
- Is this a problem when it comes to App
Store submission?
Edit: It's the whole icon that disappears, not just the graphics. It is not possible to start the app from Springboard.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我认为这个问题与这个问题类似：
安装后内部应用程序消失
尝试一下，也许会有帮助...
I think this question is similar to this one:
In-House App Disappears After Install
Give it a try, maybe it helps...
刚刚花了几个小时解决同样的问题。
我们通过无线方式提供AdHoc构建。
事实证明，当我更改应用ID时，我没有更改OTA安装plist中的bundle-identifier参数。
Just spent hours sorting out the same problem.
We deliver our AdHoc build over-the-air.
Turns out that when I changed app ID, I didn't change the bundle-identifier parameter in the OTA installation plist.
您可能需要检查高分辨率和标准分辨率图标文件是否已正确输入到 info.plist 文件中。
在旧版本的 iOS 上，只需为“图标文件”键输入标准分辨率文件名就足够了，iOS 只需在文件名中添加 @2x 即可选择高分辨率文件。
在较新的版本中，有“图标文件”（注意复数形式）数组，您可以在其中输入不同分辨率的多个文件。我使用“旧”样式遇到了类似的错误，但使用新样式解决了这些错误。
You might want to check that both high and standard resolution icon files are entered correctly into the info.plist file.
On older versions of iOS, entering just the standard resolution file name for the "Icon File" Key was sufficient, iOS would select the high resolution file by just adding @2x to the filename.
On newer versions there is the "Icon Files" (note the plural form) Array, where you may enter several files in different resolutions. I experienced similar errors using the "old" style, which were resolved using the new one.
我遇到了这个问题，问题是我们的分发/配置证书在创建 ipa 和将其安装到设备上之间都已过期。更新所有证书、重建和重新部署解决了问题。
I had this issue and the problem was that our distribution/provisioning certificates had all expired in between when the ipa was created and when it was installed on the device. Renewing all the certificates, rebuilding and redeploying fixed the problem.