The "no payload" error you're encountering when calling the say method likely stems from deeper within the Wechaty framework or its underlying puppet implementation, rather than the presence or absence of users named "test" in context.Users. This error could be related to several factors, including unsupported Sayable types, missing or incorrect payload data, issues in creating new instances of Contact, Location, MiniProgram, UrlLink, or Post from the payload, or unhandled promise rejections in asynchronous operations.

The say method itself, as shown in your description, does not perform error handling that would directly result in a "no payload" error. It's possible that the error arises from the specific implementation of currentUser.say or from the underlying logic that handles message sending, which checks for payload validity or user existence.

Regarding the context.Users collection returning a count of 0 for users with the name "test", this could be due to the Wechaty instance not being started, no users with the name "test" existing within the scope of your search, incorrect implementation or usage of user modules, or restrictions based on Wechaty's permissions and user privacy settings.

To diagnose the "no payload" error further, more specific details about your implementation, including how you handle errors and the message sending logic, would be necessary.

Details

Sources

About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

Uh oh!

NetCore8，调用say方法，报错：no payload #44

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions