Direct answer
For the Samsung Galaxy Z Fold6, one app versus the operating system, storage and service state determines the safe sequence. First, force close and restart the device, then check app/system updates and free space.
What this covers
- Samsung Galaxy Z Fold6 (SM-F956*)
- Foldable device; distinguish cover display, main display, hinge and S Pen behavior.
- The specific fault this record addresses: app keeps crashing, freezing or will not open
What it does not cover
- ×The same symptom on a different Samsung product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
The app's stored data has become corrupt
What separates it It crashes immediately on launch, every time, having worked before. Cache and stored state can be left inconsistent by an interrupted update or a full disk.
How to confirm Clear the app's cache first, then its data if that fails. Clearing data signs you out and discards local content, so it is the second step, not the first.
- 2
Storage is full or nearly full
What separates it Several apps misbehave at once, updates fail, and the camera refuses to save. An app that cannot write cannot run reliably.
How to confirm Check free storage before anything app-specific. Below a few percent free, all bets are off across the whole phone.
- 3
The app version and the OS version disagree
What separates it It broke immediately after an OS update, or after an app update on an older OS. Compatibility runs both ways.
How to confirm Check for an app update, and check whether the app still supports your OS version. An app that has dropped support for your OS will not be fixed by reinstalling it.
- 4
A permission it needs was revoked
What separates it It crashes at one specific action — opening the camera, attaching a file, starting a call. An app given a hard denial where it expected access can fail rather than degrade.
How to confirm Check the permissions for that app against what the failing action needs.
- 5
A specific piece of content is triggering it
What separates it It crashes on one conversation, one photo, one file, and is fine otherwise. A malformed item can take the app down every time it is rendered.
How to confirm Note exactly what was on screen or being opened. A reproducible trigger is a report worth sending to the developer, and it is also avoidable in the meantime.
- 6
The phone is out of memory
What separates it Apps close in the background and have to reload constantly, worse with many apps open or during heavy use. This presents as apps 'restarting' rather than crashing.
How to confirm Restart the phone and compare. Reloading rather than crashing is a memory symptom, not an app fault.
- 7
A bad update from the developer
What separates it It started for many people on the same date, and the app store reviews say so. Nothing on your phone caused it.
How to confirm Check recent reviews and the developer's status channels before spending time on your own configuration.
- 8
An account or sign-in state that cannot be resolved
What separates it It crashes at the sign-in step or immediately after. A stale token can put the app into a state it cannot recover from.
How to confirm Sign out and back in where possible before clearing data, since signing out is the lesser action.
- 9
Overheating
What separates it Crashes cluster during heavy use or in the sun, and stop when the phone cools. A throttling phone changes performance underneath the app.
How to confirm Let it cool and retry the same action.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- Whether it crashes on launch, at a specific action, or randomly during use. Those are three different faults.
- Whether one app is affected or several, which separates an app problem from a phone problem.
- The date it started, and what happened then: an OS update, an app update, a full disk, a new account.
- Exactly what was on screen or being opened when it failed, since a reproducible trigger is the most valuable single fact.
- Free storage on the phone.
- The app version and the OS version.
- Whether the phone was hot at the time.
Establish the pattern before changing anything
ReversibleCrashing on launch, at one specific action, or randomly are three different faults with three different fixes. Reinstalling first destroys the evidence that would have told you which one you had.
Check free storage
ReversibleAn app that cannot write cannot run reliably, and below a few percent free the whole phone misbehaves — several apps at once, failed updates, a camera that will not save. This is a phone-level cause that looks like an app-level one.
Restart the phone
ReversibleApps that reload constantly rather than crashing outright are describing memory pressure, not a defect. A restart clears it, and comparing before and after distinguishes the two in a couple of minutes.
Check for an app update and an OS compatibility gap
ReversibleCompatibility runs both ways: an OS update can break an old app, and an app update can drop support for an old OS. An app that no longer supports your OS version will not be fixed by reinstalling it, which is where a lot of effort gets wasted.
Check the permissions the failing action needs
ReversibleAn app crashing at one specific action — opening the camera, attaching a file, starting a call — is frequently one that was given a hard denial where it expected access and did not handle it gracefully.
Clear the cache before clearing data
Signs you outCache is disposable; data is your local content and your session. Clearing cache costs nothing and fixes a real share of corrupt-state crashes. Clearing data signs you out and discards what is stored locally, which is why it comes second.
Check the app store reviews and the developer's status
ReversibleA crash that started for many people on the same date is a bad release, and nothing on your phone caused it or will fix it. Thirty seconds of reading prevents an afternoon of configuration.
Note the exact trigger where one exists
ReversibleOne conversation, one photo, one file that reliably takes the app down is the most valuable fact available — it is a report the developer can act on, and it is avoidable in the meantime.
Reinstall last, and know what it costs
Signs you outIt clears everything local and re-prompts for permissions, which is why it sometimes works. It also discards anything not synced, and it teaches you nothing about the cause — so it belongs after the cheaper, more specific steps.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- SM-F956*. Foldable device; distinguish cover display, main display, hinge and S Pen behavior.
- Type — book-style FOLDABLE (crease is normal)
- A foldable with a small outer cover screen and a large inner folding screen. A visible CREASE down the middle of the inner screen is normal on all book foldables — it is where the panel bends, not a defect. Flex mode props it half-open for hands-free use.
- Inner screen care & S Pen
- The inner folding screen is a soft plastic-topped OLED — never use a hard/standard stylus or press hard; it supports only the specific Fold-edition S Pen (not the Ultra's). Do not force objects into the fold. IP48 rating resists water but NOT dust, so keep grit out of the hinge.
- One UI / Android
- One UI optimised for the large screen (multi-window, DeX). eSIM + physical SIM.
- Symptom boundary
- This record covers Samsung Galaxy Z Fold6 when it app keeps crashing, freezing or will not open. A different symptom on the same hardware, or this symptom on a different Samsung product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !Several unrelated apps crash after every step here, which points at the phone rather than any app.
- !The app has dropped support for your OS version — no reinstall changes that, and the choice is the OS or the app.
- !A reproducible crash on specific content, which is a developer matter and worth reporting with the exact trigger.
- !The phone restarts itself rather than the app closing, which is a system-level fault.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Samsung publishes this as "App is crashing or not working on Samsung phone or tablet". Covers apps that crash, freeze or will not open on a Galaxy phone - force stop, clear cache, update and safe mode. Probed 2026-08-21: title-verified. What that article does not carry is the model boundary — it is written for a product line, and SM-F956* is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
There's a crease/line across the middle of my Galaxy Z Fold6 screen.+
That is normal and expected on every book-style foldable — the inner screen is a single flexible panel that bends at the hinge, leaving a visible and slightly feelable crease down the centre. It is not a crack or a defect. What is NOT normal is a spreading line, a black bar, or the screen lifting at the fold, which would indicate damage — often from dust in the hinge (the Fold6 resists water but not dust) or using a hard stylus. Use only the Fold-edition S Pen on the inner screen.
One app crashes every time I open it.+
Clear its cache first — corrupt stored state after an interrupted update or a full disk is a common cause and cache is disposable. Clear its data only if that fails, because data means your session and your local content.
Several apps started crashing at once.+
Check free storage first. Below a few percent free the whole phone misbehaves — apps crash, updates fail, the camera will not save. It looks like several app faults and it is one phone-level cause.
It broke right after a system update.+
Check for an app update, and check whether the app still supports your OS version. Compatibility runs both ways, and an app that has dropped support for your OS will not be fixed by reinstalling it — which is where most of the wasted effort on this goes.
Should I just reinstall it?+
Last, not first. A reinstall clears local data and re-prompts for permissions, which is why it sometimes works, but it discards anything unsynced and teaches you nothing about the cause. Cache, storage, permissions and a restart are all cheaper and more specific.
Apps keep reloading when I switch back to them.+
That is memory pressure rather than crashing. The phone is closing background apps to make room, and they reload from scratch when you return. A restart clears it; if it recurs constantly, having fewer heavy apps open is the practical answer.
It crashes on one particular chat or photo.+
That is the most useful thing you could have found. A reproducible trigger is a report the developer can act on, and it is avoidable meanwhile. Note exactly what was on screen — that detail is the whole value of the report.
It crashes when I try to attach a photo.+
Check its permissions. An app crashing at one specific action is frequently one that was given a hard denial where it expected access and did not handle the refusal gracefully. The action names the permission to look at.
Everyone I know has the same problem with this app.+
Then it is a bad release and nothing on your phone caused it. Check the app store reviews and the developer's status channels — waiting for the next version is genuinely the correct action, and reinstalling only reinstalls the broken version.
It only crashes when the phone is hot.+
A throttling phone changes performance underneath the app, and some apps do not handle that well. Let it cool and repeat the same action — crashes that cluster during heavy use or in the sun and stop when cool are thermal rather than defects.
Does this answer apply to every Samsung model?+
No. It is scoped to SM-F956*. Foldable device; distinguish cover display, main display, hinge and S Pen behavior.
What should I record before troubleshooting app crashing or freezing?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing app crashing, freezing. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Do not delete the only authenticator, banking or unsynced-data app without recovery access.
Answer for the exact device and software version shown above.