Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No matches for $.viewer.message_threads.sync_sequence_id #179

Open
web36m opened this issue Dec 15, 2015 · 27 comments
Open

No matches for $.viewer.message_threads.sync_sequence_id #179

web36m opened this issue Dec 15, 2015 · 27 comments

Comments

@web36m
Copy link

web36m commented Dec 15, 2015

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
@web36m
Copy link
Author

web36m commented Dec 15, 2015

@web36m
Copy link
Author

web36m commented Dec 15, 2015

Now it works. Apparently this is a bug Facebook.

@jgeboski
Copy link
Collaborator

Is it working now?

@jkufner
Copy link

jkufner commented Dec 16, 2015

I've noticed this too, using Spectrum transport on Debian. It went away on its own and chat is working.

@web36m
Copy link
Author

web36m commented Dec 16, 2015

@jgeboski Since yesterday the error was not.

@jgeboski
Copy link
Collaborator

Any status updates on this issue?

@dequis
Copy link
Owner

dequis commented Dec 27, 2015

I think we can assume it was just a temporary server side issue

@jgeboski
Copy link
Collaborator

Yup. Without this value, the plugin will not work at all. If this issue issue still exists, please reopen.

@doctorcolossus
Copy link

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.

@ge0rgecz
Copy link

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)

@jgeboski jgeboski reopened this Jan 21, 2016
@jgeboski
Copy link
Collaborator

@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.

@jgeboski jgeboski removed the resolved label Jan 21, 2016
@doctorcolossus
Copy link

It stayed broken most of yesterday, but now it's connecting properly again for me.

@jgeboski
Copy link
Collaborator

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.

@doctorcolossus
Copy link

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.

@ge0rgecz
Copy link

ge0rgecz commented Feb 5, 2016

"No matches for $.viewer.message_threads.sync_sequence_id" error disapeared next day. Its ok now.

@ghost
Copy link

ghost commented Mar 15, 2016

It's happening again on my end but judging frm the rest of this thread I hope that it disappears by tonight.

@ghost
Copy link

ghost commented Mar 16, 2016

Yeah it fixed itself

@xpliz
Copy link

xpliz commented Apr 1, 2016

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.

@ghost
Copy link

ghost commented Apr 1, 2016

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.

@xpliz
Copy link

xpliz commented Apr 1, 2016

And now it works again. It reconnected by itself. Hopefully this doesn't happen all to often. I love Bitlbee for chatting.

@monsieurmax
Copy link

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.

@dl748
Copy link

dl748 commented Jul 18, 2016

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.

@dequis dequis removed the bug label Jul 19, 2016
@dequis
Copy link
Owner

dequis commented Jul 19, 2016

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.

@vdmkenny
Copy link

vdmkenny commented Aug 8, 2016

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.

@7hibault
Copy link

7hibault commented Sep 21, 2016

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

@harahauk
Copy link

I've been seeing this for a day now.

@dequis
Copy link
Owner

dequis commented Mar 30, 2017

@sinzim Go to #306

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests