Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: 2026.4.25 stable breaks Intel macOS LaunchAgent + BlueBubbles after upgrade from 4.23; rollback restores service [2 comments, 2 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#72909•Fetched 2026-04-28 06:30:24
View on GitHub
Comments
2
Participants
2
Timeline
4
Reactions
0
Author
SoumyaBanerjee2025SoumyaBanerjee2025
Participants
SoumyaBanerjee2025SoumyaBanerjee2025steipetesteipete
Timeline (top)
commented ×2closed ×1cross-referenced ×1

Upgrading a stable OpenClaw 2026.4.23 install to 2026.4.25 stable caused a macOS LaunchAgent-managed gateway to appear partially alive, but BlueBubbles/iMessage delivery became unreliable/unusable. CLI/channel probes were slow or timing out, the agent stopped responding consistently over iMessage, and logs showed a 2026.4.25 plugin-runtime-deps module failure during BlueBubbles catchup.

Rolling back to 2026.4.23 and restoring the pre-upgrade config restored normal service.

This looks related to #72848 and possibly #72846, but this report includes a BlueBubbles/runtime-deps failure on macOS Intel.

Error Message

Error [ERR_MODULE_NOT_FOUND]: Cannot find module

Root Cause

Upgrading a stable OpenClaw 2026.4.23 install to 2026.4.25 stable caused a macOS LaunchAgent-managed gateway to appear partially alive, but BlueBubbles/iMessage delivery became unreliable/unusable. CLI/channel probes were slow or timing out, the agent stopped responding consistently over iMessage, and logs showed a 2026.4.25 plugin-runtime-deps module failure during BlueBubbles catchup.

Rolling back to 2026.4.23 and restoring the pre-upgrade config restored normal service.

This looks related to #72848 and possibly #72846, but this report includes a BlueBubbles/runtime-deps failure on macOS Intel.

Fix Action

Fix / Workaround

  1. Start from a working 2026.4.23 install on macOS Intel with BlueBubbles configured.
  2. Upgrade to 2026.4.25 stable.
  3. Restart gateway / LaunchAgent.
  4. Send iMessage to the BlueBubbles-backed agent.
  5. Observe gateway/channel instability or no response.
  6. Roll back to 2026.4.23 and restore the previous config.
  7. BlueBubbles works again.

Code Example

[bluebubbles] [default] BlueBubbles catchup: unexpected failure:
Error [ERR_MODULE_NOT_FOUND]: Cannot find module
'/Users/<user>/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-17c3fa238f70/dist/paths-BFfL0I8G.js'
imported from
'/Users/<user>/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-17c3fa238f70/dist/catchup-3W0avzeW.js'

---

Config was last written by a newer OpenClaw (2026.4.25); current version is 2026.4.24.

---

OpenClaw 2026.4.23 (a979721)
Gateway reachable.
BlueBubbles default: enabled, configured, running, connected, works
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

Upgrading a stable OpenClaw 2026.4.23 install to 2026.4.25 stable caused a macOS LaunchAgent-managed gateway to appear partially alive, but BlueBubbles/iMessage delivery became unreliable/unusable. CLI/channel probes were slow or timing out, the agent stopped responding consistently over iMessage, and logs showed a 2026.4.25 plugin-runtime-deps module failure during BlueBubbles catchup.

Rolling back to 2026.4.23 and restoring the pre-upgrade config restored normal service.

This looks related to #72848 and possibly #72846, but this report includes a BlueBubbles/runtime-deps failure on macOS Intel.

Environment

  • OpenClaw before upgrade: 2026.4.23
  • OpenClaw attempted upgrade: 2026.4.25 stable
  • Rollback target: 2026.4.23
  • OS: macOS on Intel MacBook Air 2019
  • Gateway service: macOS LaunchAgent
  • Channel: BlueBubbles / iMessage
  • Machine role: headless always-on Mac

Steps to reproduce

  1. Start from a working 2026.4.23 install on macOS Intel with BlueBubbles configured.
  2. Upgrade to 2026.4.25 stable.
  3. Restart gateway / LaunchAgent.
  4. Send iMessage to the BlueBubbles-backed agent.
  5. Observe gateway/channel instability or no response.
  6. Roll back to 2026.4.23 and restore the previous config.
  7. BlueBubbles works again.

Expected behavior

After upgrading to 2026.4.25, the LaunchAgent gateway should restart cleanly and BlueBubbles catchup/reply handling should continue working.

Actual behavior

After upgrade, gateway/channel behavior became unreliable. BlueBubbles did not consistently process/respond. Logs included a plugin runtime dependency failure:

[bluebubbles] [default] BlueBubbles catchup: unexpected failure:
Error [ERR_MODULE_NOT_FOUND]: Cannot find module
'/Users/<user>/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-17c3fa238f70/dist/paths-BFfL0I8G.js'
imported from
'/Users/<user>/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-17c3fa238f70/dist/catchup-3W0avzeW.js'

During rollback testing, logs also showed newer-version config contamination when trying 2026.4.24 after 2026.4.25:

Config was last written by a newer OpenClaw (2026.4.25); current version is 2026.4.24.

After rolling back to 2026.4.23 and restoring the pre-upgrade config, channel probe succeeds:

OpenClaw 2026.4.23 (a979721)
Gateway reachable.
BlueBubbles default: enabled, configured, running, connected, works

Impact

High for BlueBubbles/iMessage users on macOS Intel. The gateway can appear present, but the agent becomes unavailable or unreliable until rollback.

Related issues

  • #72848: OpenClaw no longer works after update from 4.23 to 4.24/4.25 on Intel Mac
  • #72846: v2026.4.25 channel sidecar startup regression after ready

extent analysis

TL;DR

Downgrade to OpenClaw 2026.4.23 to restore reliable BlueBubbles/iMessage delivery on macOS Intel.

Guidance

  • Verify the issue is specific to the upgrade from 2026.4.23 to 2026.4.25 by checking the logs for the ERR_MODULE_NOT_FOUND error and the Config was last written by a newer OpenClaw warning.
  • Attempt to roll back to 2026.4.24 to see if the issue persists, but be aware of potential config contamination.
  • Check the plugin-runtime-deps module for any version mismatches or corruption.
  • Consider monitoring related issues #72848 and #72846 for potential fixes or workarounds.

Example

No code snippet is provided as the issue seems to be related to version compatibility and configuration rather than code.

Notes

The issue appears to be specific to the upgrade from 2026.4.23 to 2026.4.25 on macOS Intel, and downgrading to 2026.4.23 restores normal service. However, it's unclear if this is a permanent fix or just a temporary workaround.

Recommendation

Apply workaround: Downgrade to OpenClaw 2026.4.23, as it has been confirmed to restore reliable BlueBubbles/iMessage delivery on macOS Intel. This is a temporary solution until a fix for the compatibility issue is released.

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…

FAQ

Expected behavior

After upgrading to 2026.4.25, the LaunchAgent gateway should restart cleanly and BlueBubbles catchup/reply handling should continue working.

#training loop#device allocation#model download#tokenizer error#prompt formatting

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: 2026.4.25 stable breaks Intel macOS LaunchAgent + BlueBubbles after upgrade from 4.23; rollback restores service [2 comments, 2 participants]