Resigning
Resigning is the process of modifying an existing binary with a new signing certificate or keystore, which is required when an application needs to be published under a different developer account or when updating an existing application. It involves removing the original signature and replacing it with a new one.
Resigning iOS Binaries
To sign an iOS binary, you need a valid certificate and provisioning profile. Appcircle supports both IPA and xcarchive files. The process of signing an iOS binary involves selecting the correct certificate and provisioning profile and specifying the bundle identifier and version number. Once these details are entered, Appcircle will generate a new signed binary with the updated information.
iOS Resign Process
- Select the binary.
You can either select the files from the list or upload IPA, xcarchive files by clicking the Upload New Version button at the bottom.
- Click the... button and select Resign Binary
This form will show the following details of the original binary.
Display Name
CFBundleDisplayName: The user-visible name for the bundle, used by Siri and visible on the iOS Home screen.
Version
CFBundleShortVersionString: The release or version number of the bundle.
Build Number
CFBundleVersion: The version of the build that identifies an iteration of the bundle.
Entitlements
- Entitlements from provisioning profiles
Use entitlements from the new provisioning profile
- Combine app entitlements
Extract app bundle codesigning entitlements and combine them with entitlements from new provisioning
- New Entitlements.
You can edit this XML file to edit capabilities. Resigning process uses a single entitlement XML file.
If your provisioning profiles have the correct entitlements set, using the first option is the safest option.
Targets
You need to select new provisioning profiles for each target. Bundle ids will be automatically populated when you select a new provisioning profile. However, if you use a wildcard provisioning profile, you may need to write the correct bundle id for the selected target.
You must select a provisioning profile for each target. Otherwise resigning will fail.
- Fill in the details for resign process and hit the Sign button
Resigning Android Binaries
To sign an Android binary, you need a valid keystore file. Appcircle supports both APK and AAB files. The process of signing an Android binary involves selecting the correct keystore file. Once these details are entered, Appcircle will generate a new signed binary with the updated information.
- Select the binary.
You can either select the files from the list or upload APK, and AAB files by clicking the Upload New Version button at the bottom.
- Click the... button and select Resign Binary
This form will show the following details of the original binary.
- Select the correct keystore and click the Sign button to sign your binary. You may also change the Package ID, Version Name and Version Code.
Binary Details
- Select the binary.
You can either select the files from the list or upload binaries by clicking the Upload New Version button at the bottom.
- Click the... button and select Binary Details
- This window will show basic information about your binary.
Resign History
- Select the binary.
You can either select the files from the list or upload binaries by clicking the Upload New Version button at the bottom.
- Click the... button and select Resign History
- Each signing process will be listed for that binary. If you click the View Log button, you can get more details about the process.
You need the check the history of the original application that has been signed.