When a two-Mac clipboard workflow fails, “the clipboard didn't work” is too vague to debug. At least four things might have happened: the source app wrote the wrong representation, a sync app didn't carry the latest copy, the destination app chose an unexpected representation, or a user tried to recover an older item that was never meant to travel between devices.
The useful distinction is current-copy transport versus local history retrieval. The first moves a new clipboard event between Macs. The second lets a person find an earlier copy on one Mac. Treating them as separate behaviours makes testing
Disclosure: This article was drafted with AI assistance and checked against the linked Apple documentation and Deskferry product guides. and support much clearer.
Start with an event, not a screenshot
On macOS, an NSPasteboard can expose multiple data types for an item. A copied URL might be represented as text and as a URL; a rich selection might offer plain text, HTML, and RTF. Apple documents NSPasteboard.types as the union of the declared types, and recommends checking types before reading data. The changeCount value changes when pasteboard ownership changes. Neither fact alone proves that a particular receiving app will paste the representation you expected.
For a reproducible manual test, record this small event tuple:
| Field | Example |
|---|---|
| Source | Mac A, browser address bar |
| Event | Copy a harmless, unique marker at 10:32 |
| Intended representation | Plain text |
| Destination | Mac B, plain text editor |
| Observation | Exact marker pasted at 10:33 |
Use a fresh marker for each run, such as handoff-20260929-1032. A stale marker can look like a successful sync when it is actually yesterday's clipboard content. Never use a password, token, private message, or customer data as a test marker.
Four separate checks
- Source copy: Paste locally on Mac A immediately. If this fails, investigate the source app before the network.
- Current-copy transfer: With both Macs in the intended pairing group, copy a fresh marker on Mac A and paste it on Mac B. Record elapsed time and the exact pasted bytes. Reverse the direction.
- Representation choice: Repeat with a URL, a rich text selection, and an image or file only if the product tier supports those formats. Compare what the destination app actually pastes, not just what its clipboard viewer displays.
- History retrieval: On Mac A, copy marker A, then B, then C. Retrieve A from Mac A's history. Repeat independently on Mac B. Do not assume one Mac's past history has been replicated to the other.
These checks identify different failure boundaries. A successful current-copy transfer says nothing about history retention. A successful history retrieval says nothing about whether a new copy crosses the LAN.
A compact failure matrix
| Symptom | First useful question |
|---|---|
| Mac B pastes an old marker | Was a fresh copy observed on Mac A after pairing? |
| Text works, image does not | Is the format supported by the chosen plan and receiving app? |
| Mac A can restore an old copy; Mac B cannot | Is history local to each Mac? |
| Rich formatting disappears | Which pasteboard representation did the destination choose? |
| One direction works | Were both devices in the same active group when the reverse copy occurred? |
This is a diagnostic table, not a promise that every clipboard manager supports every cell. For Deskferry specifically, the product guide describes LAN sync for new copies while each Mac keeps its own history. Its Mac clipboard sync guide explains the two-Mac pairing workflow; the separate clipboard history guide covers local retrieval. Deskferry is still preparing its Mac App Store release, so use those pages as workflow references rather than assuming the app is already available to install.
Make the test safe enough to repeat
- Choose harmless, unique markers that reveal no private data.
- Keep the receiving app constant when comparing runs; different apps may prefer different pasteboard representations.
- Record whether the Macs were on the same network and active pairing group.
- Record the observed result, including failures and uncertainty. A preview or successful local paste is not evidence of cross-device transfer.
- Clear or replace test clipboard contents when you finish, especially on a shared machine.
If you're implementing a macOS clipboard feature, Apple's NSPasteboard.changeCount and NSPasteboard.types documentation are useful starting points. The practical lesson is to test the full copy-to-paste path with controlled content, and to report transport and history as two distinct results.
Disclosure: This article was drafted with AI assistance and checked against the linked Apple documentation and Deskferry product guides.
