Open hlesueur opened 4 years ago
@hlesueur Similar problem here. Unfortunately, it does not work for me.
One difference, the token that give me something different than error: "invalid_auth" has following format:
xoxb-(13digits)-(theRest)
Using token format as I mention I got similar response:
{ "ok": false, "error": "internal_error" }
but the riot_bridge in the slack workspace is still away
.
I had the same problem again, same symptoms :
but now indeed, as @zymone I cannot find the proper token (I always get an "invalid_auth") Can anyone provide a way to get the right token? (maybe there is still another problem on top of that but at least so that I can try to re activate the bot inside slack)
Thanks for your help !
We are having the same problem here. Has anyone been able to figure this out?
Same issue ....
Hello, I had a properly set riot-slack bridge, configured with the slack integration from riot (except pupetting did not work) I tried rebuilding the whole from scratch, so I unlinked the slack_integration bot in riot and removed the riot_bridge app in slack Then set it back again
BUT I could no longer relay messages from slack to matrix (the reverse matrix => slack was working)
After struggling a bit, I found out that the riot_bridge bot was appearing as 'away' in slack (with the empty circle, when you do a one-to-one chat) ... Which may obvisouly be a reason for it not to relay messages (it was having some beach holidays somewhere out of confinement...)
So I tortured it (and myself), after struggling (again!) I found a way to set it back to 'present' Slack has a lot of documentation about their scripts. One page is dedicated to set bot presence, user presence https://api.slack.com/methods/users.setPresence From within you can test it, for yourself or for another one using a token. (so you need your app's token !)
Although I'm not 100% sure the following steps are the ones which brought riot_bridge back, here are they:
From RIOT, do as if you wished to link a new room, then copy the URL you get when your mouse is over a room, as it contains a token...! Copy the scalar_token from that URL.
this scalar token does not work in the slack "setPresence", so I reformatted it into a Slack App token. Fortunately I had an example from an App I created myself in slack. Format is : xoxb-(13digits)-(13digits)-(theRest) without the parenthesis
going to https://api.slack.com/methods/users.setPresence/test with this token (URL: https://slack.com/api/users.setPresence?token=thisXXXtoken&presence=active&pretty=1)
Slack throwed an internal error but the doc tells you that it comes from slack side and that your action may have worked before the internal error... I looked and the bot was green again... (and the bridge back to work in both ways)