ForgeSign Support
ForgeSign is a calm, on-device IPA signing workflow for iPhone and iPad. Pick an .ipa, a .p12 certificate, and a .mobileprovision profile, see the preflight signals, then sign with the vendored zsign engine. Sources, optional dylib injection, remembered certificates, a signed-app library, and loopback OTA install keep the whole workflow on your device.
Support
Common Topics
No. Signing runs on the device. Certificates and profiles stay in the app container. Install uses a loopback HTTP server on the phone plus a trusted HTTPS plist to drive itms-services — the IPA itself is not uploaded to a third-party storage service by ForgeSign.
No. ForgeSign-2.1.ipa ships unsigned on purpose. Sign it with your own certificate and profile (with ForgeSign itself after a first install via another tool, or with Sideloadly / AltStore / similar).
Deployment target is iOS 16. Liquid Glass styling uses iOS 26+ APIs when available, with a material fallback on earlier versions.
Yes. Set an optional new bundle ID before signing. You can also strip app extensions or enable Files import / sharing.
Yes, as an explicit opt-in. Use a compatible, decrypted Mach-O dylib and enable app-extension injection only when the input needs it. ForgeSign prepares a disposable IPA copy before the existing signer runs and leaves the original input untouched.
Version 2.1 adds an Open in ForgeSign quick action to IPA previews in Files and loads the selected archive directly into the signing workflow.
No. Only sign and install applications you have the rights to modify. ForgeSign is intended for your own builds and development use.