Bot提示已上线且go-cqhttp能正常收到消息，但是Bot不做处理 #145

sakurayun · 2021-02-17T03:15:02Z

sakurayun
Feb 17, 2021

Bot提示已上线且go-cqhttp能正常收到消息，但是Bot不做处理
而同时共用go-cqhttp的另一个bot却能正常接收消息并处理
使用npm run test输出日志如下：
(node:2992) UnhandledPromiseRejectionWarning: TypeError: context.message.charAt is not a function at commonHandle (C:\Users\Administrator\Desktop\cq-picsearcher-bot-master\ma in.js:151:37) at groupMsg (C:\Users\Administrator\Desktop\cq-picsearcher-bot-master\main.j s:325:7) at CQEventBus._emitThroughHierarchy (C:\Users\Administrator\Desktop\cq-picse archer-bot-master\node_modules\cq-websocket\src\event-bus.js:157:46) at CQEventBus.emit (C:\Users\Administrator\Desktop\cq-picsearcher-bot-master \node_modules\cq-websocket\src\event-bus.js:131:17) at Function._handle (C:\Users\Administrator\Desktop\cq-picsearcher-bot-maste r\node_modules\cq-websocket\src\index.js:237:32) at W3CWebSocket._onMessage (C:\Users\Administrator\Desktop\cq-picsearcher-bo t-master\node_modules\cq-websocket\src\index.js:451:18) at W3CWebSocket._dispatchEvent [as dispatchEvent] (C:\Users\Administrator\De sktop\cq-picsearcher-bot-master\node_modules\yaeti\lib\EventTarget.js:115:12) at W3CWebSocket.onMessage (C:\Users\Administrator\Desktop\cq-picsearcher-bot -master\node_modules\websocket\lib\W3CWebSocket.js:234:14) at WebSocketConnection.<anonymous> (C:\Users\Administrator\Desktop\cq-picsea rcher-bot-master\node_modules\websocket\lib\W3CWebSocket.js:205:19) at WebSocketConnection.emit (events.js:315:20) (Usenode --trace-warnings ...to show where the warning was created) (node:2992) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To termina te the node process on unhandled promise rejection, use the CLI flag--unhandle
d-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejectio
ns_mode). (rejection id: 2)
(node:2992) [DEP0018] DeprecationWarning: Unhandled promise rejections are depre
cated. In the future, promise rejections that are not handled will terminate the
Node.js process with a non-zero exit code.

`