This is quite linked to this question but it doesn't have any solution.
On uploading a build to iTunes Connect, I received the following message:
这和这个问题有很大的关系，但是没有任何解决办法。在上传一个构建到iTunes Connect时，我收到了以下消息:
We have discovered one or more issues with your recent delivery for "Hurdal IL". Your delivery was successful, but you may wish to correct the following issues in your next delivery:
我们发现你们最近交货的"Hurdal IL"有一个或多个问题。你的交货是成功的，但你可能希望在下次交货时纠正以下问题:
Unexpected Machine Code - Your upload contains both bitcode and native machine code. When you provide bitcode, it's not necessary to include machine code as well. To reduce the size of your upload, use Xcode 7.3 or later, or any other toolchain that removes machine code.
意外的机器代码-你的上载包含位代码和本机代码。当您提供位代码时，也不需要包括机器代码。要减少上传的大小，可以使用Xcode 7.3或更高版本，或者使用任何其他可以删除机器代码的工具链。
After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to iTunes Connect.
在您纠正了问题之后，您可以使用Xcode或应用程序加载程序将一个新的二进制文件上载到iTunes Connect。
- What is the resolution?
- 分辨率是多少?
- Will the app approval be affected if this build is uploaded ?
- 如果这个构建被上传，应用程序的审批会受到影响吗?
7 个解决方案
#1
14
I just talked with the Apple Developer Support, the official one. They don't said it clearly, but yes it's a bug. So, it's confirmed that there's some malfunctioning in their side.
我刚刚和官方的苹果开发者支持部门谈过。他们没有说得很清楚，但这是一个错误。所以，可以肯定的是他们这边有一些故障。
UPDATE: It won't affect the Apps in Production neither Testing!
更新:它不会影响生产中的应用程序，也不会影响测试!
#2
3
I have same issue but in my case I set in Xcode Build Setting Enable Bitcode to NO. After this error I change it to YES and it works
我也有同样的问题，但是在我的例子中，我设置了Xcode Build设置Enable Bitcode为NO。在这个错误之后，我将它改为YES，并且它有效。
#3
1
No, its not effect app approval and the binary seems to be accepted by the iTunes store.
不，它不影响应用程序的批准，而且二进制似乎被iTunes商店所接受。
#4
1
I just uploaded a binary recently (like 20m ago). They did sent me a note just like you. After that, I just re-built it again, only update the build version (1943) and upload. Now it seems like there's nothing happened anymore. And the previous build (1942) has completed processing without failure. So I doubt it's a bug from Apple.
我最近上传了一个二进制文件(大约2000万年前)。他们确实像你一样给我发了一张纸条。之后，我重新构建了它，只更新了构建版本(1943年)并上传。现在好像什么都没发生了。之前的构建(1942)已经完成了没有失败的处理。所以我怀疑这是苹果的一个漏洞。
Just ignore it. You may want to build another binary to fix the warning tho.
只是忽略它。您可能希望构建另一个二进制文件来修复警告。
#5
1
I've the same problem, I send my application to review with that issue.
我也有同样的问题，我把我的申请寄去审查这个问题。
Result:
结果:
My app pass the review and already in publication. No problem... I think it's a issue from iTunes Connect.
我的应用程序通过了审查，已经发布了。没有问题…我认为这是iTunes Connect的问题。
#6
0
The app which I published with this waring was just approved by Apple. So to answer my question, this won't affect the app approval. Also, I am accepting @Helen Wood's answer as she was right that this is an apple bug.
我发布的这个软件是刚刚被苹果批准的。为了回答我的问题，这不会影响应用程序的审批。同时，我也接受了@Helen Wood的回答，因为她是对的，这是一个苹果迷。
#7
0
Just got this as well, it's a bug. I uploaded the near exact same binary as I did a couple of days ago which went through fine (only change was to the version and build number). Developer support confirmed this.
还有这个，这是一个bug。我上传了几乎完全相同的二进制文件，就像我几天前做的那样，它运行得很好(只是对版本和构建号进行了更改)。开发人员的支持证实了这一点。
If you do get the e-mail, don't worry about it. Your binary will still process and you'll still be able to submit it to the app store.
如果你收到了电子邮件，不要担心。你的二进制文件仍然可以处理，你仍然可以提交到应用程序商店。
#1
14
I just talked with the Apple Developer Support, the official one. They don't said it clearly, but yes it's a bug. So, it's confirmed that there's some malfunctioning in their side.
我刚刚和官方的苹果开发者支持部门谈过。他们没有说得很清楚，但这是一个错误。所以，可以肯定的是他们这边有一些故障。
UPDATE: It won't affect the Apps in Production neither Testing!
更新:它不会影响生产中的应用程序，也不会影响测试!
#2
3
I have same issue but in my case I set in Xcode Build Setting Enable Bitcode to NO. After this error I change it to YES and it works
我也有同样的问题，但是在我的例子中，我设置了Xcode Build设置Enable Bitcode为NO。在这个错误之后，我将它改为YES，并且它有效。
#3
1
No, its not effect app approval and the binary seems to be accepted by the iTunes store.
不，它不影响应用程序的批准，而且二进制似乎被iTunes商店所接受。
#4
1
I just uploaded a binary recently (like 20m ago). They did sent me a note just like you. After that, I just re-built it again, only update the build version (1943) and upload. Now it seems like there's nothing happened anymore. And the previous build (1942) has completed processing without failure. So I doubt it's a bug from Apple.
我最近上传了一个二进制文件(大约2000万年前)。他们确实像你一样给我发了一张纸条。之后，我重新构建了它，只更新了构建版本(1943年)并上传。现在好像什么都没发生了。之前的构建(1942)已经完成了没有失败的处理。所以我怀疑这是苹果的一个漏洞。
Just ignore it. You may want to build another binary to fix the warning tho.
只是忽略它。您可能希望构建另一个二进制文件来修复警告。
#5
1
I've the same problem, I send my application to review with that issue.
我也有同样的问题，我把我的申请寄去审查这个问题。
Result:
结果:
My app pass the review and already in publication. No problem... I think it's a issue from iTunes Connect.
我的应用程序通过了审查，已经发布了。没有问题…我认为这是iTunes Connect的问题。
#6
0
The app which I published with this waring was just approved by Apple. So to answer my question, this won't affect the app approval. Also, I am accepting @Helen Wood's answer as she was right that this is an apple bug.
我发布的这个软件是刚刚被苹果批准的。为了回答我的问题，这不会影响应用程序的审批。同时，我也接受了@Helen Wood的回答，因为她是对的，这是一个苹果迷。
#7
0
Just got this as well, it's a bug. I uploaded the near exact same binary as I did a couple of days ago which went through fine (only change was to the version and build number). Developer support confirmed this.
还有这个，这是一个bug。我上传了几乎完全相同的二进制文件，就像我几天前做的那样，它运行得很好(只是对版本和构建号进行了更改)。开发人员的支持证实了这一点。
If you do get the e-mail, don't worry about it. Your binary will still process and you'll still be able to submit it to the app store.
如果你收到了电子邮件，不要担心。你的二进制文件仍然可以处理，你仍然可以提交到应用程序商店。