@eryxenx/insta-chat 2.0.6 → 2.0.7

package/CHANGELOG.md

@@ -4,6 +4,20 @@ All notable changes to `@eryxenx/insta-chat` are documented here.
 The format follows [Keep a Changelog](https://keepachangelog.com/) and uses
 [Semantic Versioning](https://semver.org/).
 
+## [2.0.7] - 2026-10-11
+
+### Fixed
+
+- **`unsendMessage` silently failed for a message the bot did not send in this
+  process.** The thread of the id being unsent was resolved only from the
+  in-memory `messageID -> threadID` map, so unsending a message sent before a
+  restart (or a reply to someone else's message) threw `Unknown thread for
+  message` internally and returned `false` — `/unsend` appeared to do nothing.
+  `unsendMessage(messageID, callback?, threadID?)` now accepts the thread
+  explicitly, and the normalizer remembers the replied-to message id (whose
+  thread is known) so the map lookup succeeds. The thread the message was seen
+  in is always a safe explicit value for `/unsend`.
+
 ## [2.0.6] - 2026-10-10
 
 ### Added

package/DOCS.md

@@ -58,7 +58,7 @@ Facebook-Chat-API shape. Its methods live one-per-file under
 
 | Group | Methods |
 |-------|---------|
-| messaging | `sendMessage(form, threadID, cb?, replyToMessage?)`, `sendMessageSync`, `editMessage(text, messageID)`, `unsendMessage(messageID)`, `setMessageReaction(emoji, messageID, cb?, threadID?)`, `sendTypingIndicator`, `markAsRead`, `shareContact`, `resolvePhotoUrl` |
+| messaging | `sendMessage(form, threadID, cb?, replyToMessage?)`, `sendMessageSync`, `editMessage(text, messageID)`, `unsendMessage(messageID, cb?, threadID?)`, `setMessageReaction(emoji, messageID, cb?, threadID?)`, `sendTypingIndicator`, `markAsRead`, `shareContact`, `resolvePhotoUrl` |
 | threads | `getThreadInfo`, `getThreadList`, `getThreadHistory` |
 | users | `getUserInfo`, `getUID`, `getProfilePictureUrl` |
 | account | `getCurrentUserID`, `getAppState`, `getCookies`, `setOptions` |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eryxenx/insta-chat",
-  "version": "2.0.6",
+  "version": "2.0.7",
   "description": " Unofficial Instagram Chat API for Node.js | Build Instagram DM bots on personal accounts \u2014 send messages, media, voice notes, reactions, edit & unsend, listen for incoming chats. No browser at runtime",
   "main": "index.js",
   "types": "index.d.ts",
@@ -23,7 +23,7 @@
     "CHANGELOG.md"
   ],
   "scripts": {
-    "test": "node test/smoke.js && node test/antiSuspension.test.js && node test/replyContent.test.js && node test/edit.test.js && node test/sendReply.test.js && node test/client.test.js && node test/relayError.test.js && node test/safetyWiring.test.js && node test/mediaOrder.test.js && node test/sessionSafety.test.js && node test/emptySend.test.js && node test/pollFloor.test.js",
+    "test": "node test/smoke.js && node test/antiSuspension.test.js && node test/replyContent.test.js && node test/edit.test.js && node test/sendReply.test.js && node test/client.test.js && node test/relayError.test.js && node test/safetyWiring.test.js && node test/mediaOrder.test.js && node test/sessionSafety.test.js && node test/emptySend.test.js && node test/pollFloor.test.js && node test/unsend.test.js",
     "build": "node scripts/build.js"
   },
   "keywords": [

package/src/api/messaging/unsendMessage.js

@@ -5,12 +5,16 @@
  * Original author credit must be retained in all copies and derivatives.
  */
 
-// fca.unsendMessage(messageID) — the thread is resolved from the id.
+// fca.unsendMessage(messageID, callback, threadID) — the thread may be passed
+// explicitly; otherwise it is resolved from the id. A bot that only knows the
+// replied-to message id (it did not send that message in this process, e.g.
+// after a restart) cannot resolve the thread, so the explicit thread is what
+// makes /unsend work reliably.
 module.exports = function (client) {
-  return async function unsendMessage(messageID, callback) {
+  return async function unsendMessage(messageID, callback, threadID) {
     const cb = typeof callback === "function" ? callback : null;
     try {
-      const tid = client._resolveThread(messageID);
+      const tid = client._resolveThread(messageID, threadID);
       const ok = await client.api.unsendMessage(tid, String(messageID));
       if (cb) cb(null, ok);
       return ok;

package/src/app/InstaContext.js

@@ -29,7 +29,7 @@ class InstaContext {
   }
 
   unsend(messageID, callback) {
-    return this.client.unsendMessage(messageID, callback);
+    return this.client.unsendMessage(messageID, callback, this.threadID);
   }
 
   edit(text, messageID, callback) {

package/src/events/normalizeEvent.js

@@ -139,6 +139,12 @@ class EventNormalizer {
     // client must know which thread it belongs to.
     if (typeof this.client.rememberThread === "function") {
       this.client.rememberThread(event.messageID, threadID);
+      // Remember the replied-to message too: /unsend resolves its thread from
+      // that id, and the bot may be unssending a message it sent in an earlier
+      // process (so it is not in _msgThread otherwise).
+      if (event.messageReply && event.messageReply.messageID) {
+        this.client.rememberThread(event.messageReply.messageID, threadID);
+      }
     }
 
     return event;