A provider shows no gauge or appears unavailable
A provider shows no gauge or appears unavailable
QR code scanned but iPhone cannot connect
QR code scanned but iPhone cannot connect
Step 1: Check Tailscale.
If you are using local/Tailscale transport, Continuum warns “Tailscale installed but not running” when it detects Tailscale is present but the backend is off. Start Tailscale on both Mac and iPhone.Step 2: Try MagicDNS.
In Mac Settings → Pairing, enable “Prefer MagicDNS host in pairing QR.” MagicDNS hostnames survive sleep, wake, and Wi-Fi switching; raw IP addresses do not.Step 3: Regenerate the QR.
QR codes have a 15-minute TTL. Go to Settings → Pairing → Regenerate and scan the new code.Step 4: Use Copy URL.
In the Mac dashboard QR popover, click Copy URL and paste the pairing URL directly into the iPhone pairing flow. This bypasses any QR-scanning issues.Step 5: Check the daemon port.
The daemon starts at port
21731 and falls back through 21741. Confirm the daemon is listening: lsof -i :21731. If none of those ports are available, a conflicting process may be blocking the daemon.iPhone Analytics shows 'Waiting for Mac sync'
iPhone Analytics shows 'Waiting for Mac sync'
This is expected behavior when the iPhone app is built with a personal (free) Apple Developer account. The analytics sync between Mac and iPhone uses iCloud Key-Value storage, which requires a paid Apple Developer Program membership to sign the required entitlement.On personal team builds, the iPhone analytics tab shows “Waiting for Mac sync” and remains empty until you upgrade to a paid Apple Developer Program account and rebuild with the iCloud entitlement signed.There is no workaround within the app today.
iPhone shows an 'Update Continuum on the Mac' banner
iPhone shows an 'Update Continuum on the Mac' banner
Port already in use
Port already in use
The daemon HTTP listener starts at port Quit the conflicting process, then restart Continuum.
21731 and tries fallback ports through 21741. If all ports in that range are occupied, the daemon fails to start.Find the conflicting process:Where are the diagnostic logs?
Where are the diagnostic logs?
In-app: go to Settings → Diagnostics. This surfaces an audit log browser (sends, swaps, autopilot events) and an optional wire inspector. The wire inspector is off by default and must be enabled; it captures up to 500 recent daemon requests and responses.On disk: audit JSONL files are at
~/.clawdmeter/audit/:~/.clawdmeter/audit/sends.jsonl~/.clawdmeter/audit/swaps.jsonl~/.clawdmeter/audit/autopilot.jsonl~/.clawdmeter/audit/mobile-commands.jsonl