Messer: History command is broken

Whenever I try to access the “history” feature, I got this error… Have I done something wrong? I haven’t see anyone complaining about that yet

also… The error got one exception: when I use it on a specific contact, it displays the history as it should, but if I try to specify the number of messages it gives me back the same error I mentioned at the beginning (and which I’ll post it fully bellow).

(node:1560) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'thread_key' of null
    at formatThreadGraphQLResponse (/usr/local/lib/node_modules/messer/node_modules/facebook-chat-api/src/getThreadInfo.js:35:32)
    at /usr/local/lib/node_modules/messer/node_modules/facebook-chat-api/src/getThreadInfo.js:163:24
    at bound (domain.js:301:14)
    at runBound (domain.js:314:12)
    at tryCatcher (/usr/local/lib/node_modules/messer/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/messer/node_modules/bluebird/js/main/promise.js:510:31)
    at Promise._settlePromiseAt (/usr/local/lib/node_modules/messer/node_modules/bluebird/js/main/promise.js:584:18)
    at Promise._settlePromises (/usr/local/lib/node_modules/messer/node_modules/bluebird/js/main/promise.js:700:14)
    at Async._drainQueue (/usr/local/lib/node_modules/messer/node_modules/bluebird/js/main/async.js:123:16)
    at Async._drainQueues (/usr/local/lib/node_modules/messer/node_modules/bluebird/js/main/async.js:133:10)
    at Immediate.Async.drainQueues (/usr/local/lib/node_modules/messer/node_modules/bluebird/js/main/async.js:15:14)
    at runCallback (timers.js:794:20)
    at tryOnImmediate (timers.js:752:5)
    at processImmediate [as _immediateCallback] (timers.js:729:5)
(node:1560) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 8)

I’m running it at my Lubuntu 18.04 LTS…

update: I realized it only displays the history to the very first person at “recents”

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 2
  • Comments: 28

Most upvoted comments

recent returns nothing history returns the usual

(node:16259) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'thread_key' of null
    at formatThreadGraphQLResponse (/home/eupiteco/.nvm/versions/node/v10.12.0/lib/node_modules/messer/node_modules/facebook-chat-api/src/getThreadInfo.js:35:32)
    at /home/eupiteco/.nvm/versions/node/v10.12.0/lib/node_modules/messer/node_modules/facebook-chat-api/src/getThreadInfo.js:163:24
    at bound (domain.js:396:14)
    at runBound (domain.js:409:12)
    at tryCatcher (/home/eupiteco/.nvm/versions/node/v10.12.0/lib/node_modules/messer/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (/home/eupiteco/.nvm/versions/node/v10.12.0/lib/node_modules/messer/node_modules/bluebird/js/main/promise.js:510:31)
    at Promise._settlePromiseAt (/home/eupiteco/.nvm/versions/node/v10.12.0/lib/node_modules/messer/node_modules/bluebird/js/main/promise.js:584:18)
    at Promise._settlePromises (/home/eupiteco/.nvm/versions/node/v10.12.0/lib/node_modules/messer/node_modules/bluebird/js/main/promise.js:700:14)
    at Async._drainQueue (/home/eupiteco/.nvm/versions/node/v10.12.0/lib/node_modules/messer/node_modules/bluebird/js/main/async.js:123:16)
    at Async._drainQueues (/home/eupiteco/.nvm/versions/node/v10.12.0/lib/node_modules/messer/node_modules/bluebird/js/main/async.js:133:10)
    at Immediate.Async.drainQueues [as _onImmediate] (/home/eupiteco/.nvm/versions/node/v10.12.0/lib/node_modules/messer/node_modules/bluebird/js/main/async.js:15:14)
    at runCallback (timers.js:705:18)
    at tryOnImmediate (timers.js:676:5)
    at processImmediate (timers.js:658:5)
    at process.topLevelDomainCallback (domain.js:121:23)
(node:16259) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:16259) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:16259) [DEP0097] DeprecationWarning: Using a domain property in MakeCallback is deprecated. Use the async_context variant of MakeCallback or the AsyncResource class instead.

Yes, “with quotes”

Hi, I am now running messer in Xubuntu 18.04 and cannot run messer as user, only as root… the output is this, I don’t remember needing those permissions with 0.3.4

permission denied, mkdir '/usr/local/lib/node_modules/messer/src/tmp'

But that does not belong in this thread 😅

When running history “User Name” I still get the same error and the prompt hangs. Pressing the enter key results in the following output

TypeError: Cannot read property 'then' of null
   at REPLServer.eval (/usr/local/lib/node_modules/messer/src/messer.js:141:11)
   at bound (domain.js:301:14)
   at REPLServer.runBound [as eval] (domain.js:314:12)
   at REPLServer.onLine (repl.js:468:10)
   at emitOne (events.js:116:13)
   at REPLServer.emit (events.js:211:7)
   at REPLServer.Interface._onLine (readline.js:282:10)
   at REPLServer.Interface._line (readline.js:631:8)
   at REPLServer.Interface._ttyWrite (readline.js:911:14)
   at REPLServer.self._ttyWrite (repl.js:537:7)
   at ReadStream.onkeypress (readline.js:160:10)
   at emitTwo (events.js:126:13)
   at ReadStream.emit (events.js:214:7)
   at emitKeys (internal/readline.js:420:14)
   at emitKeys.next (<anonymous>)
   at ReadStream.onData (readline.js:1011:36)

and the > prompt is back.

Edit: Answering to your questions

what position in your thread list is the person (i.e are they most recent, second most etc.)

Get the same error whatever is the position

how many messages are in that thread

A lot…

version of Messer (just to double check)

0.4.0

What situation (if any) does history work for?

None

☝️ Same issue, can’t return any messages, like Jukiro above. Just installed version 0.3.4 via npm in a Manjaro system Subscribing for fixes. Also great app! I’ve been wating for this a long time 😄