iOS 应用提交和 Beta 审核流程

iOS app submission and beta review process

提问by Danoram

I'm currently developing an iOS application for a client. The submission review process to the store can often be a lengthy process and is relatively new to me.

我目前正在为客户开发 iOS 应用程序。提交给商店的过程通常是一个漫长的过程，对我来说相对较新。

My client wants to do a beta test using TestFlightas well as submitting the app to the app store afterwards, through XCodeand Itunes Connect.

我的客户想要使用TestFlight进行 beta 测试，并在之后通过XCode和Itunes Connect 将应用程序提交到应用程序商店。

Scouring Apple's documentation I can't seem to get a good idea of following:

搜索 Apple 的文档我似乎无法很好地了解以下内容：

• If I want to update an existing application on the store do I have to go through the review process again in full?
  
  

• If I have my app approved for beta testing release through TestFlight, is this taken into consideration when submitting the app for review to the store?
  
  

• If I want to test a new build through TestFlight, do I need to go through the beta review process again in full?
  
  

• If an app is approved on the app store, does it automatically pass the beta review?
  (This sounds counterintuitive considering you don't want to do a beta test after releasing to the store but in a scenario where you may want to do a closed release of an update for testing while a live version is up on the store)

• 如果我想更新商店中现有的应用程序，我是否必须再次完整地完成审核流程？
  
  

• 如果我的应用已通过 TestFlight 批准进行 Beta 测试发布，那么在将应用提交给商店进行审核时是否会考虑到这一点？
  
  

• 如果我想通过 TestFlight 测试新版本，我是否需要再次完整地通过 Beta 版审核流程？
  
  

• 如果应用在应用商店获得批准，它是否会自动通过测试审核？
  （这听起来有悖常理，因为您不想在发布到商店后进行 Beta 测试，但在这种情况下，您可能希望在商店中提供实时版本时进行封闭式更新以进行测试）

回答by Fattie

Useful preliminary tip!

有用的初步提示！

https://stackoverflow.com/a/55044137/294884

https://stackoverflow.com/a/55044137/294884

Critical! news for 2019

危急！2019年新闻

As of February, there's a bug on the new iTunes connect. (Who would have thought?)

截至 2 月，新的 iTunes 连接存在错误。（谁曾想到？）

If your test flight build is stuck on "processing" (after, say, 5 minutes)...

如果您的试飞版本停留在“处理”阶段（例如，5 分钟后）...

In fact, simply log out of appstoreconnect.apple.com and log back in.

事实上，只需退出 appstoreconnect.apple.com 并重新登录即可。

Amazingly, it will now be ...

令人惊讶的是，它现在将...

This seems to work "often", perhaps even "all the time", if it's stuck for more than 5 mins.

如果卡住超过 5 分钟，这似乎“经常”，甚至“一直”有效。

I would say this problem happens about 3 times in ten.

我会说这个问题大约在十次发生 3 次。

Another point that is harder to demonstrate. Traditionally if a build was "stuck": if you increased the build number by one and just archived and sent it again. That seemed to flush forward the first one that was stuck. Unfortunately the "add one" trick seems to not work any more. If a build is "stuck" it seems to just stay "stuck".

还有一点比较难证明。传统上，如果构建被“卡住”：如果您将构建编号增加 1，然后将其存档并再次发送。那似乎冲向了第一个被卡住的人。不幸的是，“添加一个”技巧似乎不再起作用。如果构建“卡住”，它似乎只是“卡住”。

---

---

News for 2018 !

2018 年的新闻！

Changes for 2018!

2018年的变化！

1. Apple had the famous "utter disaster" of the end of 2017 / early 2018 where (basically) nothing worked for some weeks. It seems to have generally settled down as of Feb 2018.

2. Change! Regarding the delay: "for betas (nothing to do with the app store), the delay you must experience, each time you have a new version numberof your beta." That was usually quite short ("about one day"); now it is distinctly longer ("about two days"). They changed something.

1. 苹果公司在 2017 年底/2018 年初发生了著名的“彻底灾难”，其中（基本上）几周没有任何效果。截至 2018 年 2 月，它似乎已经普遍稳定下来。

2. 改变！关于延迟：“对于测试版（与应用商店无关），每次您拥有测试版的新版本号时，您必须经历的延迟。” 那通常很短（“大约一天”）；现在明显更长了（“大约两天”）。他们改变了一些东西。

(Note - don't forget that: also when you actually send a version to the App Store, that "forces" you to now have a new version number on the betas. So, if it's Monday morning and your launch team gets a new version approved (for the app store), and then it's Monday afternoon and you're about to send out a new beta build, in fact you now have togo up a version (and you will get the delay mentioned in the previous point).)

（注意 - 不要忘记：当您实际向 App Store 发送一个版本时，这“强制”您现在在测试版上拥有一个新版本号。因此，如果是星期一早上并且您的发布团队获得了一个新版本版本已批准（适用于应用程序商店），然后是周一下午，您将发送新的 Beta 版本，实际上您现在必须升级一个版本（并且您会得到上一点中提到的延迟） .)

1. Change! Regarding the delay: "for betas (nothing to do with the app store), the delay you must experience, each time you simply upload a new build (so, a higher build number) with no change to the version number." Basically this is now longer, but nor broken.It used to be that this usually happened almost instantly, and, sometimes it would take awhile (say 5-10 minutes), and finally sometimes it was completely broken (as described below). For 2018:they have changed it. It now always takes "5-10 minutes". (It never happens instantly.) And they do seem to have resolved the problemwhere it is sometimes broken and you have to try again: that seems to be history, fortunately.

2. Change! Submissions to the actual app store. Simply, these are quicker now, in general. (Even if you have in app purchase - whatever.) Perhaps they improved their handling for testors, automated something, or whatever.

3. 改变！关于延迟：“对于测试版（与应用商店无关），您必须经历延迟，每次您只需上传新版本（因此，更高的版本号）而不更改版本号。” 基本上这现在更长了，但也没有坏。过去，这通常几乎立即发生，有时需要一段时间（比如 5-10 分钟），最后有时会完全中断（如下所述）。 对于 2018 年：他们已经改变了。现在总是需要“5-10 分钟”。（它永远不会立即发生。）而且他们似乎确实解决了有时会损坏并且您必须再试一次的问题：幸运的是，这似乎已成为历史。

4. 改变！提交到实际的应用程序商店。简而言之，总的来说，这些现在更快了。（即使你有应用内购买——不管怎样。）也许他们改进了对测试人员的处理，自动化了一些东西，或者其他什么。

For mid 2016 (updated for 2018) ...

2016 年年中（2018 年更新）...

If I want to update an existing application on the store do I have to go through the review process again in full?

如果我想更新商店中现有的应用程序，我是否必须再次完整地完成审核流程？

yes, definitely.

当然是。

If I have my app approved for beta testing release through TestFlight, is this taken into consideration when submitting the app for review to the store?

如果我的应用已通过 TestFlight 批准进行 Beta 测试发布，那么在将应用提交给商店进行审核时是否会考虑到这一点？

No, for better or worse it is absolutely unrelated.

不，无论好坏，这绝对无关。

(Indeed: it's fairly common to submit straght to the store. To be clear, many companies simply never use TestFlight in any way. You don't have to if you don't want to.)

（确实：直接向商店提交是相当普遍的。需要明确的是，许多公司根本不以任何方式使用 TestFlight。如果您不想，则不必使用。）

If I want to test a new build through TestFlight, do I need to go through the beta review process again in full?

如果我想通过 TestFlight 测试新版本，我是否需要再次完整地通过 Beta 版审核流程？

Say you have an app HappyApp:

假设您有一个应用程序 HappyApp：

The firsttime you submit it for betatesting, there is a delay: usually of about two days.

在第一次提交它的β测试，有一个延迟：通常在两天左右。

That is while waiting for "beta approval". So that's "build 1" of your betaversion of HappyApp on TestFlight.

那是在等待“测试版批准”。这就是TestFlight 上 HappyApp测试版的“构建 1” 。

Every FIRST TestFlightbuild, has - for sure - a delay of about two days:

每个 FIRST TestFlight构建，肯定有大约两天的延迟：

(Note - this has changed in early 2018 from "about one day" to "about two days".)

（注意 - 这在 2018 年初已从“大约一天”更改为“大约两天”。）

This appears to be a human process. (Nobody knows for sure.) You can rely on this delay, it is never shorter. This is exactly what a beta looks like during that one-day delay:

这似乎是一个人为的过程。（没有人确切知道。）您可以信赖这个延迟，它永远不会更短。在一天的延迟期间，这正是测试版的样子：

So you have to wait about two days for the firstreview of a given beta version number.

因此，您必须等待大约两天才能对给定的 beta版本号进行第一次审核。

On to the next step. So, for builds 2, 3, 4, 5 .. of HappyApp on TestFlight:

进入下一步。因此，对于 TestFlight上 HappyApp的构建2、3、4、5.. ：

When you submit each new build, there is a delay of 5-10 minutesfor each of those new builds to go through.

当您提交每个新构建时，每个新构建都会延迟 5-10 分钟。

All beta builds after the first, have a 5-10 minute delay.

第一次之后的所有 beta 版本都有 5-10 分钟的延迟。

• as of early 2018, that delay is reliably 5-10 minutes
• in the old days, sometimes it happened instantly: this is no longer the case. It is now always 5-10 minutes
• in the old days, often it would "just break" at this stage. They do appear to have finally fixed this problem, after three years of developers complaining.There was a large section in this post dealing with the issue, any history buffs can find it in the edits!

• 截至 2018 年初，该延迟可靠地为 5-10 分钟
• 在过去，有时它会立即发生：现在已经不是这样了。现在总是 5-10 分钟
• 在过去，它通常会在这个阶段“破裂”。 经过三年的开发人员抱怨，他们似乎终于解决了这个问题。这篇文章中有很大一部分涉及这个问题，任何历史爱好者都可以在编辑中找到它！

If an app is approved on the app store, does it automatically pass the beta review?

如果应用在应用商店获得批准，它是否会自动通过测试审核？

Stupidly, no. You have to completely start again.

愚蠢的，没有。你必须完全重新开始。

So TBC. Say you're on version 4of your app. You're going along making beta builds every few hours for your team. Build number 3010, 3011, 3012, etc. As it happens, you submit a real build to the app store and get the next version of the app approved - so that will be version 5in the app store. Simply then - on the beta side - you are then forcedto change to a new version number. (And thus as it explains above, you then will the suffer the "two day delay" on the next beta you send in, because, it is indeed the first beta of a new version number.)

所以待定。假设您使用的是应用程序的第 4 版。您将每隔几个小时为您的团队制作测试版。内部版本号 3010、3011、3012 等。碰巧的是，您向应用程序商店提交了一个真实的内部版本，并获得了应用程序的下一个版本的批准——因此应用程序商店中的版本 5。就这样 - 在测试版方面 - 然后您将被迫更改为新版本号。（因此，正如上面所解释的，您将在发送下一个测试版时遭受“两天延迟”，因为它确实是新版本号的第一个测试版。）

A commentor wrote...

一位评论员写道...

(All of this sounds counterintuitive...

（所有这些听起来都违反直觉......

Everything about Apple's approval process is silly. Leave your common sense at the door! :/

关于苹果审批流程的一切都是愚蠢的。把你的常识留在门口！：/

Updated for Feb 2018 !

2018 年 2 月更新！

---

---

Footnote! Apple previously had an annoying problem where: with a brand-new app (brand new BundleID, etc) it would take about half an hour to simply appear in your list of apps on iTunesConnect. This was quite confusing. Fortunately this problem is now history.

脚注！Apple 以前有一个恼人的问题：使用全新的应用程序（全新的 BundleID 等），它需要大约半小时才能出现在 iTunesConnect 上的应用程序列表中。这很令人困惑。幸运的是，这个问题现在已经成为历史。

回答by jungledev

I feel that this thread is lacking a clear and concise answer to your questions.

我觉得这个帖子对你的问题缺乏清晰简洁的答案。

In order of questions asked:

按照提问的顺序：

1. Yes- if you want to update an existing app in the App Store, you must go through the review process again.

2. No- If your app is approved in the Beta review process, this is nottaken into account for the official review process. You will still need to wait the normal duration for official review.

3. It depends*If you want to test a new build with TestFlight, you will have to wait for the beta review process again if you changed the version number. If you changed the build number, it is usually approved instantly.

4. No, if a version is approved for the app store, it is not auto-approved for TestFlight. MORE IMPORTANTLY- once you have a version approved for the official App Store, you CANNOT push a new build to your TestFlight users with the same version numberas the pre-approved official App Store app. You must change the version number if you want to push a new build to your TestFlight users, AND it will be subjected to a longer beta app review process because it is seen as a new 'version'. The better solution is to remove your pre-approved official app, push a new build to your test flight users, and re-submit your official app for review again. I know it's stupid, but it's the only effective solution.

1. 是的- 如果您想更新 App Store 中现有的应用程序，您必须再次通过审核流程。

2. 否- 如果您的应用在 Beta 审核流程中获得批准，则官方审核流程不会考虑这一点。您仍然需要等待正常的时间才能进行正式。

3. 这取决于*如果您想使用 TestFlight 测试新版本，如果您更改了版本号，则必须再次等待 beta 审核过程。如果您更改了内部版本号，通常会立即获得批准。

4. 否，如果某个版本已通过应用商店批准，则不会自动批准用于 TestFlight。更重要的是 - 一旦您获得了官方 App Store 批准的版本，您就不能将新版本推送给您的 TestFlight 用户，其版本号与预先批准的官方 App Store 应用程序相同。如果您想将新版本推送给您的 TestFlight 用户，您必须更改版本号，并且它将接受更长的 beta 应用程序过程，因为它被视为新的“版本”。更好的解决方案是删除您预先批准的官方应用程序，将新版本推送给您的试飞用户，然后重新提交您的官方应用程序以供审核。我知道这很愚蠢，但这是唯一有效的解决方案。

回答by Helen Wood

Update July 2019

2019 年 7 月更新

TestFlight review times:

TestFlight 审核时间：

• First upload build: takes 36h average.
• Updates: take from 6h to 20h average for Build.

• 第一次上传构建：平均需要 36 小时。
• 更新：从 6 小时到 20 小时的平均构建。

Weekends are off.

周末休息。

More information here:

更多信息在这里：

IOS APP SUBMISSION AND BETA REVIEW PROCESS TIMES

IOS APP提交和BETA审核流程时间

回答by Eyesofbanquo

The review process is really quick for both the Beta and Final build. I found that the Final build review process was even quicker once I put it through the Beta.

Beta 版和最终版的审核过程都非常快。我发现一旦我通过 Beta 版，最终构建过程会更快。

You'll have to get all releases checked but that's because you have to submit a review for each build you intend on pushing to the store. This is to make sure nobody gets an app up and then tries to sneak in another app that's completely different (and possibly malicious).

您必须检查所有版本，但这是因为您必须为要推送到商店的每个构建提交。这是为了确保没有人启动一个应用程序，然后试图潜入另一个完全不同的应用程序（可能是恶意的）。

For new TestFlight builds you have to submit it for review again but Apple is really quick with approving them. And once it's approved it'll send you an email saying it was approved and it'll automatically send everyone a notification, through Testflight, that the new build is available for update

对于新的 TestFlight 版本，您必须再次提交以供审核，但 Apple 批准它们的速度非常快。一旦获得批准，它会向您发送一封电子邮件，说它已获得批准，并且会自动通过 Testflight 向所有人发送通知，告知新版本可以更新

Once the App is approved the App Store then everyone who was on the Beta update will be able to update to the latest build that's currently available on the App Store.

一旦 App 在 App Store 获得批准，参与 Beta 更新的每个人都将能够更新到 App Store 上当前可用的最新版本。

The Beta builds and the Final builds may be exactly the same but Apple treats them differently so you can't get it approved for the App Store but then start using TestFlight with that build that was just approved. The App Store is the App Store and Testflight is TestFlight.

Beta 版本和 Final 版本可能完全相同，但 Apple 对它们的处理方式不同，因此您无法获得 App Store 的批准，然后开始将 TestFlight 与刚刚批准的版本一起使用。App Store 是 App Store，Testflight 是 TestFlight。