purple-facebook
purple-facebook copied to clipboard
No matches for $.viewer.message_threads.sync_sequence_id
Yesterday everything worked fine (2015-12-14). Today the problem (2015-12-15).
No matches for $ .view.message_threads.sync_sequence_id
$ pidgin -v
Pidgin 2.10.11 (libpurple 2.10.11)
$ lsb_release
No LSB modules are available.
shcoder@x:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.10
Release: 15.10
Codename: wily
$ uname -a
Linux x 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11 11:39:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Installed as described herein https://github.com/jgeboski/purple-facebook/wiki/Building-on-*NIX#from-the-git-repository . Problem still exists.
Now it works. Apparently this is a bug Facebook.
Is it working now?
I've noticed this too, using Spectrum transport on Debian. It went away on its own and chat is working.
@jgeboski Since yesterday the error was not.
Any status updates on this issue?
I think we can assume it was just a temporary server side issue
Yup. Without this value, the plugin will not work at all. If this issue issue still exists, please reopen.
I have been getting this error all day today...
No matches for $.viewer.message_threads.sync_sequence_id
I can't reopen, since it isn't my bug, so I hope that this comment reaches you.
Same problem here, today pidgin returns "No matches for $.viewer.message_threads.sync_sequence_id"
ver: Ubuntu 15.10, Pidgin 2.10.11 (libpurple 2.10.11)
@doctorcolossus @ge0rgecz: does it ever resolve itself, or does it fail indefinitely? I am thinking we might need to update the query hashes, as the old ones are from six or seven months ago.
It stayed broken most of yesterday, but now it's connecting properly again for me.
If someone could send me a debugging log of this happening, that would be great. This is likely going to require that the plugin switch to an updated revision of the Facebook Messenger protocol.
Unfortunately I'm no longer able to reproduce the problem for the time being, but if/when it recurs, then sure - I will try to capture a debug log.
"No matches for $.viewer.message_threads.sync_sequence_id" error disapeared next day. Its ok now.
It's happening again on my end but judging frm the rest of this thread I hope that it disappears by tonight.
Yeah it fixed itself
It happend to me this morning at 9am and it's still giving me the error while trying to connect from bitlbee. Everything worked fine till today, when I got disconnected and now I can't connect no more.
I can confirm that I currently have this issue with bitlbee as well. I'm hoping this will clear up, as the plugin works perfectly otherwise.
And now it works again. It reconnected by itself. Hopefully this doesn't happen all to often. I love Bitlbee for chatting.
Happened to me today for the first time, disappeared as soon as I logged on facebook website. I did not connect on Facebook website prior to that, but I used Franz.
Looks to be a problem with either Pidgin or the Plugin. Once I got the error, reconnecting always returned this error. Restarting Pidgin, allowed me to log.
If anyone happens to be reading this while experiencing this issue: please test the android messenger app as soon as possible, and report if it works.
I'm almost completely certain this is just a server-side issue that fixes itself after a few minutes most of the time. I don't think I can do much other than improving the error message to be clearer.
I'm experiencing this right now. No matches for $.viewer.message_threads.sync_sequence_id Unfortunately I do not use the android app so I can't test it.
I'm experiencing this right now, and the android messenger app works fine @dequis
Update: just a few minutes later, I could connect again with purple-facebook
I've been seeing this for a day now.
@sinzim Go to #306