Null value for $.viewer.message_threads.sync_sequence_id #306

Closed
paulguy opened this Issue Mar 29, 2017 · 82 comments

Comments

Projects
None yet
@paulguy

paulguy commented Mar 29, 2017

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

@scrad

This comment has been minimized.

Show comment
Hide comment
@scrad

scrad Mar 29, 2017

I'm getting this error as well

Windows 8.1
Pidgin 2.10.11 (libpurple 2.10.11)
purple-facebook Version: 20161121a157645c9b74a765767~117

scrad commented Mar 29, 2017

I'm getting this error as well

Windows 8.1
Pidgin 2.10.11 (libpurple 2.10.11)
purple-facebook Version: 20161121a157645c9b74a765767~117

@SarcasmCupcakes

This comment has been minimized.

Show comment
Hide comment
@SarcasmCupcakes

SarcasmCupcakes Mar 29, 2017

All morning. Even upgraded Pidgin and re-installed the two .dll files.

All morning. Even upgraded Pidgin and re-installed the two .dll files.

@drainx85

This comment has been minimized.

Show comment
Hide comment
@drainx85

drainx85 Mar 29, 2017

Just happened to me as well when I logged in to my pc this evening. Wonder what facebook changed this time...

Just happened to me as well when I logged in to my pc this evening. Wonder what facebook changed this time...

@jh-maeng

This comment has been minimized.

Show comment
Hide comment
@jh-maeng

jh-maeng Mar 29, 2017

I'm getting same error.

A few logs below:

(10:33:57) http: releasing a socket: 0E67C758
(10:33:57) http: Request 02396618 performed successfully.
(10:33:57) facebook: HTTP Response (02396618):
(10:33:57) facebook: Response Error: 200
(10:33:57) facebook: Response Data: {"viewer":{"message_threads":{"count":9,"mute_until":0,"nodes":[],"page_info":{"has_next_page":true},"sync_sequence_id":null,"unread_count":0,"unseen_count":0}}}
(10:33:57) facebook: Parsing JSON: {"viewer":{"message_threads":{"count":9,"mute_until":0,"nodes":[],"page_info":{"has_next_page":true},"sync_sequence_id":null,"unread_count":0,"unseen_count":0}}}

(10:33:57) connection: Connection error on 0E49FD90 (reason: 0 description: Null value for $.viewer.message_threads.sync_sequence_id)
(10:33:57) http: destroying socket: 0E67C758
(10:33:57) account: Disconnecting account xxxx (02356C00)
(10:33:57) connection: Disconnecting connection 0E49FD90
(10:33:57) facebook: Writing 14 (flags: 0x0)
(10:33:57) facebook: 00000000 e0 00 |..|
(10:33:57) facebook: 00000010

jh-maeng commented Mar 29, 2017

I'm getting same error.

A few logs below:

(10:33:57) http: releasing a socket: 0E67C758
(10:33:57) http: Request 02396618 performed successfully.
(10:33:57) facebook: HTTP Response (02396618):
(10:33:57) facebook: Response Error: 200
(10:33:57) facebook: Response Data: {"viewer":{"message_threads":{"count":9,"mute_until":0,"nodes":[],"page_info":{"has_next_page":true},"sync_sequence_id":null,"unread_count":0,"unseen_count":0}}}
(10:33:57) facebook: Parsing JSON: {"viewer":{"message_threads":{"count":9,"mute_until":0,"nodes":[],"page_info":{"has_next_page":true},"sync_sequence_id":null,"unread_count":0,"unseen_count":0}}}

(10:33:57) connection: Connection error on 0E49FD90 (reason: 0 description: Null value for $.viewer.message_threads.sync_sequence_id)
(10:33:57) http: destroying socket: 0E67C758
(10:33:57) account: Disconnecting account xxxx (02356C00)
(10:33:57) connection: Disconnecting connection 0E49FD90
(10:33:57) facebook: Writing 14 (flags: 0x0)
(10:33:57) facebook: 00000000 e0 00 |..|
(10:33:57) facebook: 00000010

@skolskoly

This comment has been minimized.

