fix: allow msmsg decryption and emit view-once unavailable fanout

Two issues found during view-once testing on linked devices:

1. msmsg block removal:
   The "temporary fix" that discarded all msmsg-type encrypted messages
   was also blocking legitimate view-once messages. On linked devices,
   view-once arrives as msmsg encryption type. The block was originally
   added to prevent crashes from missing messageSecret, but the existing
   try/catch in the decrypt path already handles those errors gracefully
   by marking the message as a CIPHERTEXT stub.

2. view_once_unavailable_fanout emission:
   When a linked device receives a view-once, the WA server sends only
   <unavailable type="view_once"/> (no <enc> with actual media content).
   Previously this was silently acknowledged without emitting any event,
   so consumers (zpro, astra-api, etc.) never knew a view-once arrived.
   Now it emits the message as a CIPHERTEXT stub with key.isViewOnce=true
   so consumers can display "view-once message received" in their UI.

Co-Authored-By: Renato Alcara

WAProto/WAProto.proto

@@ -1,7 +1,7 @@
 syntax = "proto3";
 package proto;
 
-/// WhatsApp Version: 2.3000.1037753511
+/// WhatsApp Version: 2.3000.1037082622
 
 message ADVDeviceIdentity {
     optional uint32 rawId = 1;

src/Defaults/baileys-version.json

@@ -1 +1 @@
-{"version":[2,3000,1037786138]}
+{"version":[2,3000,1037137890]}

src/Defaults/index.ts

@@ -31,26 +31,9 @@ export const STATUS_EXPIRY_SECONDS = 24 * 60 * 60
 export const PLACEHOLDER_MAX_AGE_SECONDS = 7 * 24 * 60 * 60
 
 export const NOISE_MODE = 'Noise_XX_25519_AESGCM_SHA256\0\0\0\0'
-
-/**
- * Protocol mode: 'web' (default) or 'native' (experimental)
- * - web: WA\x06\x03 — standard WhatsApp Web protocol
- * - native: WAM\x05 — native Android protocol (may enable view-once media on companions)
- *
- * Set via BAILEYS_PROTOCOL env var:
- *   BAILEYS_PROTOCOL=native
- */
-const PROTOCOL_MODE = process.env.BAILEYS_PROTOCOL?.trim().toLowerCase() === 'native' ? 'native' : 'web'
-
-export const DICT_VERSION = PROTOCOL_MODE === 'native' ? 5 : 3
+export const DICT_VERSION = 3
 export const KEY_BUNDLE_TYPE = Buffer.from([5])
-
-// WA\x06\x03 = web protocol, WAM\x05 = native Android protocol
-export const NOISE_WA_HEADER = PROTOCOL_MODE === 'native'
-	? Buffer.from([87, 65, 77, DICT_VERSION]) // WAM\x05
-	: Buffer.from([87, 65, 6, DICT_VERSION])  // WA\x06\x03
-
-export { PROTOCOL_MODE }
+export const NOISE_WA_HEADER = Buffer.from([87, 65, 6, DICT_VERSION]) // last is "DICT_VERSION"
 /** from: https://stackoverflow.com/questions/3809401/what-is-a-good-regular-expression-to-match-a-url */
 export const URL_REGEX = /https:\/\/(?![^:@\/\s]+:[^:@\/\s]+@)[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}(:\d+)?(\/[^\s]*)?/g
 

src/Socket/messages-recv.ts

@@ -2243,59 +2243,23 @@ export const makeMessagesRecvSocket = (config: SocketConfig) => {
 	const handleMessage = async (node: BinaryNode) => {
 		if (shouldIgnoreJid(node.attrs.from!) && node.attrs.from !== S_WHATSAPP_NET) {
 			logger.trace({ from: node.attrs.from }, 'ignored message')
+			// Send a clean ACK (no error code) so the server considers the
+			// message delivered. Using error 500 (UnhandledError) previously
+			// caused the server to retry delivery, generating duplicate traffic.
 			await sendMessageAck(node)
 			return
 		}
 
 		const encNode = getBinaryNodeChild(node, 'enc')
-		const unavailableNode = getBinaryNodeChild(node, 'unavailable')
-
 		// msmsg block removed — allow msmsg decryption (required for view-once on linked devices)
+
+		// Handle view-once unavailable sync from primary device.
+		// When the primary device sends a view-once, linked companions receive
+		// <unavailable type="view_once"/> — no enc content, just a sync signal.
+		// Acknowledge and skip decryption (nothing to decrypt).
+		const unavailableNode = getBinaryNodeChild(node, 'unavailable')
 		if (unavailableNode?.attrs?.type === 'view_once') {
-			const { fullMessage: voMsg } = decryptMessageNode(
-				node,
-				authState.creds.me!.id,
-				authState.creds.me!.lid || '',
-				signalRepository,
-				logger,
-			)
-			voMsg.key.isViewOnce = true
-
-			// Try to request the actual view-once content from the primary phone via PDO
-			// The phone may resend the full media (url, mediaKey, directPath, etc.)
-			console.log(`[VO_PDO] Requesting view-once content via PDO for ${voMsg.key.id} from ${voMsg.key.remoteJid}`)
-			try {
-				const requestId = await requestPlaceholderResend(voMsg.key, {
-					key: { ...voMsg.key },
-					pushName: voMsg.pushName,
-					messageTimestamp: voMsg.messageTimestamp,
-					participant: voMsg.key.participant,
-					participantAlt: voMsg.key.participantAlt
-				})
-				if (requestId && requestId !== 'RESOLVED') {
-					console.log(`[VO_PDO] PDO request sent! requestId=${requestId} — waiting for phone to resend`)
-				} else if (requestId === 'RESOLVED') {
-					console.log(`[VO_PDO] Message arrived during PDO delay!`)
-				} else {
-					console.log(`[VO_PDO] Already requested or no response`)
-				}
-			} catch (err: any) {
-				console.log(`[VO_PDO] PDO request failed: ${err.message} — falling back to placeholder`)
-			}
-
-			// Emit placeholder immediately so consumers see the notification
-			// If PDO succeeds, the real message will arrive via messages.upsert later
-			voMsg.message = {
-				viewOnceMessage: {
-					message: {
-						imageMessage: {
-							viewOnce: true,
-						}
-					}
-				}
-			}
-			const upsertType = node.attrs.offline ? 'append' : 'notify'
-			await upsertMessage(voMsg, upsertType)
+			logger.debug({ id: node.attrs.id, from: node.attrs.from }, 'received view_once unavailable sync from primary device')
 			await sendMessageAck(node)
 			return
 		}
@@ -2413,20 +2377,12 @@ export const makeMessagesRecvSocket = (config: SocketConfig) => {
 								{ msgId: msg.key?.id, messageType },
 								'CTWA: Skipping placeholder resend for unavailable fanout type'
 							)
-							// For view-once: emit the message with a viewOnceMessage placeholder
-							// so consumers (zpro, etc.) can detect and display it.
-							// Include a message wrapper so isValidMsg accepts it.
+							// For view-once: emit the message as a stub so consumers know it arrived.
+							// Use 'notify' for live messages so realtime consumers get the event.
 							if (messageType === 'view_once_unavailable_fanout') {
 								msg.key.isViewOnce = true
-								msg.message = {
-									viewOnceMessage: {
-										message: {
-											imageMessage: {
-												viewOnce: true,
-											}
-										}
-									}
-								}
+								msg.messageStubType = proto.WebMessageInfo.StubType.CIPHERTEXT
+								msg.messageStubParameters = ['view_once_unavailable']
 								const upsertType = node.attrs.offline ? 'append' : 'notify'
 								await upsertMessage(msg, upsertType)
 							}

src/Utils/validate-connection.ts

@@ -3,7 +3,6 @@ import { createHash } from 'crypto'
 import { proto } from '../../WAProto/index.js'
 import {
 	KEY_BUNDLE_TYPE,
-	PROTOCOL_MODE,
 	WA_ADV_ACCOUNT_SIG_PREFIX,
 	WA_ADV_DEVICE_SIG_PREFIX,
 	WA_ADV_HOSTED_ACCOUNT_SIG_PREFIX
@@ -59,10 +58,7 @@ const getClientPayload = (config: SocketConfig) => {
 		userAgent: getUserAgent(config)
 	}
 
-	// Native protocol (WAM\x05) does not use WebInfo — only web protocol does
-	if (PROTOCOL_MODE !== 'native') {
-		payload.webInfo = getWebInfo(config)
-	}
+	payload.webInfo = getWebInfo(config)
 
 	return payload
 }