-
Notifications
You must be signed in to change notification settings - Fork 43
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
"Failed to parse thread information" after 1.1.0 update #139
Comments
Please check for errors in &bitlbee, the kick in the room is meaningless, just a reference to the other error.
That error means #channel-name already exists. Use a different name, remove the other one, or just change its room setting. See |
My apologies. Removed the channel and readded, tried to join, and received the error in &bitlbee
|
2f17542 should help |
Yep, that did it! Thank you! |
Let's keep this one open for visibility |
Release notes: https://github.com/bitlbee/bitlbee-facebook/releases/tag/v1.1.0 Issue #139: bitlbee/bitlbee-facebook#139 git-svn-id: svn+ssh://svn.freebsd.org/ports/head@437274 35697150-7ecd-e111-bb59-0022644237b5
Waited a bit to release it but there it is https://github.com/bitlbee/bitlbee-facebook/releases/tag/v1.1.1 |
Likely related to 138 and the newest update, a previously functioning groupchat now returns the titular error. Packages updated, Inetd restarted, server rebooted, all the usual debugging steps. This is also what showed up promptly before the old API retiring hit my account.
Attempting to manually delete groupchat from config and rejoin manually with "chat add facebook 1111111 #channel-name" I simply get "Could not add chatroom."
The text was updated successfully, but these errors were encountered: