使用企业证书部署存在 UI 差异

发布于 2024-12-05 19:05:38 字数 98 浏览 0 评论 0原文

与使用常规开发证书进行部署相比,使用企业证书部署 iOS 应用程序会缺少 UI 元素和/或属性差异。有人会知道为什么会发生这种情况吗?我已经确认一些图像没有被复制并与构建捆绑在一起。

Deploying an iOS application using an Enterprise certificate has UI elements missing, and/or attribute differences compared to deploying with a regular development certificate. Would anyone happen to know why this occurs? I have confirmed some images are not being copied and bundled with the build.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

灼疼热情 2024-12-12 19:05:38
  • 对于任何丢失的图像,请检查图像名称的大小写。
  • 完全重建您的应用程序(即“构建”->“清理”)。
  • 进行更全面的重建 - 删除“构建”和模拟器文件夹
  • 确保所有 NIB 和图像都包含在您的企业目标中
  • 尝试临时构建

XCode 本身可能有点不稳定。我注意到 4.1 中修复的一些内容在 4.0.2 中被破坏,尽管最新的测试版引入了自己的错误。除此之外,清除构建文件夹会迫使编译器重新开始 - 即,它会强制编译器以 IDE 无法处理的方式保持一致。

文件包含在项目导航器中并不意味着它将包含在您的项目中。选择文件并查看“实用程序”视图(XCode 的右侧窗格)中“文件检查器”选项卡的“目标成员资格”部分。

有些属性在 IB 中不起作用。 IB 可能有问题。另外,模拟器和设备之间存在一些差异;在设备上测试调试和临时构建可能会帮助您发现问题。

正如您所描述的那样,由于一些奇怪的行为,我有时不得不放弃发行版构建并从头开始。 Ad Hoc 构建是一种略有不同的发行版类型,因此创建新发行版可能会以某种方式绕过为企业配置设置的任何奇怪属性。

  • For any missing images, check the case of your image names.
  • Do a full rebuild of your app (ie Build->Clean).
  • Do a fuller rebuild - delete the "build" and simulator folders
  • Make sure all of your NIBs and images are included in your enterprise target
  • Try an Ad Hoc build

XCode itself can be a bit flaky. I've noticed some things fixed in 4.1 that are broken in 4.0.2, although the latest beta versions introduce their own bugs. That aside, blowing away the build folder forces the compiler to start over - ie, it forces the compiler to be consistent in ways that the IDE isn't written to handle.

Just because a file is included in the Project Navigator doesn't mean that it will be included in your project. Select the file and look in the "Target Membership" section of the File Inspector tab within the Utilities view (the right-side pane of XCode).

Some attributes don't work in IB. IB can be buggy. Plus there's some differences between the simulator and a device; testing a debug and ad hoc build on a device might help you uncover the issue.

I've sometimes had to blow away a distribution build and start over from scratch due to some weird behavior, like you're describing. An Ad Hoc build is a slightly different type of distribution, so creating a new distribution might somehow bypass whatever weird attribute got set for your Enterprise configuration.

鹿! 2024-12-12 19:05:38

如果您构建为存档或进行临时存档,请确保将发布版本的“跳过安装”属性设置为“是”(如果您使用的是静态链接库)。

如果没有这个,您使用静态链接库(即#defines)的任何地方都可能被忽略。

本文档解释了该过程的一部分:

http://developer.apple.com/library/mac/#documentation/ToolsLanguages/Conceptual/Xcode4UserGuide/DistApps/DistApps.html

If you build to Archive or do Ad Hoc to Archive, make sure that you set the Skip Install property to YES for Release builds, if you're using static linked libraries.

Without this, any place you're using static linked libraries (i.e. #defines) could potentially be ignored.

This documentation explains that part of the process:

http://developer.apple.com/library/mac/#documentation/ToolsLanguages/Conceptual/Xcode4UserGuide/DistApps/DistApps.html

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文