Manual Facts — 2026-11-02 — Share a library with another Mac or your iPhone
🤖 AI Drafted (Not reviewed)
The user manual belongs to the maintainer (see Writing the Guides).
This page supplies facts for the “Share a library with another Mac or your iPhone” section.
Spec: specs/source/sharing-two-macs.md (its §1 is the flow, §2 and §10 the failures). Every fact
is read from the code the spec cites. Where something is not built, the section says so.
What a person can do
- On the Mac that holds the library (the host): turn Sharing on, choose the address other devices will use, and hand out a one-time code or link.
- On a second Mac (the guest): pick the host from the nearby list or paste the link, enter the code, and work in the shared library.
- On an iPhone or iPad: open the link from Messages, Mail or Notes, or scan the QR code, and the library opens there.
- Optionally turn Multi-user on so that each person signs in as themself.
Names on screen
- Host: Settings › Sharing; the switch Sharing; the address field with Use; Copy Link and the QR code; Multi-user with Create Account.
- Guest Mac: Settings › Sharing › Connect to Another Mac…; the Nearby list; the Paste link field; Connect.
- iPhone and iPad: the Connect screen, with the scanner, the pasted link and the nearby list.
- Set Up asks about sharing and accounts when a project is created (spec §6; being built).
What they see
- The address. The host shows one address: its Bonjour name (
<computer>.local, port 8765) by default, or a Tailscale name (…ts.net) when the person pastes one and presses Use. The link and QR carry that one address. A.localname works on the same network; a Tailscale name works anywhere both devices are on the tailnet. (Letting the guest try more than one address is the spec’s Stage 2, not built.) - The code. A code lasts ten minutes and is used once. If nothing is listening on the chosen address the host says so in a sentence instead of handing out a link that cannot work.
- Connecting. The guest checks the link, connects over https with the host’s certificate pinned (not needed for a Tailscale name), checks that both apps speak the same version of the API, stores the device token, and switches to the host. Then the host’s library is what the guest sees.
- Multi-user. While Multi-user is off, everyone connects as the host’s owner. Turning it on needs the owner signed in on the host and an owner password chosen first; until then the switch explains why it will not stick.
What each failure sentence means
- “Nothing is listening on “: Sharing is on but the engine could not bind that address. Pick another address or check the network. No link is issued.
- “
.local could not be found” : the two devices are not on the same network, or the network blocks Bonjour (common on a campus or hotel network). Use a Tailscale name instead. - “The certificate did not match” or “plain http is not allowed”: the link is old, the host made a new certificate, or someone changed the link. Ask for a fresh link.
- “Choose who you are”: Multi-user is on; the guest must pick an account.
- “The host stopped sharing”: Sharing was turned off on the host; the guest’s row stays until the host shares again.
- “Your access was revoked”: the host removed this device.
- “Different versions”: the two apps do not speak the same API; update the older one.
- “The Tailscale forward could not be made”: a sandboxed app cannot call Tailscale; make the forward
by hand as the sentence says, or use the
.localaddress. - “Create Account: not found (404)”: a known gap; the engine answers 409 in words once Stage 1 lands.
Defaults taken, awaiting a ruling
- One address per link today; several per link is Stage 2 of the build order.
- The Mac guest runs a version check but no library check; the phone does the reverse. Both will run the same list (spec §4) in Stage 3.
Screenshots wanted
- Settings › Sharing on the host with the address and the QR.
- The guest Mac’s Connect to Another Mac… sheet with a nearby host.
- The iPhone Connect screen after opening a link.