Universal Clipboard not working between iPhone and Mac? Here's the fix everyone misses
A few weeks ago, Universal Clipboard stopped working between my iPhone and MacBook. I ignored it. Then I needed it. Then I lost an afternoon to it.
Every setting on both devices said the feature was on. iCloud was signed in. Same network. Bluetooth on. Handoff on. By every visible signal, it should have worked, but it didn’t.
If you just want the fix, skip to it here. The rest is the story of how I got there.
What Universal Clipboard is
Universal Clipboard is the Apple feature that lets you copy text, images, or files on one device and paste them on another. Copy on your iPhone, paste on your Mac.
I used it for years without knowing its name. I imagine most people do. You just notice that copy and paste works across your devices, until one day it doesn’t.
The standard advice, which didn’t work
I started by asking Claude. When the quick suggestions didn’t help, I cross-referenced with Google and pulled in fixes from the top-ranked posts. Both sources converged on the same checklist:
- Same Apple ID on both devices
- Wi-Fi and Bluetooth on
- Handoff on
- Devices near each other
- Restart everything
- Update both operating systems
I worked through all of it. Updated iOS. Updated macOS. Signed out of iCloud on both devices, signed back in. Toggled Handoff off and on more times than I can count.
None of it worked.
At this point I had a choice: book an Apple Store appointment, or keep digging.
Why I didn’t go to the Apple Store
I’ve taken software bugs to the Apple Store before. If it’s not a hardware issue they can fix by replacing a part, the answer is usually the same checklist I already tried, followed by “wait for a future update.” So I kept digging on my own.
The accidental clue
Somewhere in the middle of the troubleshooting, after signing out of iCloud on the Mac and signing back in, I noticed something strange. I opened Find My on my iPhone and looked at how it described my Mac.
It said Find My was off on the Mac.
I switched to the Mac and checked the same setting. It said Find My was on.
The two devices disagreed about a setting they were supposed to share. The Mac thought it was registered with Apple’s services. Apple’s servers, and therefore my iPhone, did not agree.
I’d never seen this before. I check Find My regularly. I got robbed once and that left a habit. Both devices had always shown up correctly until now. The sign-out and re-sign-in had broken something in how the Mac registers with iCloud.
A problem I created by following standard advice, but useful information. When two parts of a system disagree about reality, no setting toggle will fix it. You have to find which side is lying and force a re-sync.
I cycled Find My Mac off and on, restarted the Mac. Now both devices agreed. But Universal Clipboard was still broken, and Find My was only updating every twelve hours instead of in real time. The registration was partially fixed but the Mac still wasn’t fully present.
The move I should have made earlier
After more failed attempts (restarting daemons, clearing more state, trying every plausible Terminal command), I finally did the thing I should have done first.
I created a new user account on the Mac. Logged out of mine. Logged into the new one. Signed into iCloud. Enabled Handoff. Tested Universal Clipboard.
It worked.
Then I logged back into my main account and tested again. Broken.
That single test compressed an afternoon of guessing into one sentence. The problem wasn’t the Mac. It wasn’t iCloud, the iPhone, or the network. It was somewhere inside my user account. The corruption was local to one user’s preferences and caches.
When you can’t tell whether a problem is in the system or in your configuration of the system, create a clean instance and test there. A new user account. A fresh git branch. A blank document. An anonymous browser window. Whatever the equivalent is for the system you’re debugging.
One move, and the search space is cut in half.
The fix
Once I knew the problem was in my user library, the fix was a matter of finding which files were corrupted and clearing them.
The daemon sharingd is the macOS process that handles Handoff, AirDrop, and Universal Clipboard. Its caches had gone bad in a way that survived every standard reset. Deleting them forces macOS to rebuild from scratch.
Open Terminal on your Mac and run:
rm -rf ~/Library/Caches/com.apple.sharingd
rm -rf ~/Library/Caches/com.apple.continuity*
rm -rf ~/Library/Caches/com.apple.handoff*
killall sharingd
Then test Universal Clipboard: copy text on your iPhone, paste on your Mac. It should work.
One note on what didn’t work for me. I first tried deleting just the preferences file (~/Library/Preferences/com.apple.sharingd.plist) with a restart. That alone didn’t fix it. The cache cleanup above is what worked.
The broader lesson
I almost gave up three times before doing the new-account test. Each time I told myself the next idea was probably the answer, so why bother setting up a whole new account.
But “probably the answer” had already been wrong six times in a row. I should have updated my prior.
The pattern I keep falling into: I trust the next plausible guess more than the next diagnostic. Guesses feel like progress, diagnostics feel like overhead. So I run guesses until I’ve exhausted them, then resent the time spent.
The lesson:
When two cheap guesses fail, stop guessing and run a test that splits the problem in half. The test always feels like more work than it is. The guessing always feels like less work than it is.
This applies far beyond Universal Clipboard. Most of the systems we deal with are opaque. We can’t read their source. We can only probe them. The quality of debugging is the quality of the probes, not the cleverness of the hunches.
FAQ
Will I lose any data by deleting these caches? No. macOS rebuilds them automatically. They store Handoff and sharing state, nothing you’d notice losing.
Do I need to do this on my iPhone too? No. The corruption was on the Mac. The iPhone side was fine.
What if Universal Clipboard works briefly then breaks again? Probably network or Bluetooth interference. Check both devices are on the same Wi-Fi and Bluetooth is on for both. A VPN can break Continuity features even when it appears off, if it left network filters behind.
Does this fix work on older macOS versions?
Yes. The sharingd daemon and its cache paths have existed for years.
Is this an official Apple-supported fix? No. Apple’s official troubleshooting stops at “restart your devices.”