XCode 4.3.1破坏了通过引用添加目录的应用程序的验证。任何解决方法? [英] XCode 4.3.1 breaks validation of apps with directories added by reference. Any workaround?

查看:73
本文介绍了XCode 4.3.1破坏了通过引用添加目录的应用程序的验证。任何解决方法?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我发现Xcode 4.3.1在使用应用程序捆绑包内的目录树中的资源验证应用程序时存在严重问题。

I've discovered that Xcode 4.3.1 has a serious issue validating apps with resources within a directory tree inside an application bundle.

应用程序可以在Xcode为存档构建过程-仅当通过Organizer运行验证时才失败,这是临时保存或App Store提交所必需的。

Apps can pass validation within the Xcode "Build for Archive" process - it only fails when the validation is run via Organizer, which is required to save for ad hoc or App Store submittal.

在花费数小时试图查找常见的代码签名权利问题之后,当导出失败时,我最终在系统控制台中注意到以下行:

After spending hours trying to trace down the usual code signing entitlement issues, I eventually noticed the following line in the system console when the export fails:

12年3月10日2:32:48.450 PM [0x0-0x261261] .com.apple.dt.Xcode:/ Users / chris / Library / Developer / Xcode / Archives / 2012-03-10 / Coverage 3-10-12 2.32 PM.xcarchive / Products / Applications / Coverage.app / Tiles / T-Mobile-roam / 4:是目录

标题目录已通过为任何添加的文件夹创建文件夹引用添加到我的项目中。

The "Tiles" directory has been added to my project via "Create folder reference for any added folders".

我发现删除了Tiles目录允许应用构建和验证。将其重新添加会导致此代码符号失败。

I discovered that removing the Tiles directory allows the app to build and validate. Adding it back results in this code sign failure.

似乎添加多级目录树会完全破坏验证过程,并且错误消息会将开发人员发送给用户。试图追查真正不是问题的代码签名和授权问题。

It seems that adding a multi-level directory tree completely screws up the validation process, and the error messages send developers on a wild goose chase trying to track down code signing and entitlement issues that really aren't an issue.

我以前从未在Xcode的发行版中遇到过任何问题-这似乎是Xcode 4.3.1中出现了一个严重的新错误。

I never had any issues with prior releases of Xcode - this seems to be a new serious bug in Xcode 4.3.1.

是否有任何可行的解决方法可以让我们向应用程序提交更新?

Is there any workaround possible that will allow us to submit updates to our app?

注意:

此线程似乎与以下内容相关: https://devforums.apple.com/message/630800

This thread seems related: https://devforums.apple.com/message/630800

此问题涉及类似的问题以及:
Xcode 4.3:协同设计操作失败(请检查您选择的身份是否有效)

This question touches on a similar issue as well: Xcode 4.3: Codesign operation failed (Check that the identity you selected is valid)

推荐答案

我花了一天的时间来隔离此错误,

I spent a day trying to isolate this bug, and I've finally nailed it.

在验证App Store或保存AdHoc分发扼流圈时,只要您的子目录中存在XCode 4.3.1中的代码签名者

The code signer in XCode 4.3.1 when validating for the App Store or saving for AdHoc distribution chokes whenever there is a subdirectory in your bundle that has the same name as its parent directory.

例如:

test/test/file.x -- FAIL
test/test2/file.x -- WORKS

这似乎是Xcode 4.3.1中的新功能,希望很快会得到解决。

This seems to be new in Xcode 4.3.1, and hopefully will be fixed soon.

更新:从Apple DTS支持小组收到的回音确认了该问题,并指出除了重命名捆绑包中的目录之外,没有其他已知的解决方法。 ugh

UPDATE: I have heard back from Apple DTS support confirming the issue, and indicating that there is no known workaround yet other than renaming the directories in the bundle. ugh

这篇关于XCode 4.3.1破坏了通过引用添加目录的应用程序的验证。任何解决方法?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