We have a MacOS app that we distribute outside of the App Store. The App has an embedded provisioning profile that is still valid. We would like to add the Associated Domains capability to the app ID. Does that require regenerating a new provisioning profile and embedding it into a new version of App? If we do that, does that mean that the old provisioning profile will become invalid and the old Apps that are still running with it will stop working? Is there a way to make the transition to the new provisioning profile smooth without any downtime?
When you edit your App ID to add new entitlements you will be presented with a warning that it will invalidate existing provisioning profiles. This will not impact any distributed apps. For example any time you add a capability in Xcode with automatic signing it is making requests to update the app id configuration and generate a new profile when required. We are tracking an enhancement to update this messaging. The website marks profiles as “invalid” to indicate they do not feature the latest App ID configuration or available device configuration for the team.
I hope this clarifies and we are tracking verbiage changes for that type of update to make the effect and recommended follow up action clearer.
As a reminder revoking any certificates for directly distributed apps can impact their functionality so always take caution before revocation.