From af5ed0f0c5268c7e569d34f39fc11e56ea86d92c Mon Sep 17 00:00:00 2001
From: josedario87 <jodarioel87@gmail.com>
Date: Thu, 4 Dec 2025 12:38:09 -0600
Subject: [PATCH] Fix: shouldSyncHistoryMessage debe retornar true cuando no
 hay timestamp
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

El check inicial de Baileys pasa un objeto sin messageTimestamp.
Cuando era undefined, la comparación retornaba false y Baileys
deshabilitaba la sincronización de historial completamente.
---
 server/services/baileys/manager.ts | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/server/services/baileys/manager.ts b/server/services/baileys/manager.ts
index a83e18c..50c1905 100644
--- a/server/services/baileys/manager.ts
+++ b/server/services/baileys/manager.ts
@@ -159,9 +159,11 @@ class BaileysManager extends EventEmitter {
         syncFullHistory: true,
         markOnlineOnConnect: false,
         // Sync history messages from the last 30 days
+        // IMPORTANTE: Si no hay messageTimestamp, retornar true para permitir el check inicial de Baileys
         shouldSyncHistoryMessage: (msg) => {
+          if (!msg.messageTimestamp) return true
           const thirtyDaysAgo = Date.now() / 1000 - (30 * 24 * 60 * 60)
-          return msg.messageTimestamp! >= thirtyDaysAgo
+          return msg.messageTimestamp >= thirtyDaysAgo
         },
         // getMessage for resending/decrypting messages
         getMessage: async (key) => {