Provisioning profiles change for two different reasons: the data on the profile is stale (a device was added, a capability was toggled, the signing certificate was rotated) or the profile expired and Apple needs to re-issue it. HexSign separates the two.
Update — small changes, same expiry
Updating a profile is the right tool when the underlying signing certificate is unchanged but the embedded data needs to move: a new device was registered, a capability was toggled on or off, or the profile name should change. Apple keeps the original expiration date.
Regenerate — fresh expiry, fresh data
Regenerating asks Apple to re-issue the profile from scratch. The new profile gets a new expiration date and is signed with whichever certificate you pick during the regenerate flow. This is the right tool when a certificate has been rotated, the profile has expired, or the profile is in an invalid state.
Roll the new version out
- Click Download .mobileprovision on the profile's detail page.
- Drop the file into the directory your CI expects (or update the secret in your secrets manager).
- If teammates have the profile installed locally, they can re-download it from HexSign or run their build once and let Xcode pick it up automatically from the connected Apple ID.