Chats not refreshing automatically

[blandre]

Whenever I receive a new message, it doesn't automatically show, unless I manually refresh. The same happens when I send new messages, the '>' indicator doesn't show after I send the first time. Again, refreshing manually seems to work.

[Horites]

Im having the same exact problem

[j6k4m8]

I am running into the same issue. Some important diagnostics:

• messages still do send upon hitting enter
• new messages do not render in the thread

(Hope @Horites and @blandre will let me know if their experiences differ from this)

[wgehalo]

Same issue here.

Also might be worth noting Messer, a similar project, is having a similar issue. I suspect facebook updated their API which is causing this issue.

[Horites]

Hello @j6k4m8
Yes, it seems like Im having the exact same problem as you are.
I do belive @wgehalo would be correct on the API issue.

[Toz3wm]

Same problem here.
Anyone aware of a similar project that fixed this problem ?

[michondr]

joining you guys. discovered cli clients yeasterday and still didn't manage to make usable this one nor messer 😄.

also, this happens

> /search adama
/usr/lib/node_modules/fb-messenger-cli/lib/search.js:49
            return friend.name.toLowerCase().indexOf(searchString.toLowerCase()) !== -1;
                               ^

TypeError: Cannot read property 'toLowerCase' of undefined
    at /usr/lib/node_modules/fb-messenger-cli/lib/search.js:49:32
    at Array.filter (<anonymous>)
    at Search.filterFriends (/usr/lib/node_modules/fb-messenger-cli/lib/search.js:48:38)
    at /usr/lib/node_modules/fb-messenger-cli/lib/search.js:42:18

[j6k4m8]

@michondr your second bug looks like it's solved here:
#193

• Delete the .kryptonite file
• Make sure you're on the latest node versions

[B-greg]

I'm having the same problem. Did they have any progress on this issue?

[gcantieni]

yeah i've just taken to typing /r after every series of messages, not quite ideal but...beats opening the browser?

[j6k4m8]

Can you verify that adding a /r to typed messages remedies this issue? Can others verify it works for them?

…

On Mon, Jan 13, 2020 at 11:19 AM Gus Cantieni ***@***.***> wrote: yeah i've just taken to typting /r after every series of messages, not quite ideal but...beats opening the browser? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#220?email_source=notifications&email_token=AAFJKB6DK2FGIHIVAXEHEW3Q5SIB5A5CNFSM4JQDZXCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIZKQFY#issuecomment-573745175>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFJKB3DANLENSYE4W6BG4LQ5SIB5ANCNFSM4JQDZXCA> .

[blandre]

I tried reinstalling and messed something up, so I'm currently relying on a docker version that is not even loading conversation lists
However, I remember being able to use /r to refresh conversations and it worked..

Just tested it, and typing a /r after sending a message remedies the issue. However, it does not seem to refresh the messages after receiving a response.

[gregoryfenton]

Typing in the message, pressing Enter
then typing /r
works for me but typing /r constantly to check is a bit of a pain

[j6k4m8]

To help start to centralize this:

It looks like this code is responsible for handling the explicit refresh command with /refresh or /r:

fb-messenger-cli/lib/interactive.js

Lines 431 to 437 in 309d605

	case '/refresh':
	if (action === 1) {
	interactive.initializeConversationViewFromFbid(this.currentConversationId);
	} else {
	interactive.handleCommands("/back");
	}
	break;

Might need some other eyes on this, but I believe this code is where the new incoming message triggers a thread refresh:

fb-messenger-cli/lib/interactive.js

Lines 264 to 267 in 309d605

	emitter.emit(listener, current_userId, (data) => {
	action = data.action;
	currentThreadCount = data.threadCount;
	rlInterface.prompt(true);

Actual refresh here:

fb-messenger-cli/lib/interactive.js

Line 285 in 309d605

interactive.printThread();

I can spend more time on this during the weekend, but hopefully this helps us start narrowing down where the bug lives.