An Android app keeps crashing: protect local data before clearing anything
Use app scope, updates, and a cache-only test to narrow the failure.
Decide whether the app or phone failed
Watch what happens when the problem occurs. Returning to the home screen after one app closes differs from seeing the phone's startup logo and a full restart. Write down the app name, its version, the Android version, and the exact action that triggers failure. Try another application with a similar function where possible. If only one app crashes while everything else works, begin with that app's supported guidance. A video that consistently fails during export gives a developer more useful evidence than a report that the phone sometimes feels broken.
Restart and check supported updates
Save any work you can, restart the phone normally, and repeat the smallest action that reproduces the crash. Check for an app update through the official store and for a device software update through Settings. Google provides specific steps for Pixel phones; other manufacturers may use different menus and button combinations. Read release notes when available rather than assuming every current bug is solved by a version change. A simple log of before-update and after-update behavior is useful if the failure remains. Avoid unofficial modified downloads advertised as special compatibility fixes.
Use a cache-only test carefully
Google's app guidance distinguishes clearing temporary cached data from clearing app storage. If the supported instructions suggest a cache test, read the button label carefully and choose only the intended operation. App storage removal can delete local information and sign-in state. Before any data-clearing or reinstalling step, understand whether the application stores drafts, recordings, authenticator information, or offline documents only on the phone. Export important items when possible and verify the exports. A recoverable diagnostic step is worthwhile; losing the material you were trying to open creates a larger problem than the original crash.
Try a small alternate input
If the crash occurs while handling a specific item, compare a modest, non-sensitive test item. An editor that opens a short sample but fails on one large project may be encountering an input or workload issue. Keep the original intact and work on a copy where possible. For an online app, check whether a stable connection changes the result. Do not send private documents to a public support forum to demonstrate the failure. Describe file type, approximate size, and the action instead, and share a sanitized sample only through a support channel you have verified.
Send the developer a reproducible report
If the problem remains confined to one app, contact its developer through the official store listing or support page. Include the steps in order, expected result, actual result, versions, and the tests already completed. Mention whether the issue began after an update and whether other users of the same account see it on another device. If several applications fail or the phone restarts, use the device manufacturer's broader troubleshooting route. Confirm recovery by repeating the real task and checking that saved output is intact, not just by observing that the app opens once.
Sources & further reading
Source links support the factual context. Practical examples and suggested workflows are original editorial guidance. Sources checked October 5, 2026.
Spotted something we should correct? Send a correction. Read our editorial policy.
