PairLinkHELP WITHOUT THE GUESSWORK
Start with
what happened.
Keep your records safe. Inspect the connection, permissions and receipts before taking a repair action.
Connected, but no health data?
Bluetooth connected is not the same as an authenticated PairLink session or a successful Apple Health write. Check Connection, then the sync receipt: received, written, duplicate, rejected and queued counts tell different parts of the story.
A metric is missing?
Open Compatibility in the iPhone app. A vendor’s watch app can display a reading without offering a source PairLink can access. Do not repeatedly re-pair to recover an unavailable metric.
Will it work when both apps are minimised?
Background syncing is part of the product, but foreground success alone does not prove it. Permissions, battery mode and operating-system scheduling affect delivery. Check the timestamp and remaining queue rather than assuming continuous delivery.
Why did a workout arrive after it ended?
PairLink imports completed sessions from accessible sources; it does not promise to mirror an active vendor workout. If its workout code is unfamiliar, link it to the correct exercise name when prompted.
Something looks wrong in Apple Health?
Check the source, timestamp and unit. Use PairLink Diagnostics for supported, scoped corrections. Do not delete all Apple Health data or clear watch queues. Keep a redacted receipt for investigation.
The watch keeps rebooting or a button is stuck?
A physically held button can trigger hardware-level actions. PairLink cannot repair it. Avoid repeated reboots or factory resets as a sync remedy; seek hardware service.
How do I share a useful issue report?
Record the phone/watch models, OS and firmware versions, PairLink build, approximate time and reproduction steps. Redact names, messages, pairing codes, health values and identifiers before sharing. A public support inbox is not yet published on this preview.