您的 iPhone Beta 应用程序是否使用不同的应用程序 ID？
我们这些拥有 iPhone 应用程序（已发布或未发布）的人能够使用临时分发来发送有限的测试版本。 虽然苹果文档中存在一些漏洞，但“网络”上有许多博客、帖子和其他文章可以填补这些空白。
然而，有一件事我没有看到任何人提到，我很好奇：当你进行测试版构建时，你是否使用与已发布（或即将发布）应用程序相同的应用程序 ID？
使用不同 ID 的理由是，测试版仍然可以与已发布的应用程序一起运行。 如果您已经有该领域的发布版本，这可能更重要。
反对的一个论点是，测试版将无法访问已发布的应用程序可能生成的任何数据，反之亦然。 根据具体情况，这可能是也可能不是您想要的。
这种方法有什么问题吗？ 我目前只注册了一个应用程序 ID，但是 IIRC 没有任何障碍，可以根据需要创建更多应用程序 ID..？
有兴趣听听其他人在做什么。
Those of us with iPhone apps (released or unreleased) are able to send out limited beta builds using ad-hoc distribution. While the Apple docs for this have a few holes in them, there are a number of blogs, postings and other articles out there on "the net" that fill the gaps.
However, one thing I haven't seen anyone mention, and I was curious about: When you do a beta build do you use the same app id as your released (or to-be-released) app?
The argument for using a different id is that the beta could then still run alongside the released app. This is probably more important if you already have a released version in the field.
An argument against is that the beta would not have access to any data the released app may have generated, and vice -versa. This may or may not be what you want on a case-by-case basis.
Are there any issues with this approach? I only have one app id registered currently, but IIRC there are no obstacles to just creating more as necessary..?
Would be interested to hear what others are doing.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
为了简单起见，我们使用相同的应用程序 ID。 临时分发中有很多令人头疼的问题，我们不想让任何人对“为什么我的手机上有两个应用程序？”感到困惑。 问题。
We use the same app ID, just for simplicity. There are enough headaches in ad-hoc distribution that we don't want to confuse anybody with "why are there two apps on my phone?" problems.
我使用两种不同的捆绑包标识符，以允许我的测试团队安装应用程序的多个版本以及不同的捆绑包显示名称，这样他们就可以轻松地看到他们正在使用开发或测试版本，并在出现问题时将该数字报告给我被发现。
I use both different Bundle Identifiers to allow my testing team to have multiple versions of the app installed as well as different Bundle Display NAmes, so they can easily see that they are using a development or beta build and report that number back to me when issues are found.
我认为这取决于应用程序中数据的重要性。 如果数据很有价值，我认为 Beta 测试人员不会希望它面临风险，因此拥有一个单独的 AppID 是有意义的。 当然，这也意味着他们也不会完全测试应用程序，并且任何“升级”代码都不会得到测试。
就我而言（Yummy），数据只是美味网站的缓存，因此我的代码中的灾难性错误将意味着，最糟糕的是，再次下载所有书签。 所以我倾向于对所有事情使用相同的 AppID。
I think it depends on how important the data in your app is. If the data is valuable I don't think beta testers would want it putting at risk, hence having a separate AppID would make sense. Of course, that also means that they won't test the application as fully either and any "upgrade" code won't get tested.
In my case (Yummy), the data is just a cache of delicious.com so a catastrophic bug in my code would mean, at worse, downloading all your bookmarks again. So I tend to use the same AppID for everything.