I need my phone stable for work this week, but since moving to iOS 27, apps have been closing without warning. It happened 7 times today across different apps, including once while opening a PDF. I restarted the phone and disabled background app refresh, but it continued. What should I check next?
The downside of chasing individual app settings is that crashes across unrelated apps usually point to storage, memory pressure, or the OS itself. Check Settings > General > iPhone Storage first. If space is tight, free up several gigabytes, then update every app and install any available point-release update. Disabling Background App Refresh rarely fixes this kind of crashing.
Next, open Settings > Privacy & Security > Analytics & Improvements > Analytics Data. Repeated “JetsamEvent” entries suggest apps are being killed under memory pressure. Repeated “panic-full” entries are more serious and worth taking to Apple Support. Heat can contribute too, so remove the case temporarily and see whether the phone is getting unusually warm.
If you installed a beta, I wouldn’t trust that phone for work this week. Back it up, turn off beta updates, and restore the current public release if necessary. Otherwise, try Reset All Settings before considering a full erase. It keeps your data but resets Wi-Fi, permissions, and system preferences.
Do not reset the phone before a work week has started unless there is a verified backup and enough time to restore everything. “Reset All Settings” is relatively safe, but I am skeptical of that it will fix the repeated app terminations after an OS upgrade.
An alternative middle-step is to connect the iPhone to a Mac or PC and select Update in Finder or Apple Devices, which reinstalls the current system files without the intentional deleting of data, which can solve a faulty upgrade. A backup should be done anyway. If the upgrade was installed only today, leave the phone charging on Wi-Fi overnight so that indexing and photo processing can be completed.
The analytics check from @devhive9400 is worthwhile. If you see repeated panic logs, or the phone restarts rather than merely returning to the Home Screen, stop experimenting and contact Apple. For this week, keep critical PDFs and work files available on another device or through a browser, because random crashes are not something I’d trust to settle down during an important call.
Realistically, I wouldn’t expect this to become dependable on its own before your work week. Before reinstalling the system, check Settings > General > iPhone Storage. An almost-full phone can cause apps to be terminated under memory pressure, especially while opening larger documents. Clear several gigabytes if space is tight, then install every pending app update and restart once.
Pay attention to whether Apple’s own apps fail too. If it’s mostly one PDF or cloud-storage app, reinstalling that app may be worth trying after confirming its files are synced. If unrelated built-in and third-party apps keep closing with plenty of free space, I’d stop doing random resets and open a support case. Keep a short note of the app and exact time each crash occurs, since that makes the analytics logs much easier to match.
Apps that drop you back to the Home Screen are not necessarily crashes in the apps. When others are crashing after an upgrade, the culprit can often be a shared extension, such as a third-party keyboard, a VPN, a password manager, an ad blocker, or a cloud-storage provider, or maybe the company’s security software.
A quick test would be to put in Apple’s keyboard, turn off your VPN or any filtering app, and not open the PDF directly from Mail or from cloud storage, but save the file in your Files app as “On My iPhone” and try opening that one. If the local file works but the file picker/Share Sheet or the remote copy does not, your OS is probably fine, and you need to go check all the extensions you have installed. See if the crash happens while you type in the app, sign in, attach a file, or reach for the Share Sheet — that’s more informative than the names of the apps you use.
Since this is a work phone, I’d also be careful about messing with your managed profiles. If you don’t know what that means — do not uninstall anything that came with the phone or a company profile unless instructed to by your IT support, as it may brick your device or kill your ability to use work apps. You might want to call them and ask if their VPN or device-management software is compatible with the recent update; it should be, but until you know, it is also a potential source of trouble, and it would explain many mysterious crashes.
I’d put the computer-based Update suggested by @nina_sudo ahead of Reset All Settings. Resetting settings creates its own nuisance by clearing permissions, networks, and preferences, while doing little for a broken third-party extension. If Apple’s built-in apps still close when opened normally, with every shared add-on disabled, then an OS reinstall or support case makes sense. If the crashes stop, re-enable those extras individually after your work week rather than all at once.
If the same PDF is what dies every time, stop treating this as a system-wide memory problem. A single malformed or half-synced file can hard-crash the renderer no matter how much free space you have, and it’ll happen on any app that tries to preview it. Open that exact file on another device or in a browser. If it only breaks on the phone, redownload a clean copy before you go reinstalling system files.
Where I’d push back on @retro_panda a little: extensions are a fair suspect, but seven crashes in one day across random apps smells more like one background process spiking memory and taking whatever’s in the foreground down with it. Worth watching what you had open in the background each time.
And a small habit thing people never mention. Swiping every app closed after each crash doesn’t help. Cold-launching everything again just creates fresh memory spikes right when the phone is already under pressure. Leave them alone unless one specific app is the offender.
Do not perform the test with an active work document because a program failure while saving or uploading data may result in loss of this document or a conflict with stored files in the cloud.
It is better to do a test run without the participation of Internet networks to see if the problem is caused by a VPN, account identification system, cloud storage, or company software. Fifteen-minute test runs with various apps that use locally stored data can be held when the phone is in the Airplane mode with the Wi-Fi function turned off. If the failures occur only when networks are available, the issue can be related to the incompatibility between apps and external services. However, if the phone stops responding in both modes, the error is more likely to be caused by hardware issues.
The described test is much faster and easier than the complete reset of the phone. It is better not to use the phone for editing work documents when the test has shown the failure of Apps to operate offline. This way, no working data will be lost, and a more stable device will be found. If the test has failed, I would back up the data on another phone before repairing the defective device.
Don’t keep testing with live work files or assume every dump to the Home Screen is the same problem.
Watch what happens immediately afterward. If the phone shows the lock screen and requires your passcode before Face ID works again, the phone itself restarted. That is not an ordinary app crash, and I would stop troubleshooting extensions or reinstalling random apps. Back it up and get Apple or your company IT involved. If you land directly on the Home Screen and can reopen the app, then memory pressure, a bad extension, or a damaged file is more plausible.
For this week, treat the phone as unreliable and move essential PDFs, meeting links, and authentication recovery codes to a second device. Troubleshooting can wait. Losing access during a call because the phone decided to restart cannot.
Reinstalling the system is significantly different from erasing your device and restoring the same backup as corrupted settings may return with the backup. So when you reach the erase stage, wait for work to be done and temporarily consider setting up as new rather than restoring everything at once.