whalibmob 5.24.1 → 5.24.2

package/README.md

@@ -2884,7 +2884,7 @@ client.on('version_update', ({ from, to, source }) => {
   console.log('announcing', to, 'instead of', from, '—', source)
 })
 
-await client.init('40756469325')
+await client.init('919634847671')
 ```
 
 **Reconnects are covered too.** The check runs from the socket-connect step
@@ -2923,8 +2923,8 @@ Set `{ refreshVersion: false }` on the client to turn it off.
 The manual tool still works on both platforms:
 
 ```bash
-wa refresh-version 40756469325                    # current build for the platform
-wa refresh-version 40756469325 --version 2.25.1.2 # or one you name
+wa refresh-version 919634847671                    # current build for the platform
+wa refresh-version 919634847671 --version 2.25.1.2 # or one you name
 ```
 
 Companion sessions have never had this problem: `connectWeb()` reads the live

package/cli.js

@@ -1385,7 +1385,7 @@ async function handleLine(line) {
         if (!ph) {
           fail('usage: /pair <phone> [8-char-code]');
           out('  the phone number is the account you want to link to, digits only');
-          out('  example: /pair 40756469325');
+          out('  example: /pair 919634847671');
           break;
         }
         if (_client && _client.connected) { fail('already connected — /disconnect first'); break; }
@@ -1402,7 +1402,7 @@ async function handleLine(line) {
           out('  links the number as a companion by QR instead of a pairing code');
           out('  a QR is drawn in the terminal — scan it from the phone that owns');
           out('  the number:  WhatsApp → Linked Devices → Link a device');
-          out('  example: /qrcode 40756469325');
+          out('  example: /qrcode 919634847671');
           break;
         }
         if (_client && _client.connected) { fail('already connected — /disconnect first'); break; }

package/lib/BinaryNode.js

@@ -49,7 +49,7 @@ const _JID_SERVERS = new Set([
   's.whatsapp.net', 'g.us', 'lid', 'broadcast', 'call', 'newsletter', 'c.us', 's.us'
 ]);
 
-// "120363427770886227@g.us" / "40756469325:2@s.whatsapp.net" → JID object.
+// "120363427770886227@g.us" / "919634847671:2@s.whatsapp.net" → JID object.
 // Returns null for anything that is not a full JID, so plain strings (and
 // bare server tokens like "g.us", which the dictionary already encodes as a
 // valid address) keep their existing encoding untouched.

package/lib/SessionPaths.js

@@ -6,17 +6,17 @@
 // the app state, the device cache, the LID maps, the history — used to sit
 // side by side in one directory, named after the number:
 //
-//   ~/.waSession/40756469325.json
-//   ~/.waSession/40756469325.signal.json
-//   ~/.waSession/40756469325.sk.json
+//   ~/.waSession/919634847671.json
+//   ~/.waSession/919634847671.signal.json
+//   ~/.waSession/919634847671.sk.json
 //   ...  × 11 files × every number
 //
 // Fifty numbers made that five hundred files in one place, with no way to move,
 // back up or delete one account without picking its files out of the pile by
 // prefix. A number now gets a directory of its own:
 //
-//   <base>/40756469325/40756469325.json
-//   <base>/40756469325/40756469325.signal.json
+//   <base>/919634847671/919634847671.json
+//   <base>/919634847671/919634847671.signal.json
 //   ...
 //
 // The file names inside are unchanged, so every path built as

package/lib/messages/MessageSender.js

@@ -853,7 +853,7 @@ class MessageSender {
   // ─── Clear all Signal sessions for a phone-number recipient ─────────────────
   //
   // Called on error 479 (stale session).  Deletes:
-  //   • All Signal sessions keyed by phone-number device JIDs (e.g. 40756469325:0)
+  //   • All Signal sessions keyed by phone-number device JIDs (e.g. 919634847671:0)
   //   • The corresponding LID device session if a LID mapping is known
   //
   // Then flushes the device-ID cache for that phone so the next send re-runs

package/lib/signal/SignalStore.js

@@ -43,9 +43,9 @@ const DEBOUNCE_MS = 300;
 // One-time pre-keys do not live in the snapshot above. They get a file each,
 // named one per id:
 //
-//   <base>/40756469325/40756469325.pre-key-1.json
+//   <base>/919634847671/919634847671.pre-key-1.json
 //   ...
-//   <base>/40756469325/40756469325.pre-key-812.json
+//   <base>/919634847671/919634847671.pre-key-812.json
 //
 // Everything else about a pre-key is small, but there are 812 of them
 // and every one that is consumed rewrites the whole store — so keeping them in
@@ -55,8 +55,8 @@ const DEBOUNCE_MS = 300;
 // authentication folders expects to see, and a write now touches one key.
 //
 // The stem in front of `.pre-key-` is the one the .signal.json file already
-// carries, so a number's mobile half (40756469325.pre-key-N.json) and its
-// companion half (40756469325.web.pre-key-N.json) keep separate pools, as they
+// carries, so a number's mobile half (919634847671.pre-key-N.json) and its
+// companion half (919634847671.web.pre-key-N.json) keep separate pools, as they
 // must — and a session still sitting in the old flat layout, where every
 // number shares one directory, does not collide with its neighbours either.
 //
@@ -224,8 +224,8 @@ class SignalStore {
   attachFile(filePath) {
     this._filePath = filePath;
     // The pre-key files sit beside the snapshot and share its stem, so
-    // 40756469325.signal.json gives 40756469325.pre-key-<id>.json and
-    // 40756469325.web.signal.json gives 40756469325.web.pre-key-<id>.json.
+    // 919634847671.signal.json gives 919634847671.pre-key-<id>.json and
+    // 919634847671.web.signal.json gives 919634847671.web.pre-key-<id>.json.
     const base = path.basename(filePath);
     this._pkDir    = path.dirname(filePath);
     this._pkPrefix = base.endsWith('.signal.json')

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "whalibmob",
-  "version": "5.24.1",
+  "version": "5.24.2",
   "description": "Node.js library for WhatsApp — register a number over SMS, or link as a companion by QR. Signal E2E encryption, media, groups, channels.",
   "author": "Kunboruto20",
   "main": "index.js",