存档验证的奇怪错误 [英] Strange Errors on Archive Validation

问题描述

在Xcode 8的公开发布之前，我的iOS项目处于相当稳定的状态。在与Migrator有点混淆之后，我终于说服了编译器，我做了不想要去Swift 3，而且我的代码确实是有效的Swift 2.3。不确定这是否与组织者在验证我期待已久的存档中所做的事情有关，其中包含一些针对iOS 10的早期修复程序，但我们会看到......

I've had an iOS project in fairly stable condition up until Xcode 8's public release. After a bit of confusion with the Migrator, I finally convinced the compiler that I did not want to go Swift 3 yet, and that my code was indeed valid Swift 2.3. Not sure if this at all relates to what the Organizer does in validating my long-awaited archive with some long-overdue fixes for iOS 10, but we'll see...

无论如何，我让Xcode存档我的最新版本（顺便说一下，我的iPhone 5s运行正常）。我告诉管理器验证...以准备上传到iTunes Connect。经过大量工作之后，它终于向我吐了一口气：

Anyway, I got Xcode to archive my latest build (which runs fine on my iPhone 5s by the way). I tell Organizer to "Validate..." in preparation for an upload to iTunes Connect. After a good deal of doing its thing, it finally spits this at me:

现在已经三天了。 Application Loader给了我类似的东西，但没有多大帮助：

Been at this for three days now. Application Loader gives me something similar, but not much more helpful:

按照此答案中的建议，我发现每一个我编译的资产中的一个读取为sRGB，不是 16位或P3。旁白：API分析文件什么时候变得太大？我的意思是，我确实使用Apple的API很多，但我不能单独使用它。这就是他们的目的，对吗？

Following the suggestions in this answer, I find that every single one of my compiled assets read as sRGB, not 16-bit, or P3. Aside: When does an API analysis file get "too large"? I mean, sure I use Apple's APIs a lot, but I can't be alone in that. That's what they're for, right?

我已经尝试过（差不多）我能想到的一切。我已经重新编写了十几种不同方式的代码，阅读并重新构建了我认为可能相关的构建设置，并尝试了bitcode和符号包含的每种组合。几乎所有我能想到的东西都没有移植到Swift 3！这真的是我的解决方案吗？这是一个相当大的跳跃，随着时间的推移，我倾向于在我猛烈抨击以支持更新的代码库之前将这个工作版本提供给我的用户。

I've tried (almost) everything I can think of. I've redone my code signing a dozen different ways, read and recombobulated the build settings wherever I thought could be relevant, and tried every combination of bitcode and symbol inclusion available to me. Just about everything I could come up with short of migrating to Swift 3! Could that really be my solution? It's a rather big jump, and with the time I have, I'd prefer to get this working build out to my users before I'm slammed too hard to shore up the updated codebase.

我似乎无法在ITunesSoftwareServiceAuthenticationErrorDomain上找到任何内容，或者这个神秘的错误434。到目前为止，我发现的唯一参考是死StackOverflow问题。真的希望作者没有删除它......想知道他是否找到了他的答案？

I can't seem to find anything on "ITunesSoftwareServiceAuthenticationErrorDomain", or this mysterious "error 434". The only reference I've found so far leads to a dead StackOverflow question. Really wish the author hadn't removed it... Wonder if he found his answer?

所以我的问题如下：我做错了什么来得到这些错误，我该如何解决它们？我宁愿没有上传没有符号或bitcode，所以如果这是解决方法，我想知道为什么，所以我不会限制自己的愚蠢。

So my question is as follows: What am I doing wrong to get these errors, and how can I fix them? I'd rather not have to upload without symbols or bitcode, so if that's the workaround, I'd like to know why, so I'm not limiting myself for something dumb.

干杯！

推荐答案

我在提交申请时遇到了与Xcode 8.2相同的问题：

I had the same problem with Xcode 8.2 while submitting my application:

 ITunesSoftwareServiceAuthenticationErrorDomain error 434.

解决方案：我切换到不同的网络，它对我有用。

这篇关于存档验证的奇怪错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！