You open your news app to catch the headlines, it flashes on screen, then dumps you straight back to the home screen. And it started right after the app or your phone updated. Here is the reassuring part: it is almost never your phone, and you are far from alone. App crashes bunch up around updates for a short list of well-documented reasons, and understanding why makes the fix obvious. This is the what-and-why behind the crash, not another checklist, though there is a link to the full fix-list at the end.
There is no public “news app crash rate” scoreboard, so anyone quoting a precise percentage for your specific app is guessing. What we do have is solid data on how often apps crash in general, and clear, repeatable reasons those crashes spike right after an update. Both are worth knowing.
How often do apps crash?
A well-run app almost never crashes. The industry yardstick is the crash-free rate, the share of sessions that finish without a crash, and healthy apps sit above 99.9 percent. Google puts a hard line under it: through its Android vitals program, it flags an app as misbehaving when its user-perceived crash rate climbs past roughly 1.09 percent of sessions, with a similar threshold for freezes. You can read Google’s own bad behavior thresholds for the exact figures. The takeaway is that a stable app crashing on you repeatedly is not normal background noise; something specific changed, and an update is the usual trigger.
Why an update is when it breaks
Updates change the code, and changed code is where new bugs live. When the app itself updates, the developer may have shipped a version with a defect that only shows up on certain phones or setups, which is why a crash can hit you and not your friend. When the phone’s operating system updates, the reverse happens: the app was built for the old system, and a changed interface underneath it can make an older app version fall over. Either way, an update is the moment the ground shifts, so it is no surprise that crashes cluster there. The good news is that developers patch these fast once reports come in.
The ad and analytics code problem
Most free news apps run on advertising, and they load third-party ad and analytics kits when the app starts. If one of those kits is outdated, or it tries to do heavy work the instant the app opens, it can stall or crash the app before you ever see a headline. This is one of the most common culprits behind a launch crash, and it is largely invisible to you, because the broken piece belongs to a company other than the news app itself. When a fresh app update fixes a crash you were seeing, an updated ad or analytics kit is often the quiet reason.
The in-app browser factor
News apps open articles inside a built-in browser view rather than kicking you out to Safari or Chrome. On Android that view relies on a shared component, the System WebView, and when it has a bug or is out of date, apps that lean on it can crash together, sometimes across many apps at once. There have been episodes where a single WebView update took down a wave of apps until it was patched. If your news app crashes when you tap into a story rather than on launch, the in-app browser component is a prime suspect, and updating it separately can clear the whole thing.
Memory, storage, and stale data
The unglamorous causes matter too. A phone low on free storage cannot give an app the working room it needs, so it crashes on launch. A cache of saved data that got half-written during an update can corrupt the app’s start-up. And a memory-hungry news app competing with everything else you have open can be killed by the system to free up space. None of these is dramatic, but together they explain a large share of stubborn crashes, and all of them are on your side of the fence, which means you can fix them without waiting for the developer.
Which fixes work most often, and why
Order matters, because the fixes that clear the most cases are also the quickest. Updating the app comes first, since most post-update crashes are a bug the developer has already patched in a newer build, so installing the latest version often ends it outright. A restart is next, clearing the stuck memory and background state that a fresh launch cannot. After that, freeing storage and clearing the app’s cache or reinstalling it handles the corrupted-data cases, and updating your phone’s system, including the WebView component on Android, closes the compatibility gaps. For the full step-by-step, our guide to fixing a news app that keeps closing walks through each in order.
Crash figures vary by source, platform, and how each study defines a crash, and app and OS behavior changes with every release. Treat the numbers here as general benchmarks rather than a measure of any one app, and check the developer’s own channels for known issues.
What To Know
- Healthy apps finish over 99.9 percent of sessions without crashing; Google flags an Android app past roughly a 1.09 percent crash rate.
- Crashes cluster around updates because changed app code or a changed OS underneath it introduces new bugs.
- Stale third-party ad and analytics code that runs at launch is a leading, invisible cause of startup crashes.
- On Android, an outdated or buggy System WebView can crash apps when you open an article inside them.
- Updating the app fixes the most cases, followed by a restart, clearing storage or reinstalling, and updating the OS.
Frequently Asked Questions
Is it normal for a news app to crash after an update?
A brief spell of instability right after an app or OS update is common, because new code and changed system interfaces are where fresh bugs appear. What is not normal is an app that keeps crashing for days, since healthy apps finish well over 99 percent of sessions without a crash. If yours keeps closing, install the latest app update first, as most post-update crashes are a bug the developer patches quickly once reports come in.
Why does my news app crash only when I open an article?
That points to the in-app browser rather than the app’s main screen. News apps open articles inside a built-in web view, and on Android that relies on the System WebView component. If WebView is outdated or has a bug, tapping into a story can crash the app while the feed itself works fine. Updating System WebView, and your apps, from the store usually clears this specific pattern.
Do free, ad-supported news apps crash more?
They can be more exposed to one common cause. Free apps load third-party advertising and analytics code at startup, and if one of those kits is outdated or misbehaves, it can crash the app before the content loads. The news app’s own code may be fine; the broken piece belongs to another company. That is why a later update, which often just refreshes those kits, quietly ends a crash you were seeing.
Is a crashing app a sign my phone is failing?
Rarely. A single app crashing points at that app or something it depends on, not your hardware. If every app crashes, look at your phone’s storage, memory, and system version instead. For one misbehaving news app, the cause is almost always its recent update, a stale component it uses, or low storage on the device, all of which are fixable without replacing anything.
How long until a crashing news app gets fixed?
Developer-side bugs are often patched within days, since crash reports flow back automatically and a fresh update can go out quickly. Your part is to keep the app set to update and install the newest version when it lands. Meanwhile, the fixes on your side, a restart, clearing storage, reinstalling, and updating your OS, can get you running again before the official patch arrives.
What To Do Next
If your app is closing right now, update it first, then restart your phone, since those two clear most cases. If it only crashes on articles, update your system browser component too. Keep automatic app updates on so you are not stuck on a broken version. For the complete walkthrough, see our guide to fixing a news app that keeps closing, and the technology section has more on why apps misbehave and how to steady them.
