Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[BUG] chats.update / initial history sync discard the archived flag before it reaches webhooks or the database

オープン
  • 何か問題がありますか？
#2,743 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 5 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
67/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
postgresql, typescript
領域
api, backend, databases

調査の方向性

Start in whatsapp.baileys.service.ts and compare the chats.update and messaging-history.set handlers with the compiled path cited in the issue. Then inspect the Prisma Chat model and the findChats flow. Done means archived state reaches webhook payloads, persists on Chat rows, and is returned by findChats, with the relevant migration and tests or reproduction checks passing.

索引モデルが issue の本文から書いたものです。

説明

📋 Bug Description

When a chat is archived/unarchived on the phone (or any linked device), Baileys emits the change via chats.update with an archived: true/false field. Evolution's chats.update handler in whatsapp.baileys.service.ts (WHATSAPP-BAILEYS integration) discards every field except remoteJid before forwarding to the webhook or writing to the DB:

"chats.update": async (e) => {
  const chatsRaw = e.map(chat => ({ remoteJid: chat.id, instanceId: this.instanceId }));
  this.sendDataWebhook('chats.update', chatsRaw);
  for (const chat of e)
    await this.prismaRepository.chat.updateMany({
      where: { instanceId: this.instanceId, remoteJid: chat.id, name: chat.name },
      data: { remoteJid: chat.id },
    });
}

(from compiled dist/api/integrations/channel/whatsapp/whatsapp.baileys.service.js, v2.3.7)

The messaging-history.set handler (emits chats.set) does the same trim, and additionally only forwards chats not already in the Chat table — so even a fresh reconnect can't backfill archive state for chats Evolution already knows about.

The Chat Postgres table also has no archived column at all:

Table "public.Chat"
id | remoteJid | labels | createdAt | updatedAt | instanceId | name | unreadMessages

So there is currently no way for an integrator to learn a chat's real archived state via webhook, DB, or GET /chat/findChats/:instance — it's dropped at the earliest point in Evolution's own pipeline.

🔄 Steps to Reproduce

  1. Connect an instance (WHATSAPP-BAILEYS) with the chats.update webhook enabled.
  2. Archive (or unarchive) any chat directly on the linked phone.
  3. Inspect the delivered chats.update webhook payload.
  4. Check the Chat row for that remoteJid via GET /chat/findChats/:instance or Postgres directly.

✅ Expected Behavior

chats.update carries the chat's current archived boolean, it's persisted on the Chat row, and findChats returns it — so integrators can mirror the phone's real archived list instead of maintaining a local-only flag.

❌ Actual Behavior

chats.update/chats.set payloads only ever contain {remoteJid, instanceId[, name]}. archived is silently discarded.

🌍 Environment

  • OS: Ubuntu (Docker host)
  • Evolution API version: 2.3.7
  • Integration: WHATSAPP-BAILEYS
  • Database: PostgreSQL 13

📝 Additional Context / Proposed Fix

Sketch of a fix, for whoever picks this up:

  1. Add archived Boolean @default(false) to the Chat Prisma model (migration).
  2. In chats.update, forward archived: chat.archived in the webhook payload and include it in the chat.updateMany write.
  3. In messaging-history.set, same field addition; consider also letting already-known chats' archived/pinned/muteEndTime refresh on reconnect, since today only brand-new chats get forwarded at all.
  4. Confirm findChats selects/returns the new column once it exists.

Related: #2495 looks like a different symptom in the same area (write-side archiveChat endpoint erroring) — this is the read side: archive state never reaching the integrator in the first place.

主要言語
TypeScript
スター
9.9k
フォーク
7.4k
30日以内にマージされた PR はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

evolution-foundation/evolution-api のほかの issue

evolution-foundation/evolution-api の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。