whalibmob 5.5.41 → 5.5.42

package/lib/DeviceManager.js

@@ -423,44 +423,48 @@ class DeviceManager {
   //
   //  APK-confirmed format (extracted from WhatsApp DEX string tables):
   //
+  //  Correct wire format (verified against live WA server):
+  //
   //  <iq to="s.whatsapp.net" type="get" xmlns="usync">
-  //    <usync sid="..." mode="query" last="true" index="0" context="message">
+  //    <usync sid="..." mode="query" last="true" index="0" context="interactive">
   //      <query>
-  //        <devices version="2" device_orientation="0" fetch_options="5"/>
+  //        <devices version="2"/>
   //        <lid/>
+  //        <contact/>
   //      </query>
   //      <list>
-  //        <user><contact>+phone</contact></user>  ← Buffer, not jid attr string
+  //        <user><contact>+phone</contact></user>  ← Buffer, NOT jid attr
   //      </list>
   //      <side_list/>
   //    </usync>
   //  </iq>
   //
-  //  Critical fixes vs original whalibmob implementation:
+  //  Key findings vs original buggy whalibmob implementation:
+  //
+  //  Fix A — User list format was wrong (jid attr → server ignored IQ):
+  //    Correct: <user><contact>+phone</contact></user>  (Buffer content, same as _doContactUsync)
+  //    Wrong:   <user jid="phone@s.whatsapp.net"/>      (jid attr — server silently drops IQ)
   //
-  //  Fix A — fetch_options="5" MISSING from <devices> node:
-  //    Without fetch_options="5", the WA server returns ONLY device 0 (primary phone).
-  //    fetch_options="5" instructs the server to return ALL linked devices.
-  //    device_orientation="0" is also required by the server.
+  //  Fix B — Extra <devices> attributes break the IQ:
+  //    device_orientation="0" and fetch_options="5" both cause the server to ignore the IQ.
+  //    fetch_options is not in the binary token dict → encoded as BINARY_8 → server parse error.
+  //    Use only version="2" on <devices>. Server returns ALL linked devices without extra attrs.
   //
-  //  Fix B — User list format: use <contact>+phone</contact> as Buffer content.
+  //  Fix C — context and side_list must match _doContactUsync (the working format):
+  //    context="interactive" + <side_list/> is REQUIRED. context="message" → server ignores IQ.
   async _doUsyncIq(phones) {
     const iqId = this._client._genMsgId();
     const sid  = this._client._genMsgId();
 
-    // User list: <user><contact>+phone</contact></user>
-    // This is the ONLY format the server responds to for phone-based usync.
-    // The <user jid="..."/> attribute format is silently ignored by the server.
+    // User list: identical to contact usync format that the server responds to.
     const listChildren = phones.map(p =>
       new BinaryNode('user', {}, [
         new BinaryNode('contact', {}, Buffer.from('+' + p, 'utf8'))
       ])
     );
 
-    // context="interactive" is REQUIRED.
-    // The server ignores context="message" usync IQs entirely (never replies).
-    // Query includes <devices>, <lid>, AND <contact> so the server returns
-    // the full device list + LID mapping + contact presence in one round-trip.
+    // Same structure as _doContactUsync (which works) but with <devices> and <lid>
+    // added to the query. context="interactive" + side_list matches the working format.
     const iqNode = new BinaryNode('iq',
       { id: iqId, to: 's.whatsapp.net', type: 'get', xmlns: 'usync' },
       [new BinaryNode('usync',
@@ -824,8 +828,6 @@ class DeviceManager {
         [
           new BinaryNode('query', {},
             [
-              // context="interactive" is REQUIRED — server silently ignores
-              // "message" context usync IQs (same as _doUsyncIq).
               new BinaryNode('devices', { version: '2' }, null),
               new BinaryNode('lid', {}, null)
             ]

package/package.json

@@ -1,7 +1,7 @@
 
 {
   "name": "whalibmob",
-  "version": "5.5.41",
+  "version": "5.5.42",
   "description": "WhatsApp library for interaction with WhatsApp Mobile API no web",
   "author": "Kunboruto50",
   "main": "index.js",