purple-facebook
purple-facebook copied to clipboard
dequis
Can't get a new session
My stored Facebook session was invalidated due to a password change. Pidgin gave this message:
Error validating access token: Session does not match current stored session. This may be because the user changed the password since the time the session was created or Facebook has changed the session for security reasons. (452)
So I logged out and back in. But now that message appears every time I try to reconnect. It seems Pidgin can't make a new session?
Related: #72 which contains debug for this, and claims to have fixed that with this commit
facebook: Response Data: {"error":{"message":"Error validating access token: Session does not match current stored session. This may be because the user changed the password since the time the session was created or Facebook has changed the session for security reasons.","type":"OAuthException","code":190,"error_subcode":452}}
Also related: https://github.com/bitlbee/bitlbee-facebook/issues/65
Workaround: remove account and add it again. Or maybe edit accounts xml file and remove token.
Might be an old issue, but if you find yourself stuck with this, the workaround fix proposed by @dequis works, and is easier than removing/adding the entire account, IMO: 1: Close Pidgin 2: Remove the token from the accounts.xml FB account 3: Start Pidgin
Personally, every time i've received this error, it fixed itself in the next login. I'm not sure what situation would lead to make this persistent.
I had it happen when I used Pidgin on a new machine, and had to generate a new app password in FB for it. Somehow it got stuck on that issue after that, until I solved it manually.
Every time I get this problem (pretty often the last ~2weeks, because facebook doesn't like traveling with this plugin somehow) I have to delete the account and add a new one. Pretty annoying :(
Getting this periodically too. Deleting token from accounts.xml works, but I don't like having to exit and restart each time.
Still haven't reproduced this issue even though I received this error and similar ones many times - re-enabling the account is always enough for me. Sorry, can't really help.