When AppTesters issues a renewed or replacement certificate, apps signed with the previous certificate do not automatically switch to the new one. You must import or select the new certificate, sign fresh copies of your IPAs, and install those newly signed apps.

The wording in ESign can vary slightly by version, but the process is generally the same.

Before you begin

  • Download the new .p12 and .mobileprovision files supplied for your device, if your plan uses downloadable files.
  • Confirm that both files belong to the same replacement package.
  • Keep the .p12 password available.
  • Back up important app data before removing or replacing any app.

Import the replacement certificate

  1. Open ESign.
  2. Go to the certificate or file section and import the new .p12 file.
  3. Enter the password supplied with the certificate package.
  4. Import the matching .mobileprovision file.
  5. Confirm that ESign shows the new certificate as available for signing.

Sign and install a fresh app copy

  1. Import the original IPA into ESign.
  2. Open the signing screen.
  3. Select the newly imported certificate and matching provisioning profile.
  4. Review the bundle identifier and any required entitlements.
  5. Sign the IPA and install the newly signed copy.

If iOS will not install the new copy over the old one, back up the app's data and remove the old app before installing again. Uninstalling can delete data stored only inside the app.

If the replacement is Active but signing fails, confirm that you did not mix old and new certificate files. Contact support with the exact ESign error if the problem continues; do not send certificate files through a public channel.