wechaty/puppet-whatsapp

消息id中的_serialized异常

Open

#213 opened on Feb 16, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (23 forks)github user discovery
help wantedquestion

Repository metrics

Stars
 (26 stars)
PR merge metrics
 (PR metrics pending)

Description

message.id._serialized 总是以 true_ 开头，现在遇到一种情况是以 false_ 开头的，需要明确该消息的区别点:

该消息的 ack 为 0，但是该消息是由其他人发送给 bot 的，应该不会存在 ack: 0 的状态。

{
  "mediaKey": "cQWDFFa9Bw79WIdqyCwjeer9ACczi6VItT35/go+mjY=",
  "id": {
    "fromMe": false,
    "remote": "8618500946096@c.us",
    "id": "1FD65D39B65C521339FEB44D6BC0E731",
    "_serialized": "false_8618500946096@c.us_1FD65D39B65C521339FEB44D6BC0E731"
  },
  "ack": 0,
  "hasMedia": true,
  "body": "",
  "type": "image",
  "timestamp": 1644919439,
  "from": "8618500946096@c.us",
  "to": "8613126768525@c.us",
  "deviceType": "android",
  "isForwarded": false,
  "forwardingScore": 0,
  "isStatus": false,
  "isStarred": false,
  "broadcast": false,
  "fromMe": false,
  "hasQuotedMsg": false,
  "vCards": [],
  "mentionedIds": [],
  "isGif": false,
  "isEphemeral": false,
  "links": []
}

Contributor guide

Research direction
Investigate the message ID serialization logic in the WhatsApp puppet to understand when `fromMe` can be false while ack is 0, and whether this is expected behavior or a bug.
Tech stack
typescript
Domain
backendapi
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TypeScriptNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65