The standard advice when an old app refuses to open on a new iPhone is to delete it and move on. That's wrong.

You paid for that app. It worked fine on your last phone. The real reason it stopped working isn't some vague 'compatibility issue', it's a hard technical cutoff that Apple should have explained better.

Most people blame the iOS update, but the breakdown usually comes down to one of three things: the app was built for a 32-bit processor, it relies on APIs that Apple retired, or the developer stopped updating it years ago.

But here's the part that frustrates people: some apps that were updated just a few years ago still break. What changed isn't the app, but the entire underlying system that now treats certain old code as unsafe or unrecognizable.

And that's not a bug, it's a design choice that Apple made to keep iOS secure and fast.

Why did 32-bit apps stop working?

When Apple released the iPhone 5s in 2013, it included the A7 chip, the first 64-bit processor in a smartphone. For a few years, iOS supported both 32-bit and 64-bit apps, but with iOS 11 in 2017, Apple pulled the plug on 32-bit entirely.

The operating system no longer recognizes the armv7 instruction set that those apps were compiled for. It's not that the app is 'corrupted', it's that the phone's CPU literally doesn't know how to execute its code. Think of it like trying to start a diesel engine with gasoline.

If you're holding an iPhone 5 or earlier, you're still on 32-bit. But every iPhone from the 5s onward uses a 64-bit kernel. So when you upgrade your hardware, any app that was never recompiled for arm64 simply won't launch.

What about 64-bit apps that still crash?

Even if an app survived the 64-bit transition, it can still break on newer iPhones. Apple deprecates application programming interfaces (APIs) regularly, old graphics calls, Touch ID routines, or even the way an app handles screen sizes can cause a crash on launch.

For example, apps that relied on OpenGL ES for graphics may fail on iOS 12 and later, because Apple pushed developers toward the Metal framework. And apps that weren't updated for the iPhone X's notch or the removal of the home button often misbehave.

Check these three things before you give up on an old app:

  • Is it 32-bit? (You can check in Settings > General > iPhone Storage > [app name], if it says 'App Compatibility,' it's 32-bit.)
  • Was it last updated before 2018? If so, it likely missed the Metal transition.
  • Does it require a specific hardware feature like Touch ID? Face ID replacement may break the workflow.

The better question is whether the crash happens because of a missing API or because the app was never optimized for the new screen sizes. That understates it, the real issue is that Apple's Metal framework replaced OpenGL entirely, and any app that didn't make the switch after 2018 is running on borrowed time.

Can I still download old apps from the App Store?

Even if you own the app, Apple may have removed it from the store. The company's App Store guidelines now require that all apps be updated to support 64-bit and recent APIs. If a developer abandoned the app, it can vanish from your purchase history unless you previously downloaded it on an older device.

You can still check your Purchased tab, but there's no guarantee. The app might appear with a cloud icon, but tapping it could show a message that it's not compatible with your device. In that case, you're stuck.

The cutoff isn't arbitrary; it's a trade-off between maintaining compatibility and pushing the platform forward. Apple could have kept a 32-bit emulator, but that would have added bloat and security risks. They chose to shed legacy code instead.

Quick facts: 32-bit apps stopped working with iOS 11 in 2017. 64-bit apps may crash if not updated for Metal. The App Store can remove abandoned apps. An old iPhone 5 or 6 can still run legacy apps.

Is it Apple's fault or the developer's?

Both. Apple announced the 64-bit transition in 2013 and gave developers until 2017 to update their apps. That's a generous window. But many developers, especially those who built niche or one-off apps, moved on, closed their businesses, or simply didn't care enough to update.

On the other hand, Apple's API deprecation pace is relentless. A developer who keeps an app alive for six years might still be forced to rewrite huge chunks when Apple drops support for a framework. So the blame is split.

When you can't replace that old app

If you rely on a specific legacy app for business, like a custom inventory tool or a medical reference app that was never updated, none of the explanations above help you. Your only option is to keep an old iPhone running an older iOS version.

Search for a used iPhone 5 or iPhone 6 on a site like Swappa or eBay, and don't update it beyond iOS 10 or 11. That's the nuclear option, but it works. Some people even use iPod touches as dedicated devices for a single app.

The single most important thing to understand is that 32-bit apps are dead on modern iPhones, and no amount of troubleshooting will bring them back. If you need them, your only realistic path is to keep an old device.

For 64-bit apps that crash, the fix is usually finding a modern alternative or checking if the developer has a web version. But waiting for Apple to add backward compatibility is a waste of time.