差异:Ad Hoc分布和发展分布 [英] Difference: Ad Hoc distribution and Developmental distribution

查看:166
本文介绍了差异:Ad Hoc分布和发展分布的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在创建我的第一个应用,并对Ad Hoc配置配置文件和开发配置配置文件感到困惑。我知道在此之前会问这个问题但是需要一些澄清和确认。

I am in process of creating my first app and have some confusion over Ad Hoc provisioning profile and Development Provisioning profile. I understand that this question is asked before this but needed some clarification and confirmation.

查看stackoverflow上的先前答案我假设存在以下差异:

Looking at previous answers on stackoverflow I assume there are following differences:


  1. 可以在没有iTunes的情况下安装Ad hoc版本,而必须从iTunes安装开发版本(.ipa)

  1. Ad hoc builds can be installed without iTunes while development builds(.ipa) must be installed from iTunes

当开发构建有调试器时,调试器无法附加到Ad hoc构建

Debugger cannot be attched to Ad hoc build while development build has debugger

设备令牌不同,因为APNS使用两种模式沙箱,生产取决于构建的环境是临时或发展

Device tokens are different as APNS uses two modes sandbox, production environments depending upon build is Ad hoc or developmental

我有以下问题


  1. 在许多论坛上都写到,Ad hoc版本上有100个用户,但没有提到如果开发版本有这样的限制。 100个用户的这些限制是每个开发人员配置文件还是每个应用程序?

  1. On many forums it is written that there is limit of 100 users on Ad hoc builds but nothing is mentioned that if developmental builds have such limits. Also these limits of 100 users are per developer profile or per application?

此外,只有Ad hoc版本需要在其上安装设备的UDID吗?发展构建怎么样?

Also does only Ad hoc builds require UDIDs of device to get installed on them? what about developmental builds?

请查看我是否有正确的差异,这是否会遗漏任何重要的差异,任何有关问题的信息都会有很大的帮助

Please see if I have got differences correctly, whether this misses any important difference and any information on questions will be of immense help


推荐答案

扩大您的评论


  1. Ad Hoc版本可以通过iTunes,X Code组织者或网络进行分发和安装。用于管理adhoc构建和测试的一项服务是Testflight(https://testflightapp.com/),检查它们有很多关于供应配置文件的资源,

  1. Ad Hoc builds can be distributed and installed though iTunes, the X Code organizer or though the web. One service for managing adhoc builds and testing is Testflight (https://testflightapp.com/) check them out they have lots of resources regarding provision profiles,

通常,您的分发版本会在调试信息被剥离的情况下进行优化,所以是的,您无法调试adhoc&分发在调试器中构建。

Normally your distribution builds are optimized with debugging information stripped, so yes you can not debug adhoc & distribution builds in the debugger.

您的应用程序ID已链接到APNS,因此您生成的证书将链接到您的应用程序。沙箱和生产中的设备令牌是不同的。

Your App ID is linked to APNS, so the certificate you generate is linked to your application. Device tokens on Sandbox and production are different.

回答你的问题


  1. 对于您的iOS开发者个人资料,您在整个帐户中限制为100台设备。这些在应用程序之间共享。 100个设备意味着您每年可以为每个开发者帐户注册100个设备。在您续订帐户的年末,您可以编辑此列表并重置设备配额。

  1. for your iOS developer profile you're limited to 100 devices across the entire account. These are shared between applications. 100 devices means that you are allowed to register 100 devices per developer account per year. At the end of the year when you renew your account you can edit this list and reset your device quota.

临时构建和开发人员构建都需要您的UDID 。会发生的情况是,配置文件(开发或adhoc)必须与应用程序签名的配置文件相匹配。在开发中,通常最简单的方法是使用通配符App ID(例如*),但是当您发布时(在ad hoc或app store分发下),您应该使用完整的App ID名称,例如com.company.appname,这是为了识别您的应用程序购买或推送通知服务等服务中的应用程序

Both ad hoc builds and developer builds require your UDIDs. What happens is that the provision profile (development or adhoc) must match the provision profile that the app was signed against. Under development it's usually easiest to use a wildcard App ID (such as *) but when you are releasing (under ad hoc or app store distribution) you should use the full App ID name such as com.company.appname this is to identify your app under services such as In app purchases or Push notification services

这篇关于差异:Ad Hoc分布和发展分布的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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