Fix iPhone IPA signing and verification errors
First identify whether the problem affects one IPA or every signed app. A wrong UDID, missing provisioning profile, incorrect .p12 password, expired or revoked certificate, or incompatible IPA can produce similar messages. A new certificate is not always necessary.
Unable to install app
Likely cause: The IPA was signed for a different device, the provisioning profile is missing, or the IPA itself is incompatible.
Fix: Confirm the UDID used for the certificate is the same iPhone or iPad you are installing on. Re-sign the IPA with both the .p12 certificate and the .mobileprovision profile.
Unable to verify app
Likely cause: iOS cannot verify the developer profile, the device is offline, or the certificate was revoked or expired.
Fix: Connect to the internet and check the app-management/trust prompts shown by your iOS version. If verification still fails, check certificate and provisioning profile validity and whether the profile contains this device UDID.
Integrity Could Not Be Verified
Likely cause: iOS cannot validate the signed app package. Possible reasons include a revoked or expired certificate, a profile/UDID mismatch, or a damaged IPA.
Fix: Check the certificate and profile validity, confirm the registered device UDID, and re-sign a known-compatible IPA before deciding that you need new certificate files.
Wrong certificate password
Likely cause: The .p12 password was copied incorrectly, or the signer is asking for the certificate password and not your Apple ID password.
Fix: Copy the password from your CertDrop email or install page exactly. The password is case-sensitive.
No provisioning profile found
Likely cause: Only the .p12 file was imported. Signers like ESign and Feather also need the .mobileprovision file.
Fix: Import both files: the .p12 certificate and the .mobileprovision profile. Then restart the signer app and try again.
App opens then closes immediately
Likely cause: The app may be incompatible with your iOS version, missing entitlements, modified incorrectly, or blocked by iOS.
Fix: Try a different IPA build first. If other signed apps work, the certificate is probably fine and the issue is with that IPA.
ESign signs with the wrong certificate
Likely cause: Multiple signing identities are imported and ESign selects an older, expired, or incompatible entry.
Fix: Verify that the intended .p12 and .mobileprovision were imported together, and explicitly select the matching signing identity before trying a different IPA.
Feather or ESign does not show the certificate
Likely cause: One of the files was not imported, or the signer app did not refresh its certificate list.
Fix: Import the .p12 and provisioning profile again, enter the password, then fully close and reopen the signer.
When should you buy a replacement certificate?
Check before paying: If only one IPA fails, test a known-compatible IPA and verify its iOS version and entitlements. If the certificate is still valid but a download link expired, use CertDrop Redownload or contact support rather than buying again.
A new package may be appropriate: The certificate or provisioning profile is truly expired, revoked, or registered for a different device. A replacement purchase does not guarantee that an incompatible IPA will work.
Check your setup before you lose time.
Use the free CertDrop tools to check certificate files, IPA compatibility, and iPhone setup steps before ordering or signing.
Common CertDrop installation fixes
Feather pauses, stops halfway, or stays on Ready
Open Feather → Settings → Installation Method and select Semi Local. Then return to your CertDrop install page and try the installation again.
Trying to install the certificate through iPhone Settings
Do not install the raw .p12 or .mobileprovision files directly through iPhone Settings. If your private CertDrop page offers Install Feather or Install ESign, use that prepared option. For manual setup, import both files from inside Feather, ESign, or another compatible signer.
Wrong certificate password
The password requested by Feather, ESign, or another signer is the certificate .p12 password shown in your CertDrop delivery email or private install page. It is not your Apple ID password.
Developer Mode is required
Open Settings → Privacy & Security → Developer Mode, enable it, restart the iPhone if prompted, then confirm Developer Mode after the restart.
If the problem continues, contact CertDrop support with the exact error message or a screenshot.