Editing a text message sets Message.message to JSON null, crashing Manager chat view

[elhanank1]

Description

Every time a WhatsApp text message (messageType: conversation) is edited by the sender,
the corresponding row in the Message table has its message column overwritten with a
JSON null instead of the updated content. This appears to be 100% reproducible in our
installation: every row with a MessageUpdate status of EDITED (2 out of 2 observed)
ended up with message = JSON null.

Impact

The Manager UI crashes when opening any chat containing such a message, with:
TypeError: Cannot read properties of null (reading 'contactMessage')
React Router catches it as an unhandled error and the chat screen renders blank/black —
the chat becomes permanently inaccessible in the Manager until the row is fixed directly
in the database.

Environment

• Evolution API version: 2.3.7
• Database: PostgreSQL
• Connector: Baileys (WhatsApp Web)
• Deployment: Docker (Coolify)

Steps to reproduce

1. Send a text message from a device (observed with Android as source).
2. Edit that message from the same device.
3. Query the Message table: the row's message column is now the JSON scalar null
   (not SQL NULL — "message"::text = 'null'), while MessageUpdate for that message
   shows a status of EDITED.
4. Open that chat in the Manager UI — it crashes with the TypeError above.

Suspected cause

The messages.update handler (Baileys service) appears to write the incoming update's
message field directly to the database without falling back to the previous/edited
message content when the update payload's message is empty, and the Manager's message
renderer does not null-check message before accessing message.contactMessage /
similar fields.

Workaround

We added a Postgres trigger that preserves the previous message value whenever an
UPDATE would set it to NULL/JSON null, which prevents the crash. Happy to share it,
but a proper fix in the update handler (and a null-check in the Manager renderer) would
be preferable.

[elhanank1]

Root cause identified

We captured the raw payload for a message-edit event on the same group chat mentioned above (120363107868026794@g.us). It confirms the root cause:

{
  "secretEncryptedMessage": {
    "encIv": "...",
    "encPayload": "...",
    "secretEncType": 2,
    "targetMessageKey": {
      "id": "A537CE10F9EE3A797B3F62FCF2DD817A",
      "fromMe": true,
      "remoteJid": "120363107868026794@g.us"
    }
  }
}

secretEncType: 2 corresponds to SecretEncryptedMessage.SecretEncType.MESSAGE_EDIT in Baileys' proto definitions (see https://baileys.wiki/docs/api/namespaces/proto/namespaces/Message/namespaces/SecretEncryptedMessage/enumerations/SecretEncType/). WhatsApp now delivers edited-message events wrapped in this additional encrypted layer (decrypted using a key derived from the target message), instead of the older plaintext edit/protocol-message structure.

The Baileys version bundled with Evolution 2.3.7 does not decrypt/handle secretEncryptedMessage, so it logs an "Unknown message type" and no readable content is extracted from the edit event. When Evolution's messages.update handler then persists this event, it writes the message column as JSON null instead of the edited content — which is what triggers the Manager crash described above.

This explains why the issue is 100% reproducible for us: every edited message we've seen (2/2) arrives via this new encrypted wrapper, which isn't supported yet, so every edit fails the same way. A real fix likely requires:

1. Baileys support for decrypting secretEncryptedMessage (type MESSAGE_EDIT), and
2. Evolution's update handler falling back gracefully (keep previous content, or a placeholder) when the incoming update can't be decoded, instead of persisting null.