在 Xcode 中构建存档不会创建存档
看来我所有的搜索都没有结果。了解我，这是我错过的一个愚蠢的复选框或下拉菜单。可能是我的安装问题？我需要卸载 Xcode 4 并重新安装吗？
我已经在网上和 SO 上完成了所有这些步骤、技巧和修复，但没有什么能让我更接近在我的管理器中弹出存档。当我查看构建的存档时，它只是一个零 k 文件。我构建成功，我将跳过安装更改为是和否......我做了我在网上找到的所有这些事情，我快疯了。我很确定我的证书都设置正确，我在被告知要检查的地方检查了一些东西。这让我发疯。我看到的 99％ 的解决方案是：
“无论如何，在“跳过安装”中，将“发布”的值设置为“否”（帮助文档告诉你相反的）。一旦将其设置为“否”，存档您将立即看到您的应用程序出现在存档管理器中。”
好吧，它不起作用，或者之后的任何进一步的答案也不起作用。
It seems all my searches to figure this out are fruitless. Knowing me it's one stupid checkbox or pulldown I'm missing. Is it maybe my install? Do I need to uninstall Xcode 4 and reinstall?
I've gone through all these steps and tricks and fixes all over the net and on SO, yet nothing gets me closer to getting an archive to pop up in my organizer. When I go to look at the archive that was built, it's just a zero k file. I get a build succeed, I change skip install to both yes and no ... I do all these things I find on the net, I'm going crazy. I'm pretty sure my certificates are all set up correctly, I have things checked where I'm told to be checked. It's driving me crazy. 99% of the solutions I see are:
"Anyway, in the "Skip Install", set the value for "Release" as "NO" (the help doc told you the opposite). Once you set it to "NO", archive again. You'll immediately see your app showing up in the archive organizer."
Well, it's not working or any further answers after aren't either.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
Archive似乎只包含那些设置为“安装”的构建产品，因此请确保在构建设置中停用Skip Install：此外，Xcode 需要一个
安装路径。对于应用程序，这通常是/Applications，但是当例如构建插件时，您可能希望将其设置为/，这会将构建产品放在存档的根目录中。请注意，您必须使用“真实”路径，而不是像~/Library这样的相对路径。Archiveonly seems to include those build products that are set to be "installed", so make sure that you deactivateSkip Installin your build settings:Additionally, Xcode needs an
Install Path. For Applications this is usually/Applications, but when e.g. building a plugin you might want to set this to just/, which will put the build product in the root of your archive. Note that you must use a "real" path, not a relative one like~/Library.确保您使用“产品”>“存档，而不是产品>构建>档案。
Make sure you use Product > Archive, instead of Product > Build For > Archive.
我更新到 High Sierra 后遇到了这个问题。我转到我的库文件夹。 /用户/your_user/Library/Developer/Xcode/Archives
该文件夹中有一个空文件夹，以我创建此存档的日期命名。但文件夹是空的。我删除了该文件夹并再次存档。这为我解决了这个问题。
I had this issue after I updated to High Sierra. I went to my library folder. /Users/your_user/Library/Developer/Xcode/Archives
In this folder was an empty folder named to the date I had created this archive. But the folder was empty. I removed the folder and archived again. That fixed the issue for me.
对我来说，我还必须将以下空白构建设置更改为...
最后，它开始出现在组织者/档案中。
PS 有趣的是，如果没有此设置，则会创建旧的存档文件，但它始终是空的。
For me, I had to also change the following blank build setting, to something like...
Finally, it started appearing in Organizer/Archives.
P.S. Interestingly, without this setting the old archive file was being created, but it was always empty.
我刚刚遇到了这个问题，为我解决的方法是：
希望这会有所帮助（比上面#1 更有帮助）。
I just had this issue and what resolved it for me was this:
Hope this helps (more that #1 above helps).
通过此清单，您应该在某处找到答案：
如果问题仍然存在，则应删除所有配置、吊销所有证书、重新颁发所有证书，然后重新安装所有证书。之后尝试重置代码签名，如果仍然不起作用，请使用 Apple 开发支持为您提供的两个免费 TSI 之一。如果没有任何效果，我相信他们可以为您解决。
希望这有帮助。
Go through this checklist, and you should find an answer somewhere:
If you are still having problems, you should delete all of your provisioning, revoke all of your certificates, reissue them all, and reinstall them all. Try resetting your code signing after that, and if it still doesn't work, use one of your two free TSIs given to you by Apple Dev Support. If nothing works, they can fix it for you I'm sure.
Hope this helps.
我做了以下工作以使其对我有用：
绝对路径更改到产品目录。就是这样！
提示：要了解导致存档创建存档文件而不是 ipa 的违规文件，请执行以下操作：
usr/local/include将识别您需要从公共移动到项目的罪魁祸首文件，或者您必须从绝对路径更改为产品目录的文件。但该目录（即 usr/local/include）根据您的子库目录结构而有所不同I did the following to make it work for me:
Absolute pathtoproducts directory.and that was it!
hint: to get an idea of the offending files that's causing your archive to create an archive file rather than an ipa do this:
usr/local/includewill identify the culprit header files you need to move from Public to Project or the files that you have to change from absolute path to products directory. but that directory (ie usr/local/include) varies depending on your sublibrary directory structure