For the Samsung Galaxy A35 5G, one app versus the operating system, storage and service state determines the safe sequence. First, establish the pattern before changing anything. 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.
Differential
Likely causes of “Samsung Galaxy A35 5G app keeps crashing, freezing or will not open”, and how to tell them apart
- 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
- 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.
Try in this order
0 of 9 completedEstablish 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
- Model scope
- SM-A356*. Samsung Galaxy family; S Pen, foldable display, DeX, USB moisture and One UI features vary by exact model.
- Connector
- USB-C. A cable that fits is not necessarily a cable rated for this phone's charging speed — USB-C carries several power profiles and a cable built for data will charge slowly or intermittently while seating perfectly.
- SIM
- Carries an eSIM. An eSIM does not travel with the handset the way a plastic SIM does: a phone swap, a factory reset or a repair can leave the profile behind, and restoring it is a carrier action rather than a phone setting.
- SIM
- Supports two active lines. The default line for calls, for messages and for cellular data are three separate settings, and getting them crossed produces calls arriving on one number while data or messages use another — with almost no indication that anything is wrong.
- Modem
- 5G capable. In marginal 5G coverage the phone hands repeatedly between 5G and LTE, which costs more battery and generates more heat than settling on either — so the preferred-network setting is a real diagnostic lever rather than a preference.
- Charging
- Supports wireless charging. Coil alignment is tighter than it looks and a thick case, a metal plate or a card in the case defeats it entirely — so wireless charging failing while cable charging works is usually the case rather than the phone.
- Water resistance
- Rated water resistant, which is not waterproof and which degrades with age, drops and seal disturbance. The rating covers incidental exposure; it is not a guarantee, and moisture-detection warnings are deliberately conservative and can persist after the port feels dry.
- Platform
- Android, with a manufacturer interface layer over it. Battery optimization and background-execution restrictions are applied per app and are far more aggressive than on iOS — which is why 'set this app to unrestricted' is a real fix here and has no equivalent elsewhere.
- Symptom boundary
- This record covers Samsung Galaxy A35 5G 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
- !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
Exact questions
Common questions
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.