@vanzxy/baileys 1.6.7 → 1.6.8

package/lib/Utils/MessageBuilder.js

@@ -2977,6 +2977,14 @@ class AIRich extends BaseBuilder {
 	addWidget(data = {}, { layout } = {}) {
 		const items = Array.isArray(data) ? data : [data];
 
+		// Vanz@Fix (bug 44) --- layout: 'Single' forces `widgets[0]` below (a "Single" layout's
+		// view_model can only ever hold one `primitive`, never a `primitives` array — see
+		// newLayout()). Previously an explicit { layout: 'Single' } combined with a multi-item
+		// array silently dropped every item past the first with no error. Fail loud instead.
+		if (layout === 'Single' && items.length > 1) {
+			throw new TypeError(`addWidget(): layout "Single" can only hold one widget (got ${items.length}) — use "HScroll"/"ActionRow" (or omit layout) for multiple`);
+		}
+
 		items.forEach((item, i) => {
 			// header.title or top-level title required
 			const hasTitle = item?.title || item?.header?.title;
@@ -2994,6 +3002,13 @@ class AIRich extends BaseBuilder {
 			messageText: items.map((item) => item.header?.title ?? item.title).join(', '),
 		});
 
+		// Vanz@Fix (bug 45) --- auto tool_call_id used to be `idx` scoped per-item (ctas.map's own
+		// index), resetting to 0 for every widget item. Two items (or two separate addWidget()
+		// calls) that both omit tool_call_id/id ended up minting the identical auto id ("00"),
+		// so a CTA tap could route to the wrong widget's tool call. Track the counter on the
+		// instance instead so every auto-generated id is unique for this AIRich's lifetime.
+		this._widgetCtaCounter ??= 0;
+
 		const widgets = items.map((item) => {
 			const ctas = item.ctas ?? item.actions;
 			// header accepts either a string title (legacy) or an object { title, subtitle }
@@ -3007,11 +3022,11 @@ class AIRich extends BaseBuilder {
 				},
 				body: {
 					sections: item.sections ?? [],
-					ctas: ctas.map((cta, idx) => ({
+					ctas: ctas.map((cta) => ({
 						label: cta.label ?? '',
 						state: cta.state ?? 'PENDING',
 						kind: cta.kind ?? 'OTHER',
-						tool_call_id: cta.tool_call_id ?? cta.id ?? String(idx).padStart(2, '0'),
+						tool_call_id: cta.tool_call_id ?? cta.id ?? String(this._widgetCtaCounter++).padStart(2, '0'),
 						...(cta.toast !== false && {
 							toast: { label: typeof cta.toast === 'string' ? cta.toast : headerTitle, __typename: 'GenAI3PExtWidgetToast' },
 						}),

package/lib/Utils/anti-delete.js

@@ -80,12 +80,20 @@ export class MessageStore {
         stored.isDeleted = true;
         stored.deletedAt = now;
         stored.deletedBy = deletedBy;
+        // Vanz@Fix (bug 66): the old check (`deletedBy === stored.message.key.participant`)
+        // only works in groups, where `participant` identifies who sent/revoked a message.
+        // In a private chat `key.participant` is always undefined (it's a group-only field),
+        // while `deletedBy` there falls back to `remoteJid` — so the comparison could never
+        // match and isRevokedBySender was always false for every DM, even though
+        // delete-for-everyone in a DM can only be done by the original sender. Treat a
+        // missing `participant` (i.e. not a group message) as "revoked by sender" by definition.
+        const isGroupMessage = !!stored.message.key.participant;
         const info = {
             originalMessage: stored.message,
             key,
             deletedAt: now,
             deletedBy,
-            isRevokedBySender: !deletedBy || deletedBy === stored.message.key.participant
+            isRevokedBySender: !deletedBy || !isGroupMessage || deletedBy === stored.message.key.participant
         };
         this.deletedMessages.set(this.getKey(key), info);
         return info;

package/lib/Utils/generics.js

@@ -71,7 +71,25 @@ export const encodeBigEndian = (e, t = 4) => {
 };
 export const toNumber = (t) => typeof t === 'object' && t ? ('toNumber' in t ? t.toNumber() : t.low) : t || 0;
 /** unix timestamp of a date in seconds */
-export const unixTimestampSeconds = (date = new Date()) => date.getTime() / 1000 | 0;
+// Vanz@Fix (bug 69): unixTimestampSeconds(date) assumed `date` is always a real Date
+// instance and called date.getTime() unconditionally. Any caller that passed a raw
+// number (Date.now(), or an already-converted unix timestamp) or an ISO string instead
+// of a Date crashed here with "date.getTime is not a function" — this is a coercion
+// bug in THIS function, not a proto/BloksWidget/InteractiveMessage issue (traced and
+// confirmed: normalizeMessageContent/getContentType never touch nested message content,
+// and this function is called before any encode/serialize step even starts). Coerce the
+// common input shapes instead of assuming Date, but keep throwing on genuinely invalid
+// input (NaN) so silent bad-timestamp bugs don't get hidden.
+export const unixTimestampSeconds = (date) => {
+    if (date == null) date = new Date(); // null AND undefined both mean "now" (default params only catch undefined)
+    const d = date instanceof Date
+        ? date
+        : new Date(typeof date === 'number' && date < 1e12 ? date * 1000 : date); // treat sub-1e12 numbers as already-seconds
+    if (Number.isNaN(d.getTime())) {
+        throw new TypeError(`unixTimestampSeconds: invalid timestamp input (${typeof date}): ${date}`);
+    }
+    return d.getTime() / 1000 | 0;
+};
 export const debouncedTimeout = (intervalMs = 1000, task) => {
     let timeout;
     return {

package/lib/Utils/media-set.js

@@ -145,7 +145,11 @@ export const groupLabel = async (jid, text, sock) => {
                 type: 30,
                 memberLabel: {
                     label: text.slice(0, 30),
-                    labelTimestamp: Date.now()
+                    // Vanz@Fix (bug 67): this used Date.now() (milliseconds) while the
+                    // sibling groupSetMemberLabel() correctly uses unixTimestampSeconds()
+                    // for the same proto field — WA's *Timestamp fields are unix-seconds,
+                    // so this was sending a timestamp ~1000x too large.
+                    labelTimestamp: unixTimestampSeconds() || Date.now()
                 }
             }
         }, {

package/lib/WABinary/generic-utils.js

@@ -160,7 +160,9 @@ const FLOWS_MAP = {
     // routed anything real; kept as a harmless alias in case any external caller
     // is still constructing a raw button object with the old (wrong) name.
     flow: true,
-    flow_action: true,
+    // Vanz@Fix (bug 68): removed duplicate `flow_action: true` key — already declared
+    // above (Vanzxy extended button types block); this was a leftover copy-paste dupe,
+    // harmless (same value) but confusing on re-read.
     // Vanz@Fix (single_select never renders alone) --- single_select must NEVER get
     // its own dedicated native_flow node here. WhatsApp only renders a single_select
     // button through the generic <native_flow v='9' name='mixed'> node — the same one

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vanzxy/baileys",
-  "version": "1.6.7",
+  "version": "1.6.8",
   "description": "Enhanced Baileys fork by Vanzxy \u2014 based on @itsliaaa/baileys + @whiskeysockets/baileys with fixes for audio group status and clean media without newsletter button.",
   "type": "module",
   "main": "./lib/index.js",