-
Notifications
You must be signed in to change notification settings - Fork 88
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
Null value for $.viewer.message_threads.sync_sequence_id #306
Comments
I'm getting this error as well Windows 8.1 |
All morning. Even upgraded Pidgin and re-installed the two .dll files. |
Just happened to me as well when I logged in to my pc this evening. Wonder what facebook changed this time... |
I'm getting same error. A few logs below: (10:33:57) http: releasing a socket: 0E67C758 (10:33:57) connection: Connection error on 0E49FD90 (reason: 0 description: Null value for $.viewer.message_threads.sync_sequence_id) |
This isn't a random glitch, it looks like facebook has decided to stop supporting old versions of the messenger app. I guess purple-facebook was based on the old protocol. Seems like we're out of luck until things are ported over. |
The weird thing is my messenger is still working just fine. I am kinda wondering one thing. Does any of you use mobile device and did it get an update? Just trying to figure this out might not be fun maybe. |
Same here, and I don't use the mobile app. I updated Pidgin and still see the same error. |
That rules that out maybe. |
I can confirm this on Debian GNU/Linux, with Pidgin/libpurple 2.12 and purple-facebook a157645 . This similar bug solved itself, so, wait & see. |
I suspect this has something to do with Facebook dropping support for ancient versions of Messenger: https://messengerblog.com/general-messenger/update-on-support-for-older-versions-of-messenger-and-facebook-apps/ |
Just came to say that I have the same problem |
Getting the same error here. |
Same problem for me |
Just randomly got a few messages then something like "couldn't mark messages as received" or something along those lines then the same disconnection error again. I had been noticing a lot of double or triple messages in the past month or so, so maybe there had been some odd breakages that had been going unnoticed for a while. This might indicate that it won't be the huge tear up and rewrite that people seem to be worrying about in that the protocol might not have changed all that much, just in a few places. |
Having the same issue, Pidgin 2.11.0-1.fc24 (libpurple 2.11.0), purple-facebook-0.9.0-c9b74a765767 (compiled from git) |
I have the same problem DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" but my sister have windows 8.1 and Pidgin 2.11.0 (libpurple 2.11.0) and it's work. |
Cross-posting from bitlbee/bitlbee-facebook#138 (comment)
|
+1 Arch Linux 4.10.6-1-ARCH x86_64 |
Same here Windows 7 64bit |
Fix: https://github.com/dequis/purple-facebook/releases/tag/v0.9.1-c9b74a765767 edit: nevermind still not fixed |
fix allows connection/login but when sending a message says "failed to send message" |
for me also fix login, but after successful login its instantly disconected (can see contacts for second): I had two phase verification (SMS), but I disable it for testing it. Also I approve device login on FB webpage. |
I fixed arguments are invalid by disabling "mark messages as read" , "show self messages" , "show unread messages" , "open new group chats with incoming messages" - although I can't be sure which made it work |
In addition to disconnecting because |
receiving messages works OK with "mark messages as read" disabled |
+1 |
Same problem : $ lsb_release -d |
Getting this as well |
More info: |
While installing release with dist tarball for linux on Linux Mint i got an error:
And i can't find such package. Can someone help? |
Works perfect! Would it work if I upgraded to Pidgin version 2.12 or latest? Win7 - 64 bit |
@dezooo , go check in Help -> Plugin information and look for Facebook. Make sure you are using the newest version. If you don't know, you can paste it here and wait for someone to tell you. @mtyrio , sounds like there is a path problem somewhere. I am not sure since it has been a while since I have compiled this on Linux. @patelkunala , you can upgrade if you want, but it is best to have the newest version. It is really up to you. |
Same with me - I get the same error with version |
Facebook |
works on Xubuntu 16.04 |
Thanks!! Worked for me as well.
|
|
I can confirm the "Null value for $.viewer.message_threads.sync_sequence_id" issue in Xubuntu with Pidgin 2.10.12.
|
Pidgin versions (or linux kernel versions) do not affect this issue so I don't need to know those. Instead, please check the version of this plugin in buddy list -> help menu -> plugin information. Also, there was another release since my last comment, 0.9.3, appears to fix some more issues: https://github.com/dequis/purple-facebook/releases Depending on the way it was built, that version might appear as 20170330[...] |
Facebook I'll go grab 0.9.3 and report the differential. |
👍 |
SOLVED! Sorry for error reports. |
+1 I hope i don't have to compile sources to get it back working .. ;) |
Even after a |
I was able to get it to rebuild just fine with |
Thank you very much, dequis. Works like a charm on Ubuntu Pidgin. |
Thanks indeed, dequis! Works as well with the spectrum2 transport. |
For me, on a Git checkout, it also took |
When can we have updated windows builds? |
@grzegorz-janoszka The Windows build is automatically built and updated on every commit by Travis CI. |
Ah, indeed. I was mistaken by exactly the same file length (and no version number). Indeed the windows build has been fixed. |
i tried the download from: https://github.com/dequis/purple-facebook/wiki/Installing-on-Windows I am still getting the "Null value for $.viewer.message_threads.sync_sequence_id" error. I am on the newest version of Pidgin. What should I do? |
@TheFoggyRoad please open a new issue Also, verify the version of the plugin in buddy list -> help menu -> plugin information. Depending on the way it was built, that version might appear as 20170330[...] |
I'm locking this thread since this is resolved. If anyone has any issues please open a new issue instead. |
ADMIN EDIT
This is already fixed in the latest release. This ticket is only open for visibility
Get the latest version from here https://github.com/dequis/purple-facebook/releases
Original ticket description
Connection was lost earlier today. Reconnecting results in immediately disconnecting with
Null value for $.viewer.message_threads.sync_sequence_id
.pidgin/libpurple 1.12.0
purple-facebook 0.9.0-c9b74a765767
The text was updated successfully, but these errors were encountered: