Testflight外部用户下载卡在90% [英] Testflight external user download gets stuck at 90%

查看:302
本文介绍了Testflight外部用户下载卡在90%的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

下载通过Testflight外部测试程序方法分发的应用程序的beta版本时, 显然 下载约90%。在 现实 中,下载已经完成,应用已准备就绪。

When downloading a beta build of my app, distributed via the Testflight external tester method, the download apparently stops at about 90%. In reality the download has completed and the app is ready to go.

这对我的测试人员来说非常混乱。

This is very confusing for my testers.

我发现迄今为止唯一建议的修复方法是在分发中包含应用程序info.plist,即使Xcode抱怨没有必要。无论如何包括它都没有效果。

The only suggested fix I've found to date, is to include the app info.plist in the distribution even though Xcode complains that it is not necessary. In any case including it had no effect.

推荐答案

我想确认这仍然是一个问题,因为我的外部测试人员经历了完全相同的事情。

I’d like to confirm this is still an issue as of today, as my external testers experienced exact same thing.

每个人都没有问题地下载了build 1。然后我提交了build 1.01,测试人员告诉我,他们设备上的TestFlight应用程序中的安装将无法完成,停留在90%。

Everyone downloaded build 1 without problem. Then I submitted build 1.01 and testers told me installation in TestFlight app on their devices would not complete, stuck at 90%.

我有远见制作备用电子邮件地址并邀请自己作为外部测试人员,因此我能够验证完全相同的问题。但是,我们所有人都发现我们可以退出TestFlight并且我的新版本已经替换了设备上的旧版本并且正确地作为新版本运行。

I had the foresight to make a spare email address and invite myself as an external tester, so I was able to verify exact same issue. However, all of us found we could just exit TestFlight and my new build had replaced the old build on the device and functioned correctly as new build.

我的新版本在TestFlight中显示为1.1,而不是我的Xcode项目中的1.01,应该是一个小费。

It should have been a tip-off that my new build showed up in TestFlight as 1.1, instead of the 1.01 in my Xcode project.

从那以后,我遇到了几个提到领先零问题的帖子。迟到总比没有好,我实际上深入研究了文档,发现了这个:

Since then, I’ve run across several posts mentioning the leading zero problem. Better late than never, I actually dug into the documentation, and found this:

从应用程序分发指南:设置版本号和构建字符串

From App Distribution Guide: Setting the Version Number and Build String

版本号是一个两个周期分隔的正整数列表,如4.5.2所示。第一个整数表示主要修订,第二个整数表示次要修订,第三个表示维护版本。版本号显示在商店中,该版本应与稍后在iTunes Connect中输入的版本号相匹配。有关可能值的详细信息,请参阅信息属性列表键参考中的CFBundleShortVersionString。

The version number is a two-period-separated list of positive integers, as in 4.5.2. The first integer represents a major revision, the second a minor revision, and the third a maintenance release. The version number is shown in the store and that version should match the version number you enter later in iTunes Connect. For details on possible values, see CFBundleShortVersionString in Information Property List Key Reference .

构建字符串表示包的迭代(已发布或未发布),也是两个周期分隔的正整数列表,如1.2.3所示。对于Mac应用程序,用户可以单击关于窗口中的版本号以在版本号和构建字符串之间切换。有关可能值的详细信息,请参阅信息属性列表键参考中的CFBundleVersion。

The build string represents an iteration (released or unreleased) of the bundle and is also a two-period-separated list of positive integers, as in 1.2.3. For Mac apps, the user can click the version number in the About window to toggle between the version number and the build string. For details on possible values, see CFBundleVersion in Information Property List Key Reference.

信息属性列表密钥参考在Core Foundation Keys的文档中:

Information Property List Key Reference is in documentation for Core Foundation Keys:

CFBundleVersion(String - iOS,OS X)指定捆绑包的构建版本号,该版本号标识捆绑包的迭代(已发布或未发布)。构建版本号应该是一个由三个非负的,周期分隔的整数组成的字符串,第一个整数大于零。该字符串应仅包含数字(0-9)和句点(。)字符。前导零从每个整数中截断,将被忽略(即1.02.3相当于1.2.3)。这个密钥不可本地化。

CFBundleVersion (String - iOS, OS X) specifies the build version number of the bundle, which identifies an iteration (released or unreleased) of the bundle. The build version number should be a string comprised of three non-negative, period-separated integers with the first integer being greater than zero. The string should only contain numeric (0-9) and period (.) characters. Leading zeros are truncated from each integer and will be ignored (that is, 1.02.3 is equivalent to 1.2.3). This key is not localizable.

我只为我的应用程序使用了外部测试人员,因此我无法确认内部测试人员的问题与此帖子相同:内部Testflight构建未安装挂起率为90%

I only used external testers for my app, so I’m not able to confirm this be the same issue for internal testers as in this post: Internal Testflight build not installing hangs at 90%

这篇关于Testflight外部用户下载卡在90%的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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