A problem starting right after a firmware update, a new host pairing or a software install should be checked against that specific change before a full reset. For Apple Watch pairing with iPhone, first place devices together, update iPhone and confirm the watch is not locked to another account.
What this covers
- Apple Watch pairing with iPhone with this exact failure state
- Diagnosis across watch/iPhone eligibility versus account, Bluetooth, Wi-Fi, activation lock and backup
What it does not cover
Try in this order
0 of 4 completedCapture the exact failure state
ReversibleNote the exact firmware version or newly paired host, and confirm the prior working state. Expected behavior: complete secure pairing to one compatible current iPhone.
Isolate the component boundary
ReversiblePlace devices together, update iPhone and confirm the watch is not locked to another account. Test with the new pairing removed, or check for a known-issue note for the firmware version. Boundary to separate: watch/iPhone eligibility versus account, Bluetooth, Wi-Fi, activation lock and backup.
Correct only the proven cause
ReversibleRestart/retry or erase only with ownership credentials and backup consequences understood. Apply the vendor's fix for the update, or remove the conflicting extra pairing.
Verify and stop safely
ReversibleConfirm normal operation with the change present across at least one full session. Never share activation credentials or remove the only health-data copy.
Evidence ledger
Sources behind this answer
Exact questions