My iOS Provisioning Profile will expire soon and I need to know the smoothest way to renew that profile. My certificate doesn't expire for another couple of years, so the certificate itself should be fine.It is an in-house (non-App Store) app and is installed on a number of devices.
我的iOS配置文件很快就会过期，我需要知道更新该配置文件的最流畅的方法。我的证书在未来几年内不会过期，因此证书本身应该没问题。它是一个内部（非App Store）应用程序，并安装在许多设备上。
Which is why I'm wondering if the app will stop working if I do the following:
这就是为什么我想知道如果我执行以下操作，应用程序是否会停止工作：
- Let the provisioning profile expire.
- 让配置文件到期。
- Click generate inside the existing profile.
- 单击现有配置文件中的生成。
If so, is there any way to update/renew the profile without taking down the app or releasing a new version? If I have to release a new version, is the best option to create a new profile to reduce downtime?
如果是这样，有没有办法在不删除应用程序或发布新版本的情况下更新/续订配置文件？如果我必须发布新版本，是创建新配置文件以减少停机时间的最佳选择吗？
1 个解决方案
#1
2
So generating a new provisioning profile will not invalidate any of the apps out there on devices. Basically, you should choose option 2. Generate the new provisioning profile, build a new version of the app with the new provisioning profile, and just make sure all your users / testers update to the new version of the app.
因此，生成新的配置文件不会使设备上的任何应用程序无效。基本上，您应该选择选项2.生成新的配置文件，使用新的配置文件构建新版本的应用程序，并确保所有用户/测试人员都更新到新版本的应用程序。
Alternatively, you could generate the provisioning profile and then distribute the profile to all the devices through MDM (if you're using an MDM solution) or by email (not a great experience). Basically the app will continue to run as long as the new provisioning profile gets on the device before the old one expires, whether that's through MDM, manually, or by installing a new version of the app with the provisioning profile in the .app payload. Or if your users download any app with the new provisioning profile, assuming that provisioning profile is set up with a wildcard app ID, that will also correct it (see information about that here: https://*.com/a/29121777/3708242).
或者，您可以生成配置文件，然后通过MDM（如果您使用的是MDM解决方案）或通过电子邮件（不是很棒的体验）将配置文件分发到所有设备。基本上，只要新设置配置文件在旧设备到期之前到达设备，无论是通过MDM，还是通过在.app有效负载中安装配置文件的新版本的应用程序，应用程序将继续运行。或者，如果您的用户使用新的配置文件下载任何应用程序，假设配置文件设置了通配符应用程序ID，这也将更正它（请参阅此处的信息：https：//*.com/a/29121777/ 3708242）。
But option 1 will certainly result in your app refusing to launch once the expiration date arrives.
但是选项1肯定会导致您的应用程序在到期日期到来后拒绝启动。
#1
2
So generating a new provisioning profile will not invalidate any of the apps out there on devices. Basically, you should choose option 2. Generate the new provisioning profile, build a new version of the app with the new provisioning profile, and just make sure all your users / testers update to the new version of the app.
因此，生成新的配置文件不会使设备上的任何应用程序无效。基本上，您应该选择选项2.生成新的配置文件，使用新的配置文件构建新版本的应用程序，并确保所有用户/测试人员都更新到新版本的应用程序。
Alternatively, you could generate the provisioning profile and then distribute the profile to all the devices through MDM (if you're using an MDM solution) or by email (not a great experience). Basically the app will continue to run as long as the new provisioning profile gets on the device before the old one expires, whether that's through MDM, manually, or by installing a new version of the app with the provisioning profile in the .app payload. Or if your users download any app with the new provisioning profile, assuming that provisioning profile is set up with a wildcard app ID, that will also correct it (see information about that here: https://*.com/a/29121777/3708242).
或者，您可以生成配置文件，然后通过MDM（如果您使用的是MDM解决方案）或通过电子邮件（不是很棒的体验）将配置文件分发到所有设备。基本上，只要新设置配置文件在旧设备到期之前到达设备，无论是通过MDM，还是通过在.app有效负载中安装配置文件的新版本的应用程序，应用程序将继续运行。或者，如果您的用户使用新的配置文件下载任何应用程序，假设配置文件设置了通配符应用程序ID，这也将更正它（请参阅此处的信息：https：//*.com/a/29121777/ 3708242）。
But option 1 will certainly result in your app refusing to launch once the expiration date arrives.
但是选项1肯定会导致您的应用程序在到期日期到来后拒绝启动。