bitlbee/bitlbee-facebook

Group chat unable to change topic

Closed this issue · 8 comments

I am unable to change topic using /topic in group chat channel. Every time I try facebook reconnects saying Error: Failed generic API operation

This works for me. I'm going to need some debug output

I have attached the log. All I did was connect to facebook then list chats using fbchats, join using fbjoin then change topic using /topic

[INFO] facebook: POST Request (0x5582f4bba060): https://api.facebook.com/method/messaging.setthreadname
[INFO] facebook:   Content-Type: application/x-www-form-urlencoded
[INFO] facebook:   Connection: Close
[INFO] facebook:   Accept: */*
[INFO] facebook:   Content-Length: 259
[INFO] facebook:   Host: api.facebook.com
[INFO] facebook:   Authorization: OAuth [...]
[INFO] facebook:   
[INFO] facebook:   fb_api_req_friendly_name=setThreadName&locale=en_IN&name=%22Some%20topic%20here%22&format=json&device_id=6a2ed3fb-1ad5-4968-900e-c954311f82ea&api_key=256002347743983&tid=t_id.1318734614848892&method=messaging.setthreadname&sig=f37f7524225c667b94a222470b72c88f
[INFO] facebook: POST Response (0x5582f4bba060): https://api.facebook.com/method/messaging.setthreadname (200 OK)
[INFO] facebook:   HTTP/1.1 200 OK
[INFO] facebook:   Access-Control-Allow-Origin: *
[INFO] facebook:   Pragma: no-cache
[INFO] facebook:   Cache-Control: private, no-cache, no-store, must-revalidate
[INFO] facebook:   facebook-api-version: v1.0
[INFO] facebook:   Expires: Sat, 01 Jan 2000 00:00:00 GMT
[INFO] facebook:   Content-Type: application/json
[INFO] facebook:   x-fb-trace-id: F6mvmMpDJDG
[INFO] facebook:   x-fb-rev: 2789434
[INFO] facebook:   Vary: Accept-Encoding
[INFO] facebook:   X-FB-Debug: OeXpmJUauuIIs6/OkgznDQs2u211W/Z05415JrgqcTw7nl9sRoVP1lgMaNELXmRQ+1EjyIwmhHAoX07B07EqtA==
[INFO] facebook:   Date: Sun, 22 Jan 2017 02:35:24 GMT
[INFO] facebook:   Connection: close
[INFO] facebook:   
[INFO] facebook:   {"error_code":2,"error_msg":"Service temporarily unavailable (2)","request_args":[{"key":"method","value":"messaging.setthreadname"},{"key":"fb_api_req_friendly_name","value":"setThreadName"},{"key":"locale","value":"en_IN"},{"key":"name","value":"\"Some topic here\""},{"key":"format","value":"json"},{"key":"device_id","value":"6a2ed3fb-1ad5-4968-900e-c954311f82ea"},{"key":"api_key","value":"256002347743983"},{"key":"tid","value":"t_id.1318734614848892"},{"key":"sig","value":"f37f7524225c667b94a222470b72c88f"}]}
[ERROR] facebook: Failed generic API operation

Thanks!

I forgot to mention this tends to have private stuff. I edited your comment to only include the relevant part and removed the access token. You might want to invalidate that using 'end session' in this page

I wonder how linear the x-fb-rev parameter is. I'm in 2790673, you're in 2789434 and it works here. I switched to beta and got 2789434 and still works. Maybe it really is just a case of "Service temporarily unavailable", unlike the other ticket. The bug here is mainly failing so hard, which is something this plugin likes to do.

I thought it might contain private info so created an account specifically for this purpose as I didn't want to care what part is private.

The second para goes over my head. Can you explain it to me in simpler terms

I thought it might contain private info so created an account specifically for this purpose as I didn't want to care what part is private.

Nice. I like you.

The second para goes over my head. Can you explain it to me in simpler terms

That's mostly just me thinking aloud. Since it works for me regardless of the version I test against, I think it's just a temporary issue. But this should be handled more gracefully by not disconnecting the account when it happens.

The issue is repeating. It was there two days ago, it was there yesterday, it is there today and it is there even after I pulled master and recompiled.

dgw commented

I've just run into this as well. I last updated the plugin to 82e6bcf, but based on @KamalGalrani's comment it doesn't sound like running a more recent commit would have prevented the issue.

Confirmed and fixed with 59fcaab (in the development branch)