@violetix/baileys 0.5.2 → 0.5.3

package/lib/Socket/socket.js

@@ -384,6 +384,15 @@ export const makeSocket = (config) => {
     };
     const ev = makeEventBuffer(logger);
     const { creds } = authState;
+    /**
+     * Last identity this socket has been logged in as. `sock.user` is a getter over
+     * `authState.creds.me`, and hosts read it as `sock.user.id` with no optional chaining (the
+     * @neoxr/wb engine does exactly that in serialize() and in its JID() helper). One stanza that
+     * arrives while `creds.me` is momentarily absent therefore throws inside the host's event
+     * listener instead of being processed. Keeping the identity we already know turns that into a
+     * correct answer: a socket that is receiving stanzas is logged in as this user.
+     */
+    let lastMe = creds.me;
     // add transaction capability
     const keys = addTransactionCapability(authState.keys, logger, transactionOpts);
     const signalRepository = makeSignalRepository({ creds, keys }, logger, pnFromLIDUSync);
@@ -1317,6 +1326,9 @@ export const makeSocket = (config) => {
             });
         }
         Object.assign(creds, update);
+        if (creds.me) {
+            lastMe = creds.me;
+        }
     });
     const updateServerTimeOffset = ({ attrs }) => {
         const tValue = attrs?.t;
@@ -1396,7 +1408,7 @@ export const makeSocket = (config) => {
         authState: { creds, keys },
         signalRepository,
         get user() {
-            return authState.creds.me;
+            return authState.creds.me ?? lastMe;
         },
         /**
          * True while the transport is repairing itself. A host that reads this does not build a

package/package.json

@@ -1,6 +1,6 @@
 {
    "name": "@violetix/baileys",
-   "version": "0.5.2",
+   "version": "0.5.3",
    "description": "Enhanced Baileys v7 with fixes for newsletter media uploads, plus support for interactive messages, albums, and additional message types.",
    "main": "lib/index.js",
    "types": "lib/index.d.ts",