Show comment
Hide comment
@skolskoly

skolskoly Mar 29, 2017

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.

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.

@advcomp2019

This comment has been minimized.

Show comment
Hide comment
@advcomp2019

advcomp2019 Mar 29, 2017

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.

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.

@aeridus

This comment has been minimized.

Show comment
Hide comment
@aeridus

aeridus Mar 29, 2017

Same here, and I don't use the mobile app. I updated Pidgin and still see the same error.

aeridus commented Mar 29, 2017

Same here, and I don't use the mobile app. I updated Pidgin and still see the same error.

@advcomp2019

This comment has been minimized.

Show comment
Hide comment
@advcomp2019

advcomp2019 Mar 29, 2017

That rules that out maybe.

advcomp2019 commented Mar 29, 2017

That rules that out maybe.

@Steap

This comment has been minimized.

Show comment
Hide comment
@Steap

Steap Mar 29, 2017

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.

Steap commented Mar 29, 2017

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.

@auscompgeek

This comment has been minimized.

Show comment
Hide comment
@auscompgeek

auscompgeek Mar 29, 2017

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/

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/

@starndust31

This comment has been minimized.

Show comment
Hide comment
@starndust31

starndust31 Mar 29, 2017

Just came to say that I have the same problem

Just came to say that I have the same problem

@alexolog

This comment has been minimized.

Show comment
Hide comment
@alexolog

alexolog Mar 29, 2017

Getting the same error here.
And people are reporting it on bitllbee

Getting the same error here.
And people are reporting it on bitllbee

@ionl

This comment has been minimized.

Show comment
Hide comment
@ionl

ionl Mar 29, 2017

Same problem for me
$ lsb_release -d
Description: Ubuntu 16.10
$ pidgin -v
Pidgin 2.10.12 (libpurple 2.10.12)
$ uname -a
Linux pc 4.8.0-42-generic #45-Ubuntu SMP Wed Mar 8 20:06:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

ionl commented Mar 29, 2017

Same problem for me
$ lsb_release -d
Description: Ubuntu 16.10
$ pidgin -v
Pidgin 2.10.12 (libpurple 2.10.12)
$ uname -a
Linux pc 4.8.0-42-generic #45-Ubuntu SMP Wed Mar 8 20:06:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

@paulguy

This comment has been minimized.

Show comment
Hide comment
@paulguy

paulguy Mar 29, 2017

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.

paulguy commented Mar 29, 2017

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.

@rajcze

This comment has been minimized.

Show comment
Hide comment
@rajcze

rajcze Mar 29, 2017

Having the same issue, Pidgin 2.11.0-1.fc24 (libpurple 2.11.0), purple-facebook-0.9.0-c9b74a765767 (compiled from git)

rajcze commented Mar 29, 2017

Having the same issue, Pidgin 2.11.0-1.fc24 (libpurple 2.11.0), purple-facebook-0.9.0-c9b74a765767 (compiled from git)

@anecznik

This comment has been minimized.

Show comment
Hide comment
@anecznik

anecznik Mar 29, 2017

I have the same problem

DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"
Pidgin 2.10.12 (libpurple 2.10.12)

but my sister have windows 8.1 and Pidgin 2.11.0 (libpurple 2.11.0) and it's work.

I have the same problem

DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"
Pidgin 2.10.12 (libpurple 2.10.12)

but my sister have windows 8.1 and Pidgin 2.11.0 (libpurple 2.11.0) and it's work.

@dequis

This comment has been minimized.

Show comment
Hide comment
@dequis

dequis Mar 29, 2017

Owner

Cross-posting from bitlbee/bitlbee-facebook#138 (comment)

well, fuck

Owner

dequis commented Mar 29, 2017

Cross-posting from bitlbee/bitlbee-facebook#138 (comment)

well, fuck

@mfaerevaag

This comment has been minimized.

Show comment
Hide comment
@mfaerevaag

mfaerevaag Mar 29, 2017

+1

Arch Linux 4.10.6-1-ARCH x86_64
Pidgin 2.12.0 (libpurple 2.12.0)
purple-facebook 0.9.0-1

+1

Arch Linux 4.10.6-1-ARCH x86_64
Pidgin 2.12.0 (libpurple 2.12.0)
purple-facebook 0.9.0-1

@mattlog

This comment has been minimized.

Show comment
Hide comment
@mattlog

mattlog Mar 29, 2017

Same here

Windows 7 64bit
Pidgin 2.12.0

mattlog commented Mar 29, 2017

Same here

Windows 7 64bit
Pidgin 2.12.0

@dequis

This comment has been minimized.

Show comment
Hide comment
Owner

dequis commented Mar 29, 2017

@freddysdad

This comment has been minimized.

Show comment
Hide comment
@freddysdad

freddysdad Mar 29, 2017

fix allows connection/login but when sending a message says "failed to send message"

fix allows connection/login but when sending a message says "failed to send message"

@kalab-oto

This comment has been minimized.

Show comment
Hide comment
@kalab-oto

kalab-oto Mar 29, 2017

for me also fix login, but after successful login its instantly disconected (can see contacts for second):
Arguments are invalid

I had two phase verification (SMS), but I disable it for testing it. Also I approve device login on FB webpage.

kalab-oto commented Mar 29, 2017

for me also fix login, but after successful login its instantly disconected (can see contacts for second):
Arguments are invalid

I had two phase verification (SMS), but I disable it for testing it. Also I approve device login on FB webpage.

@freddysdad

This comment has been minimized.

Show comment
Hide comment
@freddysdad

freddysdad Mar 29, 2017

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

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

@Metalhead33

This comment has been minimized.

Show comment
Hide comment
@Metalhead33

Metalhead33 Mar 29, 2017

In addition to disconnecting because failed to send message, it also fails to reconnect saying Arguments are invalid, and when I receive a message, it's Failed to mark read

In addition to disconnecting because failed to send message, it also fails to reconnect saying Arguments are invalid, and when I receive a message, it's Failed to mark read

@freddysdad

This comment has been minimized.

Show comment
Hide comment
@freddysdad

freddysdad Mar 29, 2017

receiving messages works OK with "mark messages as read" disabled

receiving messages works OK with "mark messages as read" disabled

@darkmanek

This comment has been minimized.

Show comment
Hide comment
@darkmanek

darkmanek Mar 29, 2017

+1
Manjaro 4.10.6-1-ck-pentm i686
Pidgin 2.12.0 (libpurple 2.12.0)
purple-facebook 0.9.0-1

purple-debug.txt

+1
Manjaro 4.10.6-1-ck-pentm i686
Pidgin 2.12.0 (libpurple 2.12.0)
purple-facebook 0.9.0-1

purple-debug.txt

@jcengelsen

This comment has been minimized.

Show comment
Hide comment
@jcengelsen

jcengelsen Mar 29, 2017

Same problem :

$ lsb_release -d
Description: Linux Mint 18 Sarah
$ pidgin -v
Pidgin 2.10.12 (libpurple 2.10.12)
$ uname -a
Linux ThinkPad-T530 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Same problem :

$ lsb_release -d
Description: Linux Mint 18 Sarah
$ pidgin -v
Pidgin 2.10.12 (libpurple 2.10.12)
$ uname -a
Linux ThinkPad-T530 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

@LunaSquee

This comment has been minimized.

Show comment
Hide comment
@LunaSquee

LunaSquee Mar 29, 2017

Getting this as well
Arch Linux
Pidgin 2.12.0 (libpurple 2.12.0)
Linux EvertLaptop 4.10.4-1-ARCH #1 SMP PREEMPT Sat Mar 18 19:39:18 CET 2017 x86_64 GNU/Linux

Getting this as well
Arch Linux
Pidgin 2.12.0 (libpurple 2.12.0)
Linux EvertLaptop 4.10.4-1-ARCH #1 SMP PREEMPT Sat Mar 18 19:39:18 CET 2017 x86_64 GNU/Linux

@marsjaninzmarsa

This comment has been minimized.

Show comment
Hide comment
@buchty

This comment has been minimized.

Show comment
Hide comment
@buchty

buchty Mar 29, 2017

