App opens and immediately crashes

An immediate crash means installation and basic verification got farther than an integrity failure. Stop changing certificates and investigate runtime compatibility.

Common causes

• The executable is still encrypted for App Store FairPlay delivery.
• A framework, dylib, resource, or nested bundle is missing or signed incorrectly.
• An injected tweak expects a jailbroken substrate or different hooking environment.
• The app requires JIT and did not receive it.
• The app was built for an unsupported architecture or minimum OS.
• A changed bundle ID broke keychain, App Groups, URL schemes, or service assumptions.
• The app detects modification, jailbreak state, or unsupported distribution.
• A LiveContainer guest expects capabilities the host cannot provide.

Isolation sequence

1. Try the same IPA with no injected tweaks.
2. Obtain a clean build from the primary developer.
3. Preserve the crash and signer logs.
4. Confirm executable and framework architectures.
5. Compare entitlements with the profile.
6. If JIT is required, verify helper and app support for the exact OS.
7. Test a known-good IPA with the same signing pair.

Sideloadly notes that an encrypted IPA copied from App Store delivery cannot be repaired merely by re-signing (Sideloadly).

Do not delete the old working version to test a new build. Use a disposable bundle ID or make an app-supported export first.