Why your old sideloading certificate does not transfer to a new iPhone
When you replace an iPhone, the new device has its own UDID. The provisioning profile from the old device was prepared for the previous UDID, so it does not automatically authorize the new iPhone.
The important device match lives in the provisioning profile. Your old mobileprovision file still refers to the previous device registration. Use the new iPhone UDID for the replacement certificate package.
The certificate package is device-matched
CertDrop prepares the certificate package for the UDID submitted with the order. The package includes the .p12 certificate, matching mobileprovision profile, and password. For registered-device sideloading, the target iPhone must be included in that provisioning profile.
What changes when you buy a new iPhone
- The new iPhone has a different UDID from the previous device.
- The old mobileprovision profile does not automatically add that new UDID.
- A package prepared for the old iPhone therefore remains matched to the old device registration.
What to do instead
- Capture the UDID from the new iPhone using the CertDrop UDID tool or another method described in the UDID guide.
- Order a new device-matched certificate package using that UDID.
- Use the certificate files from the new device-matched package in your signing workflow.
- If you use ESign or Feather, use the new files or the prepared install options on the new CertDrop install page.
Upgrading to iPhone 18 Pro or Pro Max?
CertDrop has a dedicated iPhone 18 Pro / Pro Max certificate page that takes you directly to the device-matched $8 order flow.
Frequently asked questions
Why does the old certificate package fail on the new iPhone?
The old provisioning profile was prepared for the previous device UDID. The new iPhone is a different registered device.
Can I edit the old mobileprovision file and add the new UDID?
No. A provisioning profile needs to be generated correctly through Apple developer signing infrastructure.
Do I need a new package even if I still have the old .p12?
For the CertDrop device-matched workflow, a different iPhone requires a package prepared for that device so the provisioning profile includes the correct UDID.