Ad Hoc Distribution - 它是否会更新应用程序的现有先前安装版本？
当用户安装现有应用程序的临时发行版时会发生什么？如果这个应用程序（或更新的应用程序）正式登陆 App Store 会发生什么？
总结一下：
- 用户已经拥有 v1.0 并收到 v2.0 ad hoc
- 用户拥有 ad hoc v2 .0 和 v2.0 的官方公开版本登陆商店
- 用户拥有 ad hoc v2.0 并且 v3.0 的官方公开版本登陆商店
换句话说，
是 ad hoc 版本的独立版本单独构建还是实际上按照更新的预期更新了以前的版本？新版本上架后是否会立即更新？
What happens when a user installs an ad hoc distribution of an existing app? And what happens if this app (or a newer one) hits the App Store officially?
To sum it up:
- A user already has a v1.0 and receives a v2.0 ad hoc
- A user has the ad hoc v2.0 and the official public release of v2.0 hits the store
- A user has the ad hoc v2.0 and an official public release of v3.0 hits the store
In other words,
is the ad hoc version a stand-alone build or does it in fact update a previous version as expected from an update? And will it be updated as soon as a newer version hits the store?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
对此我没有答案；我猜它会覆盖。
当应用程序本身进入应用程序商店时，什么也不会发生（例如，没有通过 App Store.app 发出“更新”通知）；但是，如果用户安装了 App Store 发行版。之前的 Ad Hoc 安装消失了。我使用没有本地存储的应用程序执行此操作，因此我不确定是否会保留任何本地文件（例如，应用程序是否将内容保存到其沙箱目录）。
我的免责声明：我在 SDK3.0 之前就这样做了。我有专门的 beta 测试人员，我会通过电子邮件发送测试版本。随后，几名测试人员通过促销代码获得了正式版本。
希望这有帮助。
-斯科特·H
I don't have an answer for this; I would guess it overwrites.
Nothing happens when the app hits the app store per-se (e.g. no 'update' notice via App Store.app); however if the user installs the App Store distrib. the previously Ad Hoc install goes away. I did this with an app without local storage so I'm not sure if any local files would be retained (e.g. if the app saves content to its sandbox dir).
My disclaimer: I did this prior to SDK3.0. I had ad-hoc beta testers that I would e-mail test builds. Several testers were then given the official release via promo codes.
Hope this helps.
-Scott H
即使分布式应用程序完全相同，例如相同的可执行文件，由于两个版本不同，每个版本也应该具有不同的版本号。因此，如果您临时发布了 2.0，然后发布了正式版本，则出于组织和清晰度的目的，该版本应该有所不同，例如 2.0.1。您将知道客户是否引用版本 2.0，即为临时版本，如果版本是 2.0.1，即为正式版本，无需进一步信息。总之，每个单独的版本都应该有一个单独且唯一的修订号。
Even if the distributed application is entirely the same, for example the same executable, since both realeases are different, each release ought to have a different version number. So if you released 2.0 ad hoc, and then released official version, that version ought to be different, for example 2.0.1, for organizational and clarity purposes. You will know if the customer refers to version 2.0 that that is an ad hoc version, and if the version is 2.0.1 that is the official version without requiring further information. In summary, each individual release should have an individual and unique revision number.