简体   繁体   English

企业内部应用分发

[英]Enterprise In-House App distribution

I'm developing an iPad application for a company.我正在为一家公司开发 iPad 应用程序。 Because of confidentiality reasons they do not want to publish the app to the app-store.由于保密原因,他们不想将应用发布到应用商店。

The fulfill the enterprise program requirements but they have not participated yet.满足企业计划要求,但尚未参加。 The company wants to know how the distribution process is.公司想知道分销流程是怎样的。 I've dived into apples documentation jungle and i'm a little confused about the provisioning profiles.我已经潜入苹果文档丛林,我对配置文件有点困惑。 Due to the confidentiality reasons I'd like to use the apple security api using DeviceLock with configuration profiles so I came across with MDM-Servers.由于保密原因,我想使用带有配置文件的 DeviceLock 的苹果安全 api,所以我遇到了 MDM 服务器。

Now my actual question: Do I still need the UDID of every Device I want to use with enterprise program AND if yes, can I push new provisioning profiles (with new devices) to all existing devices via MDM-Server without recompiling and redistribute the whole app?现在我的实际问题是:我是否仍然需要我想与企业程序一起使用的每个设备的 UDID,如果是,我是否可以通过 MDM 服务器将新的配置文件(带有新设备)推送到所有现有设备,而无需重新编译和重新分发整个应用程序?

You definitely don't!你绝对没有!

You can distribute the app via您可以通过以下方式分发应用程序

  • In-House Distribution: Building with that profile will create an .ipa and a .plist file.内部分发:使用该配置文件构建将创建一个 .ipa 和一个 .plist 文件。 You put that on a website that is protected via basic authentication.你把它放在一个通过基本身份验证保护的网站上。 Put a link to the plist file on the site in the below format.按照以下格式在站点上放置指向 plist 文件的链接。 Then you can just browse to that site with any ios-device, type in your credentials, click on the link and install the app.然后,您可以使用任何 ios 设备浏览到该站点,输入您的凭据,单击链接并安装该应用程序。
 <a href="itms-services://?action=download-manifest&url=http://myDomain.de/path/to/the/MyApp-Version.plist">Download my cool App!</a>
  • Ad-Hoc Distribution (Also possible with Developer Program for Beta-Testing up to 100 devices): Here you use device-ids. Ad-Hoc 分发(也可以使用开发人员计划对多达 100 台设备进行 Beta 测试):在这里您使用设备 ID。 You build the app and get an .ipa and a .mobileprovision file (a certificate needed to install the app).您构建应用程序并获得 .ipa 和 .mobileprovision 文件(安装应用程序所需的证书)。 You send those 2 files to a customer and he installs it via itunes (not sure if he can open it directly from the mail on the device).您将这 2 个文件发送给客户,然后他通过 iTunes 安装它(不确定他是否可以直接从设备上的邮件打开它)。

I'm not sure you need the UDID of each device in the enterprise program.我不确定您是否需要企业程序中每个设备的 UDID。 This answer seems to imply you don't need to. 这个答案似乎暗示你不需要。

You definitely can push a new provisioning profile without re-compiling.您绝对可以在不重新编译的情况下推送新的配置文件。

You'll also have to plan on updating the certificates each year, see:您还必须计划每年更新证书,请参阅:

An app will not run if the distribution certificate has expired.如果分发证书已过期,应用程序将不会运行。 Currently, distribution certificates are valid for one year.目前,分发证书的有效期为一年。 A few weeks before your certificate expires, request a new distribution certificate from the iOS Dev Center, use it to create new distribution provisioning profiles, and then recompile and distribute the updated apps to your users.在您的证书到期前几周,从 iOS 开发人员中心申请新的分发证书,使用它来创建新的分发配置文件,然后重新编译并将更新的应用程序分发给您的用户。

Source: http://developer.apple.com/library/ios/#featuredarticles/FA_Wireless_Enterprise_App_Distribution/Introduction/Introduction.html来源: http : //developer.apple.com/library/ios/#featuredarticles/FA_Wireless_Enterprise_App_Distribution/Introduction/Introduction.html

With Enterprise distribution program, you can sign your app with In-House distribution certificate which doesn't require UDIDs.使用企业分发程序,您可以使用不需要 UDID 的内部分发证书对您的应用程序进行签名。 That app can be installed on any iOS device and provisioning profile is embedded in the App.该应用程序可以安装在任何 iOS 设备上,并且配置文件嵌入在应用程序中。 For the apps already written and distributed using AdHoc builds you can codesign .app using codesign tool in your mac to sign the app using in-house certificate and convert to ipa.对于已经使用 AdHoc 构建编写和分发的应用程序,您可以使用 mac 中的协同设计工具对 .app 进行协同设计,以使用内部证书对应用程序进行签名并转换为 ipa。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM