mirror of
https://github.com/openclaw/openclaw.git
synced 2026-05-18 19:04:45 +00:00
c0a65ba75e
When the imsg private API bridge is not attached to Messages.app,
`handleAction` throws and the model receives a `success:false` tool
result with a "Run imsg launch" hint. The throw never reaches the
gateway log, so an operator has no signal that an outbound reply was
silently dropped — `~/.openclaw/logs/openclaw.log` stays quiet and
`openclaw channels status` continues to report the channel as
`enabled, configured, running`.
Add a `channels/imessage` subsystem WARN log right before the throw
so the silent-drop is visible to log-tailing tooling and operators
without changing the tool result shape or the model-facing error
message. Cover the path with a regression test that asserts the WARN
fires once with the documented format and that the underlying send
adapter is never called on the failure path.
Admin-merged: required CI failures (check-lint, check-test-types,
check-additional-extension-bundled) are pre-existing upstream errors
in extensions/{codex,discord,googlechat,memory-core,slack,
synology-chat,telegram,irc,line,nextcloud-talk,qqbot} test files
that affect every open PR and are unrelated to this change. PR diff
is restricted to extensions/imessage/.