Latest update (9e4c738) cures "Null value for $.viewer.message_threads.sync_sequence_id", but lets not send anything ("failed to send message" -> disconnect), also occasional "arguments are invalid" occurs. (Pidgin 2.12.0, Ubuntu 12.04LTS, Kernel 3.13.0-113-generic)

buchty commented Mar 29, 2017

Latest update (9e4c738) cures "Null value for $.viewer.message_threads.sync_sequence_id", but lets not send anything ("failed to send message" -> disconnect), also occasional "arguments are invalid" occurs. (Pidgin 2.12.0, Ubuntu 12.04LTS, Kernel 3.13.0-113-generic)

@norbert79

This comment has been minimized.

Show comment
Hide comment
@norbert79

norbert79 Mar 29, 2017

Just a generic remark over here: As it seems Facebook has added a new functionality to its chat by adding emoticons to specific lines, above the regular emoticons handling (possibly adding the functionality to express reactions on specific texts instantly). Could this be related to the failing of sending messages as specific flag is not being used or not handled well?

Just a generic remark over here: As it seems Facebook has added a new functionality to its chat by adding emoticons to specific lines, above the regular emoticons handling (possibly adding the functionality to express reactions on specific texts instantly). Could this be related to the failing of sending messages as specific flag is not being used or not handled well?

@alexander-e

This comment has been minimized.

Show comment
Hide comment
@alexander-e

alexander-e Mar 29, 2017

After updating, I get the same error message as @buchty : "Arguments are invalid". (Ubuntu 16.04, Pidgin 2.10.12)

After updating, I get the same error message as @buchty : "Arguments are invalid". (Ubuntu 16.04, Pidgin 2.10.12)

@buchty

This comment has been minimized.

Show comment
Hide comment
@buchty

buchty Mar 29, 2017

Seems like the "arguments are invalid" is related to clearing message-read flags, cause it disappears once you clear unread messages using the browser-based messenger.

buchty commented Mar 29, 2017

Seems like the "arguments are invalid" is related to clearing message-read flags, cause it disappears once you clear unread messages using the browser-based messenger.

@buchty

This comment has been minimized.

Show comment
Hide comment
@buchty

buchty Mar 29, 2017

5061391 seems to work. Flawless login, receiving, and sending so far. Great job!

buchty commented Mar 29, 2017

5061391 seems to work. Flawless login, receiving, and sending so far. Great job!

@PeopleInside

This comment has been minimized.

Show comment
Hide comment
@PeopleInside

PeopleInside Mar 29, 2017

I AM using Pidgin, how to fix this issue in Pidgin?

I AM using Pidgin, how to fix this issue in Pidgin?

@dequis

This comment has been minimized.

Show comment
Hide comment
@dequis

dequis Mar 29, 2017

Owner

Yeah everything seems to be working now, but please test.

Release with dist tarball for linux users: https://github.com/dequis/purple-facebook/releases/tag/v0.9.2-c9b74a765767

Windows users can get a new dll from the usual place, https://github.com/dequis/purple-facebook/wiki/Installing-on-Windows

Remember to restart pidgin

Owner

dequis commented Mar 29, 2017

Yeah everything seems to be working now, but please test.

Release with dist tarball for linux users: https://github.com/dequis/purple-facebook/releases/tag/v0.9.2-c9b74a765767

Windows users can get a new dll from the usual place, https://github.com/dequis/purple-facebook/wiki/Installing-on-Windows

Remember to restart pidgin

@PeopleInside

This comment has been minimized.

Show comment
Hide comment
@PeopleInside

PeopleInside Mar 29, 2017

Works, thank you!

Works, thank you!

@kalab-oto

This comment has been minimized.

Show comment
Hide comment
@kalab-oto

kalab-oto Mar 29, 2017

Works, thank you very much for fast fix! 👍

Works, thank you very much for fast fix! 👍

@freddysdad

This comment has been minimized.

Show comment
Hide comment
@freddysdad

freddysdad Mar 29, 2017

confirmed working on Linux/Pidgin

confirmed working on Linux/Pidgin

@dequis

This comment has been minimized.

