Short answer: when only one app crashes after an iOS 27 update, the scope is the diagnosis. A single misbehaving app almost always means that app has not adapted to the new system yet, or that its local cache is damaged — not that your iPhone is broken. So the order is: update that app, restart the phone, reinstall the app, and report it to its developer.
The rest of this article explains why that order is the shortest path, and how to tell the rare case where a single app is genuinely the symptom of something wider.
Why one app can fail on its own
A major OS release is not a cosmetic change for developers. It changes the interfaces apps call, the permission rules they operate under, and the environment they run in. For an app to work reliably on it, the app usually has to be rebuilt against the new version.
Until that build lands, a few specific failures become possible in that app alone:
- the app reads local data written in an older format at launch and exits;
- the app calls an interface whose behaviour changed and gets terminated;
- the app needs an extra declaration for a permission under the new system and crashes when it does not get one.
None of that involves the rest of the phone. That is exactly why the pattern is so lopsided: Messages, Camera and Settings are Apple's own and ship with the system, while third-party apps arrive on their own timetables.
Four steps, lightest to heaviest
① Update the app. Open the App Store, tap your picture in the top corner, pull to refresh, and install everything under Available Updates. After a major release, developers typically ship adaptation builds within days to weeks. Most single-app crashes end here.
② Restart the phone. A normal power off and on is enough. If the crash began in the first days after updating, a restart also clears background adaptation work that has not finished. Still failing? A forced restart clears more stuck state — the sequence is in How to force restart a stuck iPhone.
③ Reinstall that one app. In Settings → General → iPhone Storage, open the app and choose Offload App (keeps some documents and data) or Delete App. A damaged cache or local database is a common cause of a launch crash, and a reinstall rebuilds that environment. ⚠️ Local data can be lost, so confirm anything important is synced or exported first.
④ Report it, if it survives all three. Tell the developer your iPhone model, your iOS version, and the exact steps that trigger the crash. That report is more valuable to them than any further change you could make on your own phone.
If you are not sure yet whether the fault is the app or the system, the surrounding checks are laid out in iOS 27 apps crashing after the update. The short version: scope first, then act.
One app or the system: how to tell
| What you see | Reading | What to do |
|---|---|---|
| Only this app crashes; built-in apps are fine | That app has not adapted | Update, restart, reinstall, report |
| The same action crashes it every single time | A defect in that feature | Report it and avoid that action meanwhile |
| It crashes only when the body is hot | Thermal limits, not the app | Cool the phone down and retest |
| Several apps crash at random, built-in ones included | Something wider | Update iOS, check free space, restart |
| It crashes plus storage keeps filling | Space pressure is a suspect | Free space before more reinstalls |
Row three is easy to misread. When an iPhone gets genuinely hot, thermal protection reduces performance and can terminate demanding work; the app is a bystander. Row five is the other common false lead — with very little free space, an app may be unable to write the temporary files it needs, which looks exactly like an app bug. If free space is tight, see Several GB free but "not enough storage"?.
What not to do
- Do not erase the whole phone for one app. The evidence points at the app; erasing is the heaviest possible response to the lightest possible cause.
- Do not install "repair" or optimizer tools. A third-party utility cannot make an app compatible with a new system, and it introduces new risk instead.
- Do not assume the crash damaged anything. An app that crashes has simply failed to reach agreement with the system. Nothing is consumed or worn out by it.
- Do not reinstall repeatedly. If a clean install of the current version crashes at the same step, more reinstalls will not change the outcome; the developer needs the report.
When a single app is genuinely a symptom
Rarely, one app crashing is the visible tip of a wider problem. Take it more seriously if the crash is accompanied by any of these:
- the phone runs hot and the screen dims during ordinary use — see Why is my iPhone hot?;
- free space is nearly gone, or the storage list shows an unexplained category that keeps growing — see iOS 27 storage full after update;
- the phone stutters broadly, not only inside that app — see iOS 27 lag and stuttering after the update.
In those cases, fix the environment first and retest the app. More often than not the crash goes with it.