#🐛 BUG: Mac App v2026.2.17-2.19 - Critical Issues (AVAudioEngine Crash + Connection Mode)

1 messages · Page 1 of 1 (latest)

storm badger
#

Hi! I'm experiencing critical bugs with the OpenClaw Mac app versions 2026.2.17-2.19 on macOS 26.3.0:

Issue 1: AVAudioEngine Crash Loop

  • Mac app consumes 200%+ CPU immediately after launch
  • Repeated crashes from audio engine exception
  • Voice Wake feature cannot be disabled (setting not saved)
  • Crash trace: AVAudioEngineImpl::InstallTapOnNode → MicLevelMonitor.start → VoiceWakeSettings.restartMeter

Issue 2: Connection Mode Bug

  • Mac app tries to connect as "role: node" instead of local client
  • Gateway rejects with "unauthorized role: node"
  • Causes web dashboard to disconnect when Mac app launches
  • Even setting connectionMode = local in plist doesn't fix it

Workaround Found:
Downgrading to v2026.2.15 fixes both issues - CPU now 2.5% and everything works.

Environment:

  • macOS 26.3.0 (Mac16,10)
  • OpenClaw CLI: 2026.2.19-2
  • Gateway: 2026.2.19-2 on 127.0.0.1:18789

Full bug report with crash logs and details available if needed. This appears to be a regression between v2026.2.15 and v2026.2.17.

silent parcelBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

severe valveBOT
#

That sounds like a real regression — and the “downgrade to v2026.2.15” workaround is totally reasonable for now.

A couple notes / things to try that might separate “expected behavior” from “bug”:

Issue 2 (“unauthorized role: node” / connection mode)

The macOS app is supposed to present itself as a node (so it can expose canvas/system.run/etc). So seeing role: node isn’t automatically wrong.

What is wrong is the gateway rejecting it as unauthorized. In current builds, node connectivity is gated by device pairing (not the old openclaw nodes pending/approve flow).

Try this while launching the app (on v2026.2.17+):

  1. Run: openclaw devices list
  2. If you see a pending request for the Mac app/device, run: openclaw devices approve <requestId>
  3. Then relaunch the app and check if it stays connected.

If it still fails, the most useful next artifact is a short snippet from:

  • openclaw logs --follow
    right when the app attempts to connect (redact tokens/secrets).
#

Docs reference (so we’re aligned on the intended flow): https://docs.openclaw.ai/nodes (pairing section)

Issue 1 (AVAudioEngine crash loop / 200% CPU)

Given the stack (InstallTapOnNode → MicLevelMonitor.start → VoiceWakeSettings.restartMeter) this smells like a meter/tap getting re-installed repeatedly (or installed in an invalid state) and the settings toggle not persisting makes it worse.

Two quick “contain the blast radius” tests:

  • In System Settings → Privacy & Security → Microphone, temporarily disable microphone access for OpenClaw and relaunch.
    If the crash loop stops, it’s almost certainly the mic meter / tap lifecycle.
  • If you can’t reach settings without it spinning: stay on v2026.2.15 until there’s a fixed build.

For a proper fix (what maintainers will need)

If you can paste/upload these, it’ll make the bug actionable quickly:

  • The .crash report from ~/Library/Logs/DiagnosticReports/ (OpenClaw*.crash)
  • openclaw logs --follow around both:
    • the node connect attempt (unauthorized role: node)
    • the voice wake/mic meter start
  • Whether Mic + Speech permissions were granted, and which input device is selected