Show comment
Hide comment
@dequis

dequis Mar 29, 2017

Owner

@Dodger395 please open a new ticket

edit: and include a debug log https://github.com/dequis/purple-facebook/wiki/Debugging-Logs

Owner

dequis commented Mar 29, 2017

@Dodger395 please open a new ticket

edit: and include a debug log https://github.com/dequis/purple-facebook/wiki/Debugging-Logs

@scrad

This comment has been minimized.

Show comment
Hide comment
@scrad

scrad Mar 29, 2017

Works on windows 8.1

Thanks for the speedy fix and support.

scrad commented Mar 29, 2017

Works on windows 8.1

Thanks for the speedy fix and support.

@agent-rat

This comment has been minimized.

Show comment
Hide comment
@agent-rat

agent-rat Mar 29, 2017

Tested working on win7. Nice one!

Tested working on win7. Nice one!

@alexolog

This comment has been minimized.

Show comment
Hide comment
@alexolog

alexolog Mar 30, 2017

The new DLL still does not work for me (windows XP "POSReady 2009")

[mod edit, removed noise]
(21:59:14) connection: Connection error on 02E02418 (reason: 0 description: Null value for $.viewer.message_threads.sync_sequence_id)
(21:59:14) account: Disconnecting account [removed] (01235618)
(21:59:14) connection: Disconnecting connection 02E02418
(21:59:14) connection: Destroying connection 02E02418
(21:59:19) util: Writing file accounts.xml to directory C:\Documents and Settings\User\Application Data\.purple
(21:59:19) util: Writing file C:\Documents and Settings\User\Application Data\.purple\accounts.xml

alexolog commented Mar 30, 2017

The new DLL still does not work for me (windows XP "POSReady 2009")

[mod edit, removed noise]
(21:59:14) connection: Connection error on 02E02418 (reason: 0 description: Null value for $.viewer.message_threads.sync_sequence_id)
(21:59:14) account: Disconnecting account [removed] (01235618)
(21:59:14) connection: Disconnecting connection 02E02418
(21:59:14) connection: Destroying connection 02E02418
(21:59:19) util: Writing file accounts.xml to directory C:\Documents and Settings\User\Application Data\.purple
(21:59:19) util: Writing file C:\Documents and Settings\User\Application Data\.purple\accounts.xml
@alexolog

This comment has been minimized.

Show comment
Hide comment
@alexolog

alexolog Mar 30, 2017

Incidentally, connecting from my computer at work (Win 8.1) worked file even with the old DLL.

Looking inside the DLL for strings I see "20170329~5061391~c9b74a765767~124"
Is that the latest?

alexolog commented Mar 30, 2017

Incidentally, connecting from my computer at work (Win 8.1) worked file even with the old DLL.

Looking inside the DLL for strings I see "20170329~5061391~c9b74a765767~124"
Is that the latest?

@dequis

This comment has been minimized.

Show comment
Hide comment
@dequis

dequis Mar 30, 2017

Owner

@alexolog That debug log is useless without the flags mentioned in https://github.com/dequis/purple-facebook/wiki/Debugging-Logs

Also please open a new ticket.

Looking inside the DLL for strings I see "20170329~5061391~c9b74a765767~124"
Is that the latest?

Yes. Also, you can just use buddy list -> help menu -> plugin information

Owner

dequis commented Mar 30, 2017

@alexolog That debug log is useless without the flags mentioned in https://github.com/dequis/purple-facebook/wiki/Debugging-Logs

Also please open a new ticket.

Looking inside the DLL for strings I see "20170329~5061391~c9b74a765767~124"
Is that the latest?

Yes. Also, you can just use buddy list -> help menu -> plugin information

@alexolog

This comment has been minimized.

Show comment
Hide comment
@alexolog

alexolog Mar 30, 2017

Log emailed. Thanks.

Log emailed. Thanks.

@dcarriger90

This comment has been minimized.

Show comment
Hide comment
@dcarriger90

dcarriger90 Mar 30, 2017

Working for me on windows 10 after replacing dlls. Thanks.

Working for me on windows 10 after replacing dlls. Thanks.

