Certificate and provisioning identifiers are redacted in the Sign preview.
## Features - **Sign IPAs on-device** — pick an `.ipa`, a `.p12` certificate and a `.mobileprovision` profile, optionally rewrite the bundle ID, strip app extensions or enable Files sharing, and sign in seconds with the vendored zsign engine. - **Remembered certificates** — imported `.p12` files are validated once and stored on-device (Application Support). The last-used certificate is re-selected automatically. - **Certificate insights** — common name, organization and team ID are parsed from the certificate, and a live countdown pill shows remaining validity (`200d left`, amber under 30 days, red when expired). - **Keychain passwords** — opt-in password storage in the iOS Keychain (with an encrypted-file fallback when the Keychain is unavailable), so re-signing takes two taps. - **Install on device** — semi-local OTA install: the IPA is served over loopback HTTP while a trusted remote HTTPS plist (`api.palera.in`) drives `itms-services` directly (Safari is a fallback only). Silent-audio keep-alive keeps large downloads alive in the background. - **Library** — a persistent history of every signed app with status (signed / installing / installed / missing), plus reinstall, share and delete actions. - **IPA preflight** — package, bundle, encryption and architecture signals are shown before a signing run. - **Sources** — save repository feeds and hand selected IPA downloads into the normal signing flow. - **Optional dylib injection** — inject a compatible decrypted dylib into the app, with an opt-in app-extension path, before signing. The original IPA is left untouched. - **Glass design language** — lighter translucent cards, ambient color blooms, Liquid Glass on iOS 26+ with a material fallback back to iOS 16, light and dark themes. ## Requirements - Xcode 26+ (the build needs the iOS 26 SDK for the Liquid Glass APIs; deployment target is iOS 16) - [XcodeGen](https://github.com/yonaskolb/XcodeGen) (`brew install xcodegen`) - iOS 16.0+ on device ## Build from source ```bash xcodegen generate open ForgeSignMobile.xcodeproj ``` Build the `ForgeSignMobile` scheme for a device. Code signing is disabled in the project settings by design — sign the produced app with your own certificate and profile (ForgeSign desktop can do it, or any sideloading tool). ## Sideload the prebuilt IPA Grab `ForgeSign-1.1.ipa` from the [1.1 release](https://github.com/Mesutcydev/ForgeSign-iOS/releases/tag/v1.1). The IPA ships **unsigned** — that is the point of the app: sign it like any other IPA. 1. Download the IPA. 2. Sign it with your certificate + provisioning profile — e.g. with ForgeSign (desktop or the iOS app itself), Sideloadly, AltStore or a similar tool. 3. Install the signed IPA on your device. Only sign and install applications you have the rights to modify. Intended for your own builds and development use. ## What’s new in 1.1 - Preflight card for package, bundle, encryption and architecture checks. - Optional dylib injection with app-extension support for compatible decrypted Mach-O inputs. - Sources tab with repository feeds and direct IPA handoff. - Lighter glass surfaces and refreshed dark-mode screens.    ## How it works 1. Picked files are staged into the app container. 2. The zsign engine (`Bridge/`) re-signs the Mach-O binaries, injects the profile and rewrites metadata, producing `