ios 我的预发布应用程序已经在 iTunes Connect 中“处理”了一个多星期，结果是什么？

My prerelease app has been "processing" for over a week in iTunes Connect, what gives?

提问by Robert Atkins

I used Xcode 6.1.1 to upload a new version of a prerelease app to iTunes Connect so I could distribute it to my external beta testers. I've done this with two versions of the same app previously and it worked fine.

我使用 Xcode 6.1.1 将预发布应用程序的新版本上传到 iTunes Connect，以便我可以将其分发给我的外部 Beta 测试人员。我以前用同一个应用程序的两个版本完成了这个，它运行良好。

But this time, the upload was stuck in "Processing" state for over a week. I tried again (same version, new build number) and it's now been over 24 hours with no change.

但这一次，上传卡在“正在处理”状态一个多星期。我再次尝试（相同版本，新版本号），现在已经超过 24 小时没有任何变化。

The app passed validation fine.

该应用程序通过了验证。

What gives?

是什么赋予了？

采纳答案by combinatorial

Go to "Resources & Help" in iTunes Connect. Select "Contact Us" and follow the wizard. I don't think anyone other than Apple can answer this. And this is what we have done in a similar situation in the past.

前往 iTunes Connect 中的“资源和帮助”。选择“联系我们”并按照向导操作。我认为除了 Apple 之外没有任何人可以回答这个问题。这就是我们过去在类似情况下所做的。

回答by Nuthatch

We had a similar issue. Uploaded builds were queueing up and it simply said "Processing" with the popup help, “After builds are uploaded they will go through a processing state before they can be used.” Days passed.

我们有一个类似的问题。上传的构建正在排队，它只是简单地说“正在处理”并带有弹出式帮助，“构建上传后，它们将经过处理状态才能使用。” 日子过去了。

Selecting "Internal Testers," making a change, and saving seemed to immediately clear the queue: The latest build was now active and available for testing. I've done this twice with two different apps now.

选择“内部测试人员”，进行更改并保存似乎立即清除了队列：最新版本现在处于活动状态并可用于测试。我现在已经用两个不同的应用程序完成了两次。

Update:At this point, all bets are off. It seems "processing" happens when Apple quietly upgrades iTunes Connect and there's nothing you can do about it.

更新：此时，所有赌注都已结束。似乎“处理”发生在 Apple 悄悄升级 iTunes Connect 时，您对此无能为力。

On September 23, 2015 iTunes Connect didn't accept any uploads for nearly 24 hours. The "Internal Testers" trick didn't work. Eventually bumping the version number (to avoid "duplicate binary" error) and re-submitting worked.

2015 年 9 月 23 日，iTunes Connect 近 24 小时不接受任何上传。“内部测试人员”技巧没有奏效。最终修改版本号（以避免“重复二进制”错误）并重新提交工作。

