Skip to content
Android smartphone showing a contacts-related error on screen

Fix “Unfortunately, Contacts Has Stopped” on Android (2026)

Stop the Contacts app from crashing: clear cache, free storage, update Play services, disable bad overlays, and recover sync without wiping your Google address book.

10 min readContacts has stopped, Android Contacts crash, Unfortunately Contacts

“Unfortunately, Contacts has stopped” (or “Contacts keeps stopping”) means the Contacts app process crashed. It feels catastrophic because your address book is involved — but in most cases the Google cloud copy is fine, and the phone is choking on local cache, full storage, or a bad Play services state.

This guide fixes the crash path first, then covers how to confirm your people are still synced.

Crash vs missing contacts

Symptom What it usually is What to do
App opens then immediately closes Local crash Clear cache; free space
Empty list, no crash Wrong account / sync off Check Google sync
Crash only when searching Index/cache corruption Clear cache; update app
Crash after installing a cleaner/theme Overlay / accessibility conflict Safe mode; uninstall offender
Crash + Play Store broken Broader Google stack issue Fix Play Store first

Learn where the data actually lives in where contacts are stored on Android so you do not wipe the wrong layer.

Soft reboot when the UI is wedged

If the dialog loops and you cannot reach Settings:

  1. Use a force restart on a frozen phone for your model
  2. After boot, do not open Contacts yet
  3. Free storage and clear cache first, then reopen

A force restart is not a fix by itself, but it breaks crash loops long enough to apply real steps.

Clear cache the safe way

Do

  1. Settings → Apps → show system apps if needed
  2. Open ContactsStorageClear cache
  3. Open Contacts Storage (system) → Clear cache if present
  4. Force stop both, reboot, reopen Contacts

Avoid as step one

  • Clear storage/data (resets the app)
  • Factory reset
  • “Contacts fixer” APKs from random sites

If you must clear storage/data later, export a .vcf first when the app can stay open long enough — or export from contacts.google.com on a computer.

Storage pressure causes weird Contacts bugs

Android contact databases need room to rewrite. When internal storage is critically low, Contacts and dialer helpers crash more often.

Free space with the practical cleanup in Android storage full. Aim for multiple free gigabytes, not a few hundred megabytes. Then retest Contacts before any data wipe.

Update the Google stack

Contacts depends on:

  • The Contacts app (Google or OEM)
  • Google Play services
  • Sometimes Google app / Carrier Services
  • Account sync framework

If the Play Store cannot update anything, fix that path with Google Play Store not working. A Contacts crash that started the same week as Play failures is often one stack, not two mysteries.

Safe mode to catch overlays and “cleaners”

Third-party apps that draw over the screen, modify UI, or hook Accessibility can crash Contacts on open.

  1. Boot into Safe mode (OEM hold-power instructions vary)
  2. Open Contacts
  3. If it works in Safe mode, uninstall recent themes, cleaners, clone apps, and aggressive battery tools
  4. Reboot to normal mode and retest

Also disable work-profile Contacts briefly if only the managed profile crashes.

Sync checks after the app stays open

Once Contacts launches:

  1. Settings → Passwords & accounts → Google → sync Contacts on
  2. Pull to refresh or tap sync now
  3. Confirm the same people on contacts.google.com
  4. Set default save account to Google, not SIM

Device-only contacts that never synced will not reappear from the cloud — that is why exports matter before repair or reset.

When clearing app data is justified

Clear storage/data for Contacts only if:

  • Cache clear + updates + Safe mode still crash
  • You confirmed Google web contacts look complete
  • You exported device-only contacts if any exist

After clear data:

  1. Sign into Google if prompted
  2. Wait on Wi‑Fi for the first sync
  3. Do not immediately install overlay apps again

Hardware and repair notes

Contacts crashing alone rarely means a bad motherboard. Consider service if:

  • Multiple Google apps crash constantly after storage is free
  • The phone reboots when opening any app
  • Storage reports nonsense sizes after a drop or liquid event

If you must send the device out, back up accounts first — see before sending a phone for repair and keep a .vcf offline.

What usually does not fix Contacts crashes

  • Changing the ringtone
  • Removing the SIM as step one (unless dual-SIM tools are clearly involved)
  • Disabling Play Protect permanently
  • Installing a second Contacts app and ignoring the system crash dialog forever

A sideloaded Contacts APK can hide the dialog without fixing sync corruption underneath.

OEM Contacts wrappers vs Google Contacts

Samsung, Xiaomi, and other skins ship a branded Contacts app that still talks to the same sync accounts. A crash dialog that says “Contacts” might be the OEM package, not com.google.android.contacts.

Practical implications:

  1. Clear cache on both the visible Contacts app and Contacts Storage
  2. If you installed Google Contacts from Play as a second app, test which icon crashes
  3. Disable the unused Contacts app only after you confirm the other opens and syncs
  4. Dual-app / “clone app” features can create a second Contacts process that crashes independently

When the OEM Contacts app is the one failing, updating the system Apps bundle from the vendor’s update channel matters as much as Play Store updates. After a major One UI or HyperOS jump, wait for the matching Contacts hotfix before you assume hardware failure.

Work profile and dual-SIM edge cases

Contacts crashes that happen only when a work profile is active often come from the managed Contacts provider, not your personal Google account. Test by:

  • Opening personal Contacts while work apps are paused
  • Checking whether the crash occurs only when searching work directories
  • Asking IT whether a recent MDM policy pushed a Contacts configuration

Dual-SIM phones sometimes show carrier “profile” contacts that break after a SIM swap. Removing the SIM briefly is a diagnostic, not a fix — put it back and clear cache after you confirm whether the crash tracks the SIM change.

Bottom line

“Contacts has stopped” is almost always a local app/storage/Play services problem, not proof that Google deleted your address book. Force-restart if needed, clear Contacts cache, free gigabytes of space, update Play services, and use Safe mode to catch overlays. Clear app data only after you verify cloud contacts — and read how Android stores people so you back up the right layer before any wipe.

Frequently Asked Questions

What does “Unfortunately, Contacts has stopped” mean?

The system Contacts app (or a OEM Contacts wrapper) crashed. Your Google cloud contacts are often still safe. Fix local cache, storage, and Play services before assuming data loss.

Does clearing Contacts cache delete my people?

Clearing cache should keep accounts and synced contacts. Clearing storage/data resets the app and may require re-sync; export a vCard first if you have device-only contacts.

Why did Contacts start crashing after an update?

A bad Play services/Contacts update, full storage, or a conflicting overlay/theme app is common. Update or roll forward the Play stack, free space, and retest in Safe mode.

Can I still call people if Contacts crashed?

Sometimes the Phone/Dialer still shows recent calls. Do not factory reset to place one call — clear cache and use Google Contacts on the web if you urgently need a number.