Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Device re-pairing required after minor macOS update on already-paired device [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#62176•Fetched 2026-04-08 03:08:03
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
bo-bluebo-blue
Participants
bo-bluebo-blue
Timeline (top)
cross-referenced ×1

After a macOS point release update (26.3.1 → 26.4.0) and reboot, the gateway rejects the companion app's WebSocket connection with code=1008 reason=pairing required, even though the device (bo-mini) is already paired with both node and operator roles.

The gateway logs show a metadata-upgrade security audit where claimedPlatform=macOS 26.4.0 doesn't match pinnedPlatform=macOS 26.3.1. The connection is rejected repeatedly until a human manually runs openclaw devices approve --latest to re-approve the repair pairing.

Root Cause

After a macOS point release update (26.3.1 → 26.4.0) and reboot, the gateway rejects the companion app's WebSocket connection with code=1008 reason=pairing required, even though the device (bo-mini) is already paired with both node and operator roles.

The gateway logs show a metadata-upgrade security audit where claimedPlatform=macOS 26.4.0 doesn't match pinnedPlatform=macOS 26.3.1. The connection is rejected repeatedly until a human manually runs openclaw devices approve --latest to re-approve the repair pairing.

Fix Action

Fix / Workaround

Auto-approve metadata-upgrade requests when:

  • The device is already paired
  • Only the OS minor/patch version changed
  • The device family and hardware fingerprint remain the same
RAW_BUFFERClick to expand / collapse

Summary

After a macOS point release update (26.3.1 → 26.4.0) and reboot, the gateway rejects the companion app's WebSocket connection with code=1008 reason=pairing required, even though the device (bo-mini) is already paired with both node and operator roles.

The gateway logs show a metadata-upgrade security audit where claimedPlatform=macOS 26.4.0 doesn't match pinnedPlatform=macOS 26.3.1. The connection is rejected repeatedly until a human manually runs openclaw devices approve --latest to re-approve the repair pairing.

Steps to Reproduce

  1. Have a fully paired device (companion app connected to gateway)
  2. Apply a minor macOS update (e.g., 26.3.1 → 26.4.0)
  3. Reboot
  4. Observe companion app cannot reconnect — gateway rejects with pairing required

Expected Behavior

Minor OS version bumps on an already-paired device should be auto-approved (or at least auto-prompted in the companion app UI), not silently rejected in a retry loop. The device identity (hardware fingerprint) hasn't changed — only the OS version string.

Actual Behavior

  • Gateway rejects every WebSocket connection attempt with code=1008
  • Companion app retries aggressively (941 rejected connections observed in ~5 minutes)
  • No user-visible notification that re-pairing is needed
  • Requires CLI intervention: openclaw devices approve --latest

Environment

  • OpenClaw 2026.4.5 (3e72c03)
  • macOS 26.4.0 (upgraded from 26.3.1)
  • Gateway mode: local, port 18789
  • Companion app: OpenClaw/2026040501

Suggested Fix

Auto-approve metadata-upgrade requests when:

  • The device is already paired
  • Only the OS minor/patch version changed
  • The device family and hardware fingerprint remain the same

Or at minimum, surface the re-pairing requirement in the companion app UI instead of silently failing.

extent analysis

TL;DR

Auto-approve metadata-upgrade requests for minor OS version changes on already paired devices to resolve the WebSocket connection rejection issue.

Guidance

  • Verify that the device's hardware fingerprint and family remain unchanged after the OS update to ensure auto-approval is safe.
  • Consider implementing a UI prompt in the companion app to notify users of the required re-pairing when a minor OS version update occurs.
  • Review the OpenClaw documentation to see if there are any existing configuration options or flags that can be used to auto-approve metadata-upgrade requests for minor OS version changes.
  • Evaluate the feasibility of adding a version tolerance or range to the pairing approval process to accommodate minor OS updates.

Example

No specific code example is provided as the issue does not explicitly mention the programming language or API used.

Notes

The suggested fix assumes that the device's identity and security posture remain unchanged after a minor OS update. However, this may not always be the case, and additional security considerations may be necessary.

Recommendation

Apply a workaround by running openclaw devices approve --latest after each minor OS update until a permanent fix is implemented, as this provides a temporary solution to the connection rejection issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#tensor shape#autograd error#model save/load#optimization#mixed precision

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING