fix(imessage): self-explaining private-API failures and dedicated sen… · openclaw/openclaw@6c35c0d
omarshahine
·
2026-06-08
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -430,11 +430,17 @@ export const imessageMessageActions: ChannelMessageActionAdapter = {
|
430 | 430 | // disappeared — they only see "channel: running" in `channels status`. |
431 | 431 | // Common cause: gateway restart un-injects the imsg-bridge-helper.dylib |
432 | 432 | // from Messages.app while imsg rpc keeps running. |
| 433 | +// imsg's status message names the actual blocker (SIP, library |
| 434 | +// validation, macOS 26 AMFI gate) — append it so the operator isn't |
| 435 | +// told to "run imsg launch" when the OS is rejecting the dylib. |
| 436 | +const reason = privateApiStatus?.statusMessage |
| 437 | + ? ` imsg reports: ${privateApiStatus.statusMessage}` |
| 438 | + : ""; |
433 | 439 | log.warn( |
434 | | -`iMessage ${action} blocked: private API bridge unavailable (accountId=${account.accountId}, cliPath=${cliPathForProbe}). Run \`imsg launch\` to re-inject the dylib, then \`openclaw channels status\` to refresh.`, |
| 440 | +`iMessage ${action} blocked: private API bridge unavailable (accountId=${account.accountId}, cliPath=${cliPathForProbe}). Run \`imsg launch\` to re-inject the dylib, then \`openclaw channels status\` to refresh.${reason}`, |
435 | 441 | ); |
436 | 442 | throw new Error( |
437 | | -`iMessage ${action} requires the imsg private API bridge. Run imsg launch, then openclaw channels status to refresh capability detection.`, |
| 443 | +`iMessage ${action} requires the imsg private API bridge. Run imsg launch, then openclaw channels status to refresh capability detection.${reason}`, |
438 | 444 | ); |
439 | 445 | } |
440 | 446 | }; |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