The next day, Surprise! iTunes Connect was completely changed. I guess we were all looking at a dead site while they brought up the new version in the background :(

第二天，惊喜！iTunes Connect 完全改变了。我猜我们都在看一个死网站，而他们在后台提出新版本:(

In our case we can still see dozens of "failed" uploads still sitting in the "processing" state. Oh well.

在我们的例子中，我们仍然可以看到数十个“失败”的上传仍然处于“处理”状态。那好吧。

Some people report using Application Loaderworks better than Xcode for submitting builds to iTunes Connect. You can find it inside Xcode now, under the Xcode menu "Open Developer Tool" item.

有些人报告说使用Application Loader比 Xcode 更好地将构建提交到 iTunes Connect。您现在可以在 Xcode 中的 Xcode 菜单“Open Developer Tool”项下找到它。

Sometimes this works. Sometimes it doesn't. Your milage may vary ˉ\_(ツ)_/ˉ

有时这有效。有时不会。您的里程可能会有所不同 ˉ\_(ツ)_/ˉ

回答by Scotch Design

The solution (as suggested by Apple Support in their response to a request for assistance) is to upload a new binary. I did this via XCode (same revision 1.4, but incremented the Build number from 1 to 2) and it processed almost immediately.

解决方案（正如 Apple 支持在响应帮助请求时所建议的那样）是上传一个新的二进制文件。我通过 XCode（相同的修订版 1.4，但将内部版本号从 1 增加到 2）并几乎立即处理。

If you get stuck in "Processing" purgatory, increment the Build number in XCode, Archive and Submit to the App Store again. If it doesn't process within 15 minutes, try again.

如果您陷入“处理”炼狱，请在 XCode 中增加内部版本号，存档并再次提交到 App Store。如果在 15 分钟内没有处理，请重试。

回答by Avt

Had the same problem using XCode 7 betta-5. Fixed by unchecking "Include bitcode" checkbox during archive uploading:

使用 XCode 7 betta-5 有同样的问题。通过在存档上传期间取消选中“包含位码”复选框来修复：

回答by Sean Miller

I had the same issue. I tried making changes to "Internal Testers." No effect. I uploaded a new build using the Application Loader. Once the upload completed, the previous build changed from "Processing" to being available.

我遇到过同样的问题。我尝试对“内部测试人员”进行更改。没有效果。我使用 Application Loader 上传了一个新版本。上传完成后，之前的构建将从“正在处理”变为可用。

回答by turingtested

I got this message from App Store Developer Support (2016-01-02):

我从 App Store 开发者支持 (2016-01-02) 收到这条消息：

Be aware that it can take up to 24 hours for a build to fully process through our system and become available for use. If a build does not finish processing in 24 hours, this can typically be resolved by submitting the build again with a higher build number.

请注意，构建完成通过我们的系统并可供使用最多可能需要 24 小时。如果构建未在 24 小时内完成处理，通常可以通过使用更高的构建编号再次提交构建来解决此问题。

Not much of an answer (nothing about why it can take so long time), but it's the answer Apple is giving us.

没有太多答案（没有关于为什么要花这么长时间），但这是 Apple 给我们的答案。

回答by Oscar Salguero

I had a similar issue.

我有一个类似的问题。

Yesterday, I submitted an app build (1.03) using Xcode, it was around 6 PM and this morning it was still "Processing", in fact it is still "Processing".

昨天，我使用 Xcode 提交了一个应用程序构建（1.03），当时是下午 6 点左右，今天早上它仍然在“处理中”，实际上它仍然是“处理中”。

This morning around 10:30 AM I submitted a second build (1.04) using Xcode but that one also took too much time to change its status, so I submitted a third build (1.05) using Application Loader around noon, application loader gave me a warning about the app being too large to validate its API usage (the build is around 12.5 MB), it was just a warning so I submitted it and I'm still waiting to for it to change status (2:16 PM).

今天早上 10 点 30 分左右，我使用 Xcode 提交了第二个构建 (1.04)，但那个也花了太多时间来更改其状态，所以我在中午左右使用 Application Loader 提交了第三个构建 (1.05)，应用程序加载器给了我一个关于应用程序太大而无法验证其 API 使用情况的警告（构建大约 12.5 MB），这只是一个警告，所以我提交了它，我仍在等待它更改状态（下午 2:16）。

Of course, each time I bumped up the Build number. All the builds had Enable Bitcode set to NO.

当然，每次我增加版本号。所有版本的 Enable Bitcode 都设置为 NO。

UPDATE (1:52 PM):

更新（下午 1:52）：

The second build (1.0.4) just became available for TestFlight.

第二个版本 (1.0.4) 刚刚可用于 TestFlight。

UPDATE (4:43 PM):

更新（下午 4:43）：

The third build (1.0.5), the one submitted with Application Loader just became available for TestFlight.

第三个版本 (1.0.5)，即随 Application Loader 提交的版本，刚刚可用于 TestFlight。

My conclusion is that their servers are slower than before... maybe the volume of apps that are being processed has increased and the load of their systems is higher because there are new things to check for (bitcode, watch os stuff, etc).

我的结论是他们的服务器比以前慢了……也许正在处理的应用程序的数量增加了，他们的系统负载更高了，因为有新的东西要检查（位码、观看操作系统等）。

回答by Seslyn

I ran into this issue yesterday. I submitted multiple builds with a variety of different settings. What finally worked for me was submitting through Application Loader with no bitcode.

我昨天遇到了这个问题。我提交了多个具有各种不同设置的构建。最终对我有用的是通过 Application Loader 提交而没有 bitcode。

I hope this helps someone avoid the headache I went through. Its been 24 hours and the apps submitted through Xcode are all still "processing", the one submitted through Application Loader was available within an hour or so.

我希望这可以帮助某人避免我经历的头痛。已经 24 小时了，通过 Xcode 提交的应用程序都还在“处理”中，通过 Application Loader 提交的应用程序在一小时左右就可用了。

回答by Royce C

If you run into this issue now, it's an Apple issue. They are releasing a new version of iTunesConnect. A bunch of my builds had been getting stuck in Processing these past few days. Today, they were getting stuck on Uploaded. Multiple phone calls and different answers later, the new site was justreleased and my builds are showing as Processing or available for submission. Though, they all have a yellow warning icon next to them. Not sure what that is.

如果你现在遇到这个问题，那就是苹果的问题。他们正在发布新版本的 iTunesConnect。在过去的几天里，我的一些构建一直卡在 Processing 中。今天，他们陷入了上传的困境。多个电话和不同的答案之后，新站点刚刚发布，我的构建显示为正在处理或可供提交。不过，它们旁边都有一个黄色警告图标。不知道那是什么。

回答by Jervisbay

I submitted a new version of my app via Xcode 7.1 successfully. Then noticed the build was stuck in "Processing" longer than usual.

我通过 Xcode 7.1 成功提交了我的应用程序的新版本。然后注意到构建卡在“处理”中的时间比平时长。

I followed Scotch's suggestion by increasing the build number, while keeping the same version, and submitted again from Xcode. This time the new build became available for testing within 5 minutes.

我按照 Scotch 的建议增加了内部版本号，同时保持相同的版本，然后从 Xcode 再次提交。这次新版本在 5 分钟内即可用于测试。

I was then able to select that build and clicked on Start testing. My internal testers received the notification emails and were able to test the new version via the Testflight app.

然后我能够选择该版本并单击开始测试。我的内部测试人员收到了通知电子邮件，并能够通过 Testflight 应用程序测试新版本。