@DnR-iData

This comment has been minimized.

Show comment
Hide comment
@DnR-iData

DnR-iData Mar 30, 2017

Worked for me on Ubuntu 16.04.2 LTS, thanks a lot :)

Worked for me on Ubuntu 16.04.2 LTS, thanks a lot :)

@dezooo

This comment has been minimized.

Show comment
Hide comment
@dezooo

dezooo Mar 30, 2017

Hei guys,
pulled 3cbb433, built and still the same error :(
Pidgin 2.11.0 (libpurple 2.11.0), debian jessie, using socks5

dezooo commented Mar 30, 2017

Hei guys,
pulled 3cbb433, built and still the same error :(
Pidgin 2.11.0 (libpurple 2.11.0), debian jessie, using socks5

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Mar 30, 2017

While installing release with dist tarball for linux on Linux Mint i got an error:

configure: error: Package requirements (purple <  3) were not met:

No package 'purple' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

And i can't find such package. Can someone help?

ghost commented Mar 30, 2017

While installing release with dist tarball for linux on Linux Mint i got an error:

configure: error: Package requirements (purple <  3) were not met:

No package 'purple' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

And i can't find such package. Can someone help?

@patelkunala

This comment has been minimized.

Show comment
Hide comment
@patelkunala

patelkunala Mar 30, 2017

Works perfect! Would it work if I upgraded to Pidgin version 2.12 or latest?

Win7 - 64 bit
Pidgin version - 2.10.12

Works perfect! Would it work if I upgraded to Pidgin version 2.12 or latest?

Win7 - 64 bit
Pidgin version - 2.10.12

@advcomp2019

This comment has been minimized.

Show comment
Hide comment
@advcomp2019

advcomp2019 Mar 30, 2017

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

advcomp2019 commented Mar 30, 2017

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

@boris-petrov

This comment has been minimized.

Show comment
Hide comment
@boris-petrov

boris-petrov Mar 30, 2017

Same with me - I get the same error with version 0.9.3-c9b74a765767 (seen in the Help -> Plugin information page). Help, I can't live without this plugin!

Same with me - I get the same error with version 0.9.3-c9b74a765767 (seen in the Help -> Plugin information page). Help, I can't live without this plugin!

@dezooo

This comment has been minimized.

Show comment
Hide comment
@dezooo

dezooo Mar 30, 2017

Facebook
Author: (null)
Version: 0.9.3-c9b74a765767
Website: https://github.com/dequis/purple-facebook
ID String: prpl-facebook
Loadable: Yes
Loaded: Yes

dezooo commented Mar 30, 2017

Facebook
Author: (null)
Version: 0.9.3-c9b74a765767
Website: https://github.com/dequis/purple-facebook
ID String: prpl-facebook
Loadable: Yes
Loaded: Yes

@abpross

This comment has been minimized.

Show comment
Hide comment
@abpross

abpross Mar 30, 2017

works on Xubuntu 16.04
Pidgin 2.10.12 (libpurple 2.10.12)

abpross commented Mar 30, 2017

works on Xubuntu 16.04
Pidgin 2.10.12 (libpurple 2.10.12)

@martlin2cz

This comment has been minimized.

Show comment
Hide comment
@martlin2cz

martlin2cz Mar 30, 2017

Thanks!! Worked for me as well.

$ uname -a
Linux martlins 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
$ pidgin -v
Pidgin 2.11.0 (libpurple 2.11.0)

Thanks!! Worked for me as well.

$ uname -a
Linux martlins 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
$ pidgin -v
Pidgin 2.11.0 (libpurple 2.11.0)
@dezooo

This comment has been minimized.

Show comment
Hide comment
@dezooo

dezooo Mar 30, 2017

(14:30:50) facebook: HTTP Response (0x7f7725c1ab00):
(14:30:50) facebook:   Response Error: 200
(14:30:50) facebook:   Response Data: {"viewer":{"message_threads":{"count":378,"mute_until":0,"nodes":[],"page_info":{"has_next_page":true},"sync_sequence_id":null,"unread_count":11,"unseen_count":0}}}
(14:30:50) facebook: Parsing JSON: {"viewer":{"message_threads":{"count":378,"mute_until":0,"nodes":[],"page_info":{"has_next_page":true},"sync_sequence_id":null,"unread_count":11,"unseen_count":0}}}
(14:30:50) connection: Connection error on 0x7f7725125e90 (reason: 0 description: Null value for $.viewer.message_threads.sync_sequence_id)

dezooo commented Mar 30, 2017

(14:30:50) facebook: HTTP Response (0x7f7725c1ab00):
(14:30:50) facebook:   Response Error: 200
(14:30:50) facebook:   Response Data: {"viewer":{"message_threads":{"count":378,"mute_until":0,"nodes":[],"page_info":{"has_next_page":true},"sync_sequence_id":null,"unread_count":11,"unseen_count":0}}}
(14:30:50) facebook: Parsing JSON: {"viewer":{"message_threads":{"count":378,"mute_until":0,"nodes":[],"page_info":{"has_next_page":true},"sync_sequence_id":null,"unread_count":11,"unseen_count":0}}}
(14:30:50) connection: Connection error on 0x7f7725125e90 (reason: 0 description: Null value for $.viewer.message_threads.sync_sequence_id)
@jnsatterfield

This comment has been minimized.

Show comment
Hide comment
@jnsatterfield

jnsatterfield Mar 30, 2017

I can confirm the "Null value for $.viewer.message_threads.sync_sequence_id" issue in Xubuntu with Pidgin 2.10.12.

uname -a
Linux himinbjorn 4.8.0-42-generic #45-Ubuntu SMP Wed Mar 8 20:06:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

pidgin -v
Pidgin 2.10.12 (libpurple 2.10.12)

jnsatterfield commented Mar 30, 2017

I can confirm the "Null value for $.viewer.message_threads.sync_sequence_id" issue in Xubuntu with Pidgin 2.10.12.

uname -a
Linux himinbjorn 4.8.0-42-generic #45-Ubuntu SMP Wed Mar 8 20:06:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

pidgin -v
Pidgin 2.10.12 (libpurple 2.10.12)

@dequis

This comment has been minimized.

Show comment
Hide comment
@dequis

dequis Mar 30, 2017

Owner

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[...]

Owner

dequis commented Mar 30, 2017

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[...]

@jnsatterfield

This comment has been minimized.

Show comment
Hide comment
@jnsatterfield

jnsatterfield Mar 30, 2017

Facebook
Author: (null)
Version: 0.9.0-c9b74a765767
Website: https://github.com/dequis/purple-facebook
ID String: prpl-facebook
Loadable: Yes
Loaded: Yes

I'll go grab 0.9.3 and report the differential.

Facebook
Author: (null)
Version: 0.9.0-c9b74a765767
Website: https://github.com/dequis/purple-facebook
ID String: prpl-facebook
Loadable: Yes
Loaded: Yes

I'll go grab 0.9.3 and report the differential.

@jnsatterfield

This comment has been minimized.

Show comment
Hide comment
@jnsatterfield

jnsatterfield Mar 30, 2017

👍
After cloning version 0.9.3 and building/installing, the Null value for $.viewer.message_threads.sync_sequence_id issue seems to be resolved.

👍
After cloning version 0.9.3 and building/installing, the Null value for $.viewer.message_threads.sync_sequence_id issue seems to be resolved.

@dezooo

This comment has been minimized.

Show comment
Hide comment
@dezooo

dezooo Mar 30, 2017

SOLVED!
make clean && make
is not enough! something is not rebuilt!
If I cloned a fresh copy and built it, it worked!

Sorry for error reports.

dezooo commented Mar 30, 2017

SOLVED!
make clean && make
is not enough! something is not rebuilt!
If I cloned a fresh copy and built it, it worked!

Sorry for error reports.

@marmz

This comment has been minimized.

Show comment
Hide comment
@marmz

marmz Mar 30, 2017

+1
Same error message, from today...
Using pidgin + libpurple-dev from OFFICIAL Debian Jessie STABLE repositories.

I hope i don't have to compile sources to get it back working .. ;)

marmz commented Mar 30, 2017

+1
Same error message, from today...
Using pidgin + libpurple-dev from OFFICIAL Debian Jessie STABLE repositories.

I hope i don't have to compile sources to get it back working .. ;)

@rfc1036

This comment has been minimized.

Show comment
Hide comment
@rfc1036

rfc1036 Mar 30, 2017

Even after a make distclean, I had to run again update.sh to build a working pluing. HTH.

rfc1036 commented Mar 30, 2017

Even after a make distclean, I had to run again update.sh to build a working pluing. HTH.

@paulguy

This comment has been minimized.

Show comment
Hide comment
@paulguy

paulguy Mar 30, 2017

I was able to get it to rebuild just fine with git reset --hard then running ./autogen.sh.

paulguy commented Mar 30, 2017

I was able to get it to rebuild just fine with git reset --hard then running ./autogen.sh.

@baronvertigovongrahamthesecondofsealand

This comment has been minimized.

Show comment
Hide comment
@baronvertigovongrahamthesecondofsealand

baronvertigovongrahamthesecondofsealand Mar 30, 2017

Thank you very much, dequis. Works like a charm on Ubuntu Pidgin.

Thank you very much, dequis. Works like a charm on Ubuntu Pidgin.

@karbon15

This comment has been minimized.

Show comment
Hide comment
@karbon15

karbon15 Mar 30, 2017

Thanks indeed, dequis! Works as well with the spectrum2 transport.

Thanks indeed, dequis! Works as well with the spectrum2 transport.

@mandree

This comment has been minimized.

Show comment
Hide comment
@mandree

mandree Mar 30, 2017

For me, on a Git checkout, it also took ./update.sh and autogen.sh before I could build a working version. Just "git pull" isn't sufficient.

mandree commented Mar 30, 2017

For me, on a Git checkout, it also took ./update.sh and autogen.sh before I could build a working version. Just "git pull" isn't sufficient.

@grzegorz-janoszka

This comment has been minimized.

Show comment
Hide comment
@grzegorz-janoszka

grzegorz-janoszka Apr 7, 2017

When can we have updated windows builds?

When can we have updated windows builds?

@auscompgeek

This comment has been minimized.

Show comment
Hide comment
@auscompgeek

auscompgeek Apr 7, 2017

@grzegorz-janoszka The Windows build is automatically built and updated on every commit by Travis CI.

auscompgeek commented Apr 7, 2017

@grzegorz-janoszka The Windows build is automatically built and updated on every commit by Travis CI.

@grzegorz-janoszka

This comment has been minimized.

Show comment
Hide comment
@grzegorz-janoszka

grzegorz-janoszka Apr 7, 2017

Ah, indeed. I was mistaken by exactly the same file length (and no version number). Indeed the windows build has been fixed.

Ah, indeed. I was mistaken by exactly the same file length (and no version number). Indeed the windows build has been fixed.

@TheFoggyRoad

This comment has been minimized.

Show comment
Hide comment
@TheFoggyRoad

TheFoggyRoad Apr 9, 2017

i tried the download from: https://github.com/dequis/purple-facebook/wiki/Installing-on-Windows
As well as downloading the new package from chocolatey: cup purple-facebook --version=0.9.3.126

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?

i tried the download from: https://github.com/dequis/purple-facebook/wiki/Installing-on-Windows
As well as downloading the new package from chocolatey: cup purple-facebook --version=0.9.3.126

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?

@dequis

This comment has been minimized.

Show comment
Hide comment
@dequis

dequis Apr 10, 2017

Owner

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

Owner

dequis commented Apr 10, 2017

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

Repository owner locked and limited conversation to collaborators Apr 10, 2017

@dequis

This comment has been minimized.

Show comment
Hide comment
@dequis

dequis Apr 10, 2017

Owner

I'm locking this thread since this is resolved.

If anyone has any issues please open a new issue instead.

Owner

dequis commented Apr 10, 2017

I'm locking this thread since this is resolved.

If anyone has any issues please open a new issue instead.

@dequis dequis closed this Jun 10, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.