Fix “Requires a Newer Version of iOS” When Installing an IPA
You try to install an IPA file and it fails with a message that the app needs a newer version of iOS than your iPhone runs. This is one of the few install errors with a single, clear cause: the app itself says which iOS it needs, and your device is below that. This guide explains where that number comes from, how to check it, the fixes that work, and the shortcut that often does not.
The Short Version
- Every app states the oldest iOS it supports in a setting called MinimumOSVersion.
- If your iOS is older, the install is refused. The real fixes are to update iOS, if your iPhone can, or to find an older build of the app made for your iOS.
- Tools can lower the number inside the IPA. That only removes the check. If the app uses features from the newer iOS, it can crash when it opens, and the edited IPA has to be signed again.
What the Error Means
Apple describes MinimumOSVersion as “the minimum version of the operating system required for the app to run in iOS, iPadOS, tvOS, and watchOS.” Developers do not usually type it in by hand: Apple says Xcode fills it in from the app’s Deployment Target. So the number reflects the oldest iOS the developer built and tested the app for.
The exact wording of the error depends on the tool you install with. AltStore and SideStore, for example, use messages such as “[App] requires iOS 17.0 or later.” or “This device is running iOS 16.7, but [App] requires iOS 17.0 or later.” Other installers may only say the install failed. If you see a version number in the message, compare it with your own iOS in Settings > General > About.
A few apps also set a maximum version. AltStore shows “[App] requires iOS [version] or earlier” in that case. The fixes below work the same way, just in the other direction.
How to Check Which iOS an IPA Needs
You can read the number yourself before installing anything:
- Make a copy of the IPA file and rename the copy from
.ipato.zip. An IPA is a zip archive. - Open the zip and go to
Payload/, then into the folder ending in.app. - Open
Info.plistand look forMinimumOSVersion. On a Mac,plutil -p Info.plistin Terminal prints it, even if the file is in binary form.
For more on what sits inside an IPA, see understanding IPA files.
Fix 1: Update iOS, If Your iPhone Can
If Apple still supports your iPhone on a newer iOS, updating is the clean fix. Apple’s path is Settings > General > Software Update. Before you update, check that your sideloading tool works on the new version, because an iOS update can affect apps you already sideloaded. Scarlet is confirmed on iOS 14 through iOS 26; iOS 27 support is reported by third parties but not officially confirmed. See the best iOS version for sideloading and fixing sideloaded apps that crash after an iOS update.
If your iPhone cannot run a newer iOS, skip to Fix 2. Our guide to sideloading on older iPhones lists which tools still support older devices.
Fix 2: Use an Older Build of the App
Most apps raise their minimum iOS over time, so an older release of the same app often still supports your iOS. Open source projects usually keep their past releases on their GitHub releases page, with the supported iOS in the notes. Take older builds only from the developer’s own releases or a source you trust, and check the file first: see how to scan IPA files for malware. Keep in mind that an old build can lack security fixes, and apps that log in to an online service may refuse versions that are too old.
Fix 3: Lowering MinimumOSVersion (What It Really Does)
Some signing tools can change the number for you. Sideloadly, for example, lists an option to “Change the minimum iOS version required to run the app”. Be clear about what this does and does not do:
- It only removes the check. The app’s code is unchanged. If it calls features that only exist in the newer iOS, it can crash at launch or when you reach that feature. Nothing in the edit can add those features to your iOS.
- It means re-signing. The signature of an app includes a hash of its Info.plist (Apple’s technical note TN3126 describes this). Change the file and the old signature no longer matches, so the IPA must be signed again before iOS will install it. See how to resign IPA files.
- It works best for small gaps. When the developer raised the minimum without using new features, the app may run fine. When the gap is several major versions, a crash is the likely result.
If the edited app opens and then quits, that is this problem, not a broken install. Go back to Fix 1 or Fix 2. For general crash causes, see the crash-on-launch fixes.
Errors That Look Similar
- “Integrity could not be verified”: the IPA or its signature is damaged, or the certificate is revoked. See the integrity error fixes.
- “Unable to Verify App”: the app installed, but iOS cannot check its certificate when you open it. See how to fix “Unable to Verify App”.
- “Maximum number of installed apps”: the free Apple ID limit of 3 apps. See the 3-app limit fix.
- General signing errors: see how to fix app signing errors on iOS.
FAQ
Can I install an app that needs iOS 18 on iOS 16?
Only by lowering MinimumOSVersion and re-signing, and the app may crash if it depends on iOS 17 or 18 features. An older build of the app made for iOS 16 is the more reliable route.
Does this error mean the IPA is broken?
No. The file is fine; it was simply built for a newer iOS than your device runs.
Will changing the minimum version get my account banned?
The edit itself is local to the file. Apps that check their own integrity, often games and banking apps, may refuse to run or flag a modified copy, so use edited builds at your own risk.