openclaw - 💡(How to fix) Fix [Bug] metadata-upgrade re-approval requestId expires in ~1-2s, no UI prompt — still broken on macOS 26.5.0 (regression from #62176)

Official PRs (…)
ON THIS PAGE

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…

#62176 was closed as resolved, but the metadata-upgrade re-approval flow is still broken. Hit this today after macOS updated from 26.3.1 → 26.5.0 on an already-paired Mac mini.

Error Message

security audit: device metadata upgrade requested reason=metadata-upgrade device=f8f00f95... claimedPlatform=macOS 26.5.0 pinnedPlatform=macOS 26.3.1
closed before connect code=1008 reason=pairing required: device identity changed and must be re-approved (requestId: ...)

Related closed issue: #62176

Root Cause

#62176 was closed as resolved, but the metadata-upgrade re-approval flow is still broken. Hit this today after macOS updated from 26.3.1 → 26.5.0 on an already-paired Mac mini.

Fix Action

Fix / Workaround

  • The device retries the connection in a tight loop, generating a new requestId every ~1–2 seconds
  • Each requestId expires before any human can run openclaw devices approve <requestId> manually
  • openclaw nodes pending and the agent nodes tool return emptyisRepair: true requests are invisible there, only visible in openclaw devices list
  • No prompt in the companion app UI, no prompt in Control UI, no /pair approve command exists
  • The only working workaround: script openclaw devices list --json + openclaw devices approve in a single atomic shell pipeline to beat the expiry

Code Example

security audit: device metadata upgrade requested reason=metadata-upgrade device=f8f00f95... claimedPlatform=macOS 26.5.0 pinnedPlatform=macOS 26.3.1
closed before connect code=1008 reason=pairing required: device identity changed and must be re-approved (requestId: ...)
RAW_BUFFERClick to expand / collapse

Summary

#62176 was closed as resolved, but the metadata-upgrade re-approval flow is still broken. Hit this today after macOS updated from 26.3.1 → 26.5.0 on an already-paired Mac mini.

Steps to Reproduce

  1. Have a paired openclaw-macos device (ui mode) with both node and operator roles
  2. Update macOS to a new point release (e.g. 26.3.1 → 26.5.0)
  3. Reboot / restart OpenClaw
  4. Gateway detects metadata-upgrade (claimedPlatformpinnedPlatform) and rejects the connection with code=1008 reason=pairing required: device identity changed and must be re-approved

Actual Behavior

  • The device retries the connection in a tight loop, generating a new requestId every ~1–2 seconds
  • Each requestId expires before any human can run openclaw devices approve <requestId> manually
  • openclaw nodes pending and the agent nodes tool return emptyisRepair: true requests are invisible there, only visible in openclaw devices list
  • No prompt in the companion app UI, no prompt in Control UI, no /pair approve command exists
  • The only working workaround: script openclaw devices list --json + openclaw devices approve in a single atomic shell pipeline to beat the expiry

Expected Behavior

  • requestId TTL for isRepair / metadata-upgrade requests should be much longer (minutes, not ~1–2 seconds)
  • The companion macOS app should surface a visible re-approval banner/prompt when stuck in this state
  • OR: minor OS point release bumps on the same device hardware should be auto-approved

Environment

  • OpenClaw gateway: v2026.5.26
  • OpenClaw macOS app: v2026.5.22
  • macOS: 26.3.1 → 26.5.0
  • Client: openclaw-macos, clientMode: ui, roles: node + operator
  • Device: Mac mini (Mac14,3)

Logs

security audit: device metadata upgrade requested reason=metadata-upgrade device=f8f00f95... claimedPlatform=macOS 26.5.0 pinnedPlatform=macOS 26.3.1
closed before connect code=1008 reason=pairing required: device identity changed and must be re-approved (requestId: ...)

Related closed issue: #62176

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING