Common iOS sideloading and IPA signing errors
Most sideloading problems come from the same few places: wrong UDID, missing provisioning profile, incorrect .p12 password, revoked certificate, expired certificate, or an incompatible IPA file.
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, then go to Settings and trust the developer profile. If verification still fails, check whether the certificate has expired or been revoked.
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.